The Consumer Financial Protection Bureau's (CFPB) information security program was rated ineffective in its annual cybersecurity audit for the second year in a row. Conducted by the Federal Reserve and the CFPB Office of Inspector General (OIG), the audit cited inadequate security policies and unpatched critical vulnerabilities. The data protection metrics remained at Level 2 out of 5, the same as the previous year. An effective rating requires at least Level 4.
This isn't just a federal issue. A repeat failure with no improvement is a case study in what happens when audit findings aren't turned into funded, owned, and verified remediation. For internal auditors, this conversion problem is the real focus.
What the Data Shows
Three key facts stand out. The program was ineffective for the second consecutive year. The data protection rating stayed at Level 2. The gap to reach an effective threshold is two full maturity levels, not just a minor shortfall.
A one-year miss might be a bad cycle. A flat score over two cycles suggests the initial recommendations weren't accepted, resourced, or tested for closure. This is where your audit function should focus.
Key Findings
1. A flat score signals a remediation failure, not a detection failure.
The oversight bodies identified the weaknesses, but the agency's rating didn't improve. Detection worked; correction didn't. If your audit function measures success by findings issued, you're focusing on the wrong part of the process.
2. Policy gaps and technical gaps appear together.
Inadequate security policies and unpatched vulnerabilities are listed side by side. Weak policy standards often mean no enforceable patching timelines, no defined ownership, and no escalation path when deadlines are missed. Unpatched vulnerabilities are symptoms of undefined or unenforced standards.
3. Two levels below effective is a design problem.
A gap this large isn't due to a few missed tasks. It indicates control design weaknesses needing structural fixes: clear accountability, defined processes, and monitoring that doesn't rely on individual diligence.
4. Independent oversight did its job; internal follow-through did not.
The involvement of both the Federal Reserve and the OIG shows the value of independent assessment. But independent assessors can't own remediation. Management does. Your Chief Audit Executive should ask who owns closure in your organization and whether anyone verifies it.
5. Repeat results erode institutional credibility.
An agency tasked with protecting consumers that fails its own security program two years in a row invites a trust issue. The same applies to any organization holding sensitive personal data. Stakeholders see repeat audit findings as evidence that governance isn't functioning, regardless of breaches.
What This Means for Your Team
The lesson for internal audit isn't just about federal agencies. It's about your own findings log.
Pull your last two cycles of security-related audit findings. Count how many recur, even if the wording changed. Recurrence is your most honest key control indicator for whether remediation works. If the same weakness resurfaces, the original finding was either closed on paper only or addressed at the wrong level.
Next, examine how your organization defines "closed." Many teams accept a management assertion or a submitted ticket. Effective closure requires re-performance: test the corrected compliance control and confirm it operates as designed. Without that, you're tracking activity, not risk reduction.
Finally, consider how repeat findings reach governance bodies. If recurring Severity Level 1 or 2 items stay inside audit reports and never reach the audit committee in aggregate, you have a reporting gap. Boards and committees need to see aging and recurrence, not just new issues.
Action Items by Priority
Priority 1: Establish a recurrence test on your findings.
Review prior-cycle security audit findings and flag any that repeat. Report the recurrence rate to your audit committee as a standing metric.
Priority 2: Require validated closure.
Change your closure standard so high-severity items are closed only after audit fieldwork confirms the remediated control operates effectively. Management attestation alone shouldn't suffice.
Priority 3: Trace each technical finding to its policy standard.
For any unpatched-vulnerability finding, check whether a written standard defines patch timelines by severity, assigns an owner, and specifies an escalation path. If it doesn't, fix the standard before addressing individual systems.
Priority 4: Assign named owners and dates.
Every finding needs an accountable individual and a committed date. Unowned findings are the ones that return next year at the same rating.
Priority 5: Apply risk-based audit planning to follow-up.
Don't treat follow-up as a clerical exercise. Allocate more fieldwork to areas with repeat findings and to controls protecting sensitive personal data, and record the exposure in your cybersecurity risk register.
Priority 6: Set a maturity target and track the gap.
If you use a maturity model, define your target level explicitly and report progress against it. The CFPB result shows how a score can remain unchanged when no one is accountable for moving it.
Priority 7: Maintain professional skepticism toward self-reported progress.
Management will often report remediation as underway. Test it. A plan isn't a control.





