The strongest answer you can give an auditor is a design where no employee has a technical path to the keys, plus evidence the auditor can check without trusting you. On Lit Protocol, keys are derived inside an attested hardware enclave, and Lit's own code never stores or exports them. The rules for using them live in a contract on Base, and you can make your own multisig the only account the contract accepts rule changes from. An auditor can verify the code running in the enclave, read the rules, and see every change as a signed transaction.
I will go through what an auditor usually asks, how each answer works on Lit, the commands they can run, and the limits you should tell them about.
What the auditor will ask
The first question is where the key lives and who can get it. The second is who can change the rules for using the key. The third is how they can see every change that was made.…