Somewhere in your files is a cyber insurance application, signed by an officer of your firm, making specific factual representations about your controls: MFA on email and remote access, EDR deployed, backups tested, payment instructions verified out-of-band, training conducted. The premium was priced on those answers. The claim, when it comes, will be adjusted against them, and the gap between what the application says and what your environment does is, functionally, an unfunded retention you don’t know you’re carrying.
This is not theoretical. Carriers have rescinded policies and contested claims over application misrepresentations. The matter practitioners cite is Travelers v. International Control Services (2022), in which the carrier sought rescission after alleging the insured’s MFA representation was inaccurate, and the policy was ultimately rescinded by agreement: not a litigated merits decision, but an unambiguous statement of carrier intent. The market’s broader correction since has made underwriting questions sharper and adjusters more willing to check.
Why advisory firms drift into misrepresentation
Nobody lies on purpose. The application gets filled out by whoever renews the insurance, usually from memory, usually optimistically. “Do you have MFA?” gets a yes because the firm has MFA somewhere, while the custodian portal, the legacy VPN, or the file server quietly lack it. Then twelve months pass, an employee disables enforcement for a difficult partner, a new SaaS tool comes aboard outside the SSO, and the representations age while the signature stays fresh. At claim time, the adjuster doesn’t ask what you intended. They ask what was true.
The annual reconciliation
The fix is mechanical: treat the insurance application as a compliance document and reconcile it annually, ideally as a named section of your 206(4)-7 review.
- Pull the actual application, not the policy, the application with your answers. Your broker has it if you don’t.
- Convert each representation into a checkable claim. “MFA on all email accounts” becomes a report from your identity provider showing enforcement status per account, exceptions listed.
- Test the strongest claims hardest. “Backups are tested” means a restoration test with a date and a result. “Out-of-band verification” means the wire log shows call-backs actually recorded. “Training conducted” means completion records, not a calendar invite.
- Document the variances and pick a side. Either remediate the environment to match the representation, or correct the answer at renewal and accept the premium consequence. Both are legitimate. Silent variance is the only wrong answer.
- File the reconciliation memo. One page: representations checked, evidence, variances, disposition. If a claim is ever contested, this memo is your good-faith record, and if an examiner asks how the firm assesses its own controls, it does double duty.
The renewal-season bonus
Walking into renewal with evidence behind every answer changes the conversation. Brokers can negotiate from documented controls; underwriters price uncertainty into premiums. Firms that show up with an identity-provider MFA report, a restoration test log, and a wire verification log are not the risks the questionnaire was designed to smoke out, and it shows in the quotes.
BrainTrust members: the Annual Risk Assessment Template includes the insurance reconciliation section, and the Access Control and MFA Policy defines the enforcement standard your application almost certainly already claims you have.