Opening Scenario
On October 23 2024 the Office of the Comptroller of the Currency (OCC) released Bulletin 2024‑07 – Data Classification and Critical Asset Identification Guidance (OCC 2024‑07). The bulletin, published in the Federal Register link, requires every national bank and federal savings association to adopt a formal Data Classification Guidance taxonomy and to explicitly identify the data assets that are critical to core operations.
The guidance became effective December 1 2024, giving banks just over a month to align policies, processes, and technical controls before the next scheduled OCC examination cycle. The OCC highlighted recent examiner findings where banks could not demonstrate a clear linkage between data repositories and essential business processes, resulting in “significant examination findings” and corrective‑action plans.
The core thesis is simple: without a disciplined classification framework that isolates critical data assets, banks cannot reliably prove to examiners that they have the controls, monitoring, and resilience mechanisms needed to protect the most mission‑essential information.
Problem
Banks traditionally store customer, transaction, and risk data across legacy core systems, third‑party SaaS platforms, and ad‑hoc data lakes. That architectural sprawl makes it difficult to answer two examiner‑level questions that now appear on every OCC worksheet:
- Which data sets are essential for the continuity of core banking services?
- How are those data sets protected, monitored, and backed up in accordance with the bank’s risk appetite?
In practice, many institutions still rely on informal spreadsheets or undocumented naming conventions to flag “important” data. Those approaches break down when data moves across cloud environments, when new fintech partners are onboarded, or when a merger adds duplicate data stores. The OCC bulletin explicitly calls out “inconsistent data classifications” and “absence of a documented critical‑asset matrix” as recurring deficiencies that have led to examination findings in 2022‑2023.
The regulatory impact is twofold. First, banks must produce a Data Classification Matrix that maps every data element to one of the OCC‑defined categories – Public, Internal, Confidential, or Restricted – and annotate whether the element constitutes a critical asset. Second, the matrix must be tied to an Asset‑Criticality Register that links each critical data set to the business function it enables (for example loan origination, payments clearing, or fraud detection). Failure to produce these artifacts on request will result in a “significant finding” and potentially higher supervisory ratings.
Beyond examiner scrutiny, the lack of a robust classification regime inflates operational risk. Data‑loss incidents become harder to contain because teams cannot quickly isolate the most sensitive or mission‑critical records. Incident response plans that treat all data uniformly often allocate resources inefficiently, leading to prolonged outages for services that depend on those critical assets. Moreover, without clear ownership and control mapping, banks may inadvertently violate privacy regulations such as the Gramm‑Leach‑Bliley Act or the Fair Credit Reporting Act, exposing them to civil penalties.
A well‑executed Data Classification Guidance program therefore protects both regulatory compliance and operational continuity.
The CoComply Approach
CoComply helps banks meet the OCC’s Data Classification Guidance with a three‑phase methodology that combines automation, policy enforcement, and continuous monitoring.
1. Discovery & Inventory – Automated agents scan on‑prem servers, cloud storage buckets, and SaaS applications to build a complete inventory of data objects. Each object is enriched with metadata such as data owner, format, access frequency, retention schedule, and encryption status. The inventory refreshes nightly to capture new data created after the December 1 deadline and to flag orphaned files that lack stewardship. This ongoing discovery ensures that even data created in rapid‑deployment cloud projects is captured and classified promptly.
2. Classification Engine – A rule‑based engine applies the OCC’s four classification levels to every data object. Banks can define custom rules; for example, any table containing social security numbers is automatically marked Restricted, while marketing contact lists are classified as Public. The engine also runs a risk‑scoring model that evaluates transaction volume, regulatory relevance, and the business process supported, surfacing the most likely candidates for the Critical Asset Register.
The model can be tuned to prioritize assets that support high‑value services such as loan origination or real‑time payments, ensuring that the most impactful data receives the strongest controls.
3. Governance Dashboard – A real‑time UI visualizes the classification matrix, maps critical assets to business functions, and flags gaps where no steward is assigned or where controls are missing. Data stewards can approve classifications, attach supporting documentation, and generate examiner‑ready reports directly from the dashboard. The dashboard also includes a built‑in checklist that mirrors the OCC worksheet, covering ownership, control mapping, business impact, and review cadence. This alignment removes manual transcription errors and gives examiners a single source of truth during onsite visits.
Integrated Controls Supporting OCC Requirements
- Ownership – Every data object has a designated steward recorded in an immutable audit log. Steward assignments can be bulk‑imported from HR directories, reducing administrative overhead. * Control Mapping – The platform automatically verifies encryption at rest and in transit, enforces role‑based access controls, and continuously monitors activity logs for each classification tier. Any deviation triggers an alert. * Business Impact – CoComply quantifies the financial, reputational, and regulatory impact of data loss for each asset and links that assessment to the Asset‑Criticality Register.
This quantification satisfies the OCC’s demand for a risk‑based justification of classification levels. * Review Cadence – Automated annual reviews re‑run the discovery engine, compare the new inventory with the prior matrix, and surface any drift. Review findings are compiled into a draft worksheet that senior management can sign off before the examination deadline.
Continuous Monitoring – Alerts fire when a data object’s classification changes without approval, when unauthorized access is detected, or when a critical asset is moved to an unapproved environment.
Versioned Policy Management – Every classification decision is recorded in an immutable audit log, allowing auditors to trace the evolution of a label and proving that banks have exercised due diligence.
Third‑Party Integration – Connectors for AWS S3, Azure Blob, Google Cloud Storage, Snowflake, Salesforce, and other common platforms ensure the classification scope is truly enterprise‑wide.
Scenario‑Based Testing – Simulated breach drills test whether critical‑asset protections hold under ransomware, insider threat, and cloud‑outage scenarios, providing evidence for the OCC’s resilience expectations.
Regulatory Reporting Automation – Pre‑built templates populate the OCC worksheet directly from the Governance Dashboard, eliminating manual data entry errors and accelerating the preparation of the Data Classification Matrix and Asset‑Criticality Register.
By embedding classification logic into the data lifecycle, CoComply guarantees that new data created after December 1 2024 automatically inherits the appropriate label and critical‑asset flag. The platform’s audit‑trail export satisfies the OCC’s evidence‑submission requirements, dramatically reducing the time needed to assemble examination packets and freeing staff to focus on remediation rather than paperwork.
Closing Insight
The OCC’s Data Classification Guidance transforms a long‑standing best practice into a regulatory must‑have. Banks that treat classification as a one‑time checklist risk costly examination findings and operational blind spots. Those that embed a systematic, automated framework, like the CoComply solution, gain continuous visibility into which data truly powers their core services, enabling faster remediation, stronger resilience, and smoother examiner reviews.
Bottom line: Identify, classify, and protect your critical data assets now, or face a regulator‑driven sprint to compliance after the December 1 deadline.
