How to Run the Cybersecurity Section of Your Annual 206(4)-7 Review

Rule 206(4)-7 requires an adviser to review, at least annually, the adequacy of its compliance policies and the effectiveness of their implementation. Most firms do this faithfully for trading, custody, and marketing, and then the cybersecurity section says something like “the firm’s IT provider confirmed systems are secure.” That sentence answers neither of the questions the rule actually asks, and examiners know it.

The problem isn’t effort. It’s that nobody ever showed the CCO what reviewing cybersecurity means when you aren’t a technician. Here is the method I use when I run these reviews for client firms.

The question the review answers

Not “are we secure?”: no honest review can answer that. The question is: do our written policies describe what the firm actually does, and can we produce evidence of it? Adequacy and effectiveness, exactly as the rule frames it. Every finding in the section should be one of three sentences: the policy matches practice and here is the evidence; the practice exists but the policy doesn’t describe it; the policy promises something the firm doesn’t do. The third kind is the one that becomes an enforcement theory, because a written policy you ignore is evidence against you.

The evidence to pull before the meeting

  • Access recertification. A user list from each critical system, email, custodian portal, CRM, portfolio management, reviewed name by name against current employees and current roles. Departed employee still active in anything = finding.
  • MFA coverage. Not “we have MFA”: which accounts, which systems, and what the exceptions are. Pull the report from your identity provider; don’t ask, verify.
  • The incident log. Review every entry, including near-misses. If the log is empty, the finding is about the log.
  • Vendor file sampling. Pick three vendors that touch client data. Confirm current diligence, a contract with breach-notification terms, and that nobody at the firm can remember a problem the file doesn’t reflect.
  • Training records. Who completed it, who didn’t, and what happened to the people who didn’t.
  • Backup restoration test. Not “backups are running”: when did someone last restore a file and confirm it was intact? If the answer is never, that’s the finding.
  • Last assessment’s findings. The fastest deficiency an examiner can write is a finding you identified yourself last year and didn’t remediate. Every prior finding gets a status: closed, in progress with a date, or accepted with a documented reason.

Write it down like an examiner will read it — because one will

Examiners ask for the annual review’s documentation, and a written record is what they expect to see. (A 2023 amendment would have made written documentation an explicit rule requirement; it was vacated by the Fifth Circuit along with the private fund adviser rules, so today the obligation is examiner expectation and self-preservation rather than rule text. Conduct the review without a record and you will spend the exam trying to prove a negative.) The format that works: a dated memo, the evidence reviewed listed by name, findings numbered, owners and deadlines assigned. One page of specific beats ten pages of boilerplate.

Make it a calendar event, not an archaeology project

The review collapses when it’s attempted in one heroic week. Spread the evidence pulls across the year, access recertification in Q1, vendor sampling in Q2, restoration test in Q3, and the annual review meeting becomes assembly rather than excavation. This is what “maintained year-round” actually means in practice.

BrainTrust members: the Annual 206(4)-7 Compliance Review template structures this exact method, and the Compliance Calendar Checklist spreads the evidence collection across the year. Run them together once and the second year takes half the time.

The BrainTrust, free

This article is public. A free BrainTrust account opens every Insight, the 13 Sample Deliverables, the full Mock SEC Cyber Exam and the core compliance briefs. Name and email, no card.

Create Free Account →
Outside Testing

Want an outside test of your program? One-time engagements are available only to BrainTrust Premium members →