M-17-12 made the privacy official the federal breach lead and wrote the contract terms agencies had to add

OMB’s January 3, 2017 breach memo gave the privacy official the lead, the agency head the call on notice, and contracts the forensic duties. Later guidance kept those roles. No government-wide breach clause followed; a 2025 FAR proposal for controlled unclassified information was still pending.

Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.

Two-minute summaryThe dek and the first sentence of each section, quoted from the article

OMB’s January 3, 2017 breach memo gave the privacy official the lead, the agency head the call on notice, and contracts the forensic duties. Later guidance kept those roles. No government-wide breach clause followed; a 2025 FAR proposal for controlled unclassified information was still pending.

  1. The week The memo described three things it contained.
  2. Who decides: the privacy official leads and the agency head decides on notice M-17-12 gave the breach response plan to the SAOP.
  3. What counts and who reports: a broad definition and a duty on everyone with access Two features of that wording widened the net.
  4. How harm is weighed: three factors and a division of labor M-17-12 required the SAOP to conduct and document an assessment of the risk of harm to the people affected, working with the team where applicable. [1] The harms it listed went past money.
  5. Who outside the agency is bound: contractors, grantees and other agencies The memo listed the minimum terms.
  6. How the memo lands on different public bodies M-17-12 applied to executive departments and agencies. [1] Its effect still varied with an agency’s size and how much of its work ran through others.
  7. Objections, in order The memo did not put containment under the SAOP.
  8. What CIOs, CISOs and privacy officials could check The checks below follow the four parts.
  9. With hindsight M-17-12 lasted.

The week

On January 3, 2017, the Director of the Office of Management and Budget issued Memorandum M-17-12 to the heads of executive departments and agencies. [1] Its subject was preparing for and responding to a breach of personally identifiable information, or PII. [1] It set the policy agencies were to follow before, during and after a breach. [1]

The memo described three things it contained. It set a framework for assessing and mitigating the risk of harm to people affected by a breach. [1] It gave guidance on whether and how to notify them and offer services. [1] And it required common standards and processes, while leaving agencies room to tailor each response to the facts. [1]

M-17-12 replaced four earlier OMB documents. It rescinded M-07-16 of May 22, 2007, OMB’s earlier memo on safeguarding against and responding to PII breaches. [1] It also rescinded identity theft notification recommendations of September 20, 2006, M-06-19 of July 12, 2006, and M-06-15 of May 22, 2006. [1] OMB said the new memo updated its breach policies in line with the Federal Information Security Modernization Act of 2014. [1]

That statute, Public Law 113-283, had been approved on December 18, 2014. [3] It directed the OMB Director to keep data breach notification policies updated. [3] It required notice to named congressional committees no later than 30 days after an agency discovered an unauthorized acquisition or access. [3] It required notice to affected individuals as expeditiously as practicable and without unreasonable delay. [3] It also let the Attorney General, the head of an intelligence element or the Secretary of Homeland Security delay notice for law enforcement, national security or remediation reasons. [3]

FISMA 2014 added a separate track for major incidents. Agencies were to notify the committees not later than seven days after there was a reasonable basis to conclude that a major incident had occurred. [3] OMB had defined the term in M-17-05, its guidance of November 4, 2016. That fiscal year 2016-2017 FISMA guidance said an unauthorized modification of, deletion of, exfiltration of or access to the PII of 100,000 or more individuals constitutes a major incident. [2] M-17-12 pointed to that guidance for congressional reporting. [1]

The memo named its main audience. That was the Senior Agency Official for Privacy, or SAOP, together with the officials and staff who evaluate the risk of harm. [1] It said sections were also relevant to the Chief Information Officer, the senior agency information security officer and IT and cybersecurity staff. [1] It drew a line around its own scope. It did not set policy on information security, threat detection, containment, evidence collection or other parts of managing a cyber incident. [1]

OMB framed the policies as a floor. The memo called them the minimum requirements for responding to a breach, and said agencies could impose stricter standards. [1] It applied to federal information and information systems as FISMA defines them, and not to national security systems, though their operators were encouraged to apply it. [1]

The memo cited its own figures for why the update was needed. It said incidents reported by agencies to the US-CERT at the Department of Homeland Security rose 27 percent between fiscal years 2013 and 2015. [1] It cited Federal Trade Commission data showing identity theft made up 16 percent of more than 3 million complaints in 2015. [1] It also listed uses of stolen PII beyond credit fraud, among them seeking employment, obtaining prescription drugs, claiming benefits and filing false tax returns. [1]

Finally, M-17-12 set deadlines. Within 180 days of issuance, each SAOP was to update the agency’s breach response plan and send it to OMB. [1] The Federal Acquisition Regulatory Council was to work promptly on contract clauses for contractor breach response, in coordination with OMB. [1] DHS was to update the US-CERT incident notification guidelines and forms. [1] The memo was published in the first week of 2017, and every one of those tasks lay ahead. [1]

Breach memos are easy to read as notification rules. M-17-12 did more work than that. It decided who in an agency owned a breach, what counted as one, how harm would be judged and who outside the agency had to help. [1] Its answers moved the center of breach response away from the security operations center.

Our argument is that M-17-12 made a breach a privacy decision with contractual reach. The security team still detected and reported incidents. [1] But the privacy official led the response, the agency head decided on notice, and contracts and grants had to carry the agency’s duties to outside parties. [1] For a CIO or CISO, that meant the breach plan was not the security team’s document to own alone.

We take the memo in four parts, one for each decision it allocated:

  1. Who decides: the privacy official leads, and the agency head decides on notice.
  2. What counts and who reports: a broad definition of breach and a duty on everyone with access.
  3. How harm is weighed: the factors the memo required, and who assesses each.
  4. Who outside the agency is bound: contractors, grantees and other agencies.

Each part covers a different question, and together they cover the memo’s operative requirements. After them we look at how the memo lands on different kinds of public bodies, take the strongest objections in order, and end with checks a CIO, CISO or privacy official could run.

Who decides: the privacy official leads and the agency head decides on notice

The lead role moved to privacy

M-17-12 gave the breach response plan to the SAOP. The SAOP was to develop and implement it, and the plan had to be part of the agency’s formal incident response plan. [1] The plan was to be tailored to the agency’s missions, size, structure and functions. [1]

The breach response team followed the same logic. The head of the agency designated the team, and once convened, the SAOP led it. [1] The SAOP also decided, on each report, whether staff could handle the response or the team had to meet. [1] The team had to meet whenever a breach was a major incident. [1]

The minimum membership shows the intended balance. The team had to include the SAOP, the CIO or a designee and the senior agency information security officer. [1] It also had to include legal counsel, a legislative affairs official and a communications official. [1] Four of those six seats belong to functions outside technology, and one of them speaks for the agency to Congress.

The memo listed others the team might consult. They included budget and procurement staff for breaches involving contractors, human resources for misconduct, law enforcement and physical security. [1] That list reads as a map of the agency, not of the network. A breach that starts with a lost box of files touches different people from one that starts with an intrusion, and the memo expected the team to reach them. [1]

The final call stayed with the agency head

The memo placed one decision above the team. The head of the agency was responsible for deciding whether to notify people, offer guidance and provide services. [1] The team advised the head on responding effectively and efficiently. [1]

This split matters for timing. Notification had to be as expeditious as practicable and without unreasonable delay, consistent with FISMA. [1] [3] Yet the memo also told agencies to avoid multiple notices for one breach and to balance speed against confirming facts. [1] Someone has to weigh those two instructions in each case. M-17-12 put that weight on the head, advised by the SAOP.

Only three officials could formally delay notice to individuals. The Attorney General, the head of an intelligence community element or the Secretary of Homeland Security could do so if notice would disrupt an investigation, endanger national security or hamper remediation. [1] [3] An instruction to delay went to the head of the agency. [1] A component’s own security staff could not create that delay on their own authority.

What the security office kept

The memo did not sideline security. It required each breach response plan to identify the agency’s principal security operations center. [1] That center notified US-CERT of a breach under the agency’s incident policy and the US-CERT guidelines. [1] The agency also had to assess whether a breach was a major incident and report that designation as soon as it had a reasonable basis to conclude one had occurred. [1]

The SAOP had to make sure the people staffing that center were trained to identify a breach. [1] At the end of each quarter, the center had to report to the SAOP on the status of each breach reported to it, and the SAOP had to validate the report. [1] So the reporting line ran in both directions. Security fed the privacy official, and the privacy official checked what security recorded.

Technical response remained the agency’s job. US-CERT could help assess causes and take corrective action within its scope, but the memo said the agency was responsible for full remediation and forensic analysis. [1] The CIO had to identify the remediation and forensic capabilities inside the agency and which offices maintained them. [1] Where it found gaps, the memo said the CIO should talk to the Chief Acquisition Officer about contracts or other options. [1]

The cadence the plan imposed

M-17-12 also set a rhythm for the people it named. The plan had to identify who would notify and consult law enforcement, the Office of Inspector General and the Office of General Counsel. [1] When a breach warranted a report to law enforcement, the report had to be prompt even if the breach was unconfirmed. [1]

Review came at three intervals. Each quarter, the security operations center reported the status of every breach to the SAOP. [1] After any breach reported to Congress, the SAOP had to convene the team for a formal lessons-learned review and document resulting changes. [1] At the end of each fiscal year, the SAOP reviewed the year’s reports and the plan itself. [1]

The annual review had a defined menu. The SAOP was to consider updating the plan, writing or revising policies, improving training, changing information sharing arrangements and revising privacy documents. [1] The SAOP had to document the date of the latest review and submit the plan to OMB when asked as part of FISMA reporting. [1]

Exercises were mandatory. The SAOP had to convene the team for a tabletop exercise periodically and at least once a year. [1] The memo said the purpose was to test the plan, make sure members knew their roles and find weaknesses. [1] The annual FISMA report then had to confirm that team members took part, or explain why not. [1]

The FISMA report carried the rest of the evidence. Agencies had to submit counts of breaches reported internally, to US-CERT and to Congress, and the number of people potentially affected. [1] They had to submit the plan, certify its review in the past 12 months, and list the team’s members and any changes. [1] In our reading, those items turned the plan from a document into a record that oversight bodies could test.

What counts and who reports: a broad definition and a duty on everyone with access

The definition

M-17-12 defined a breach as a type of incident. [1] The definition covered the loss of control, compromise, unauthorized disclosure, unauthorized acquisition or any similar occurrence. [1] It applied where someone other than an authorized user accessed or potentially accessed PII. [1] It also applied where an authorized user accessed or potentially accessed PII for an other than authorized purpose. [1]

Two features of that wording widened the net. The word “potentially” meant a breach did not require proof that anyone saw the data. [1] The second limb meant an employee with legitimate access could cause a breach by looking for the wrong reason. [1] The memo gave the example of an employee looking up a celebrity’s file out of curiosity. [1]

The memo also said a breach was not limited to network intrusions. It listed lost or stolen laptops and storage devices, misdirected email, a lost box of documents, overheard conversations and PII posted on a public website by mistake. [1] It noted that an occurrence might first be identified as an incident and later as a breach once PII was found to be involved. [1]

The duty to report

Every individual with access to agency information and systems had to report a suspected or confirmed breach as soon as possible and without unreasonable delay. [1] That covered paper, oral and electronic forms. [1] People were told not to wait for confirmation, because delay could cost the chance to wipe a device remotely or recover a document. [1]

The memo backed the duty with mechanics. Agencies were to make reporting quick and easy from the office, from telework and while traveling. [1] They were to consider a memorable email address or toll-free number for incident reports. [1] Their rules of behavior had to state the consequences of failing to report, and staff and contractors had to agree to those rules before getting access. [1]

Training was the third mechanism. Each agency had to train everyone with access on how to identify and report a breach, before they got access. [1] That included detailees, contractors, grantees, volunteers and interns. [1] The memo called annual training a baseline and suggested specialized training for supervisors and people responsible for high value assets. [1]

The narrow exception

The memo allowed a small zone where reporting was not required. The SAOP could issue guidance on such circumstances, but only where the risk of harm was negligible and not reporting would not violate law or regulation. [1] The SAOP had to assess the risk of harm before issuing that guidance, and the agency had to document the circumstances in its incident management policy. [1]

That exception is narrow by design. It covers only circumstances the SAOP has assessed in advance and written down. [1]

That exception is the one place where the memo invited agencies to set their own threshold. It came with conditions that made the SAOP answerable for it. [1] In our reading, the design was deliberate. A broad duty to report keeps information flowing, and a documented exception keeps the volume manageable without letting each office decide privately on its own.

The congressional track

A breach could also trigger reporting to Congress, under a test separate from the harm assessment. Agencies had to notify the appropriate committees no later than seven days after there was a reasonable basis to conclude that a breach constituting a major incident had occurred. [1] [3] They then had to supplement that notice with a report no later than 30 days after discovering the breach. [1]

The committees were listed in a footnote. They included oversight, homeland security and science committees in the House, homeland security and commerce committees in the Senate, both judiciary committees and the relevant authorizing and appropriations committees. [1] The breach plan had to name the officials responsible for those notices. [1]

OMB’s major-incident test was in M-17-05. A breach was a major incident if compromising the PII was likely to cause demonstrable harm to national security, foreign relations or the economy. [2] Likely demonstrable harm to public confidence, civil liberties or public health and safety also counted. [2] Compromise of the PII of 100,000 or more people met the test automatically. [2] M-17-05 said that analysis was distinct from the assessment of risk of harm to individuals. [2]

That separation matters for planning. A breach of 500 records about informants falls far below the 100,000-person line, yet could need a full harm response. It would reach Congress only if it met M-17-05’s separate test of likely demonstrable harm. A breach of 150,000 low-sensitivity records meets the 100,000-person test, so it needs congressional notice within seven days, and could need only a modest response to individuals. Both outcomes follow from the two tests as written. [1] [2]

How harm is weighed: three factors and a division of labor

The factors

M-17-12 required the SAOP to conduct and document an assessment of the risk of harm to the people affected, working with the team where applicable. [1] The harms it listed went past money. They included blackmail, disclosure of private facts, emotional distress, exposure of contact details for victims of abuse and humiliation. [1]

The memo set three factors as a minimum. The first was the nature and sensitivity of the PII. [1] The second was the likelihood of access and use, including whether the data was encrypted or otherwise made inaccessible. [1] The third was the type of breach, including the circumstances, the actors and their intent. [1]

Each factor had sub-factors. Sensitivity covered data elements, context, private information, vulnerable populations and permanence. [1] Likelihood covered security safeguards, format and media, duration of exposure and evidence of misuse. [1] Type of breach covered intent and the recipient. [1]

Who assesses what

The memo did not leave every sub-factor to the SAOP. For security safeguards, it said the CIO shall evaluate the implementation and effectiveness of the safeguards protecting the information. [1] For encrypted data, the CIO, working with the SAOP and CISO, had to confirm whether encryption was in effect, its degree, the level at which it applied and whether keys were controlled. [1]

That allocation turns a technical fact into an input to a privacy decision. Whether a stolen laptop was encrypted at the device or file level, and whether its keys were exposed, changes the likelihood factor. [1] The memo noted that protection can be undermined if keys, credentials or authenticators are compromised. [1] A security team that cannot answer those questions quickly slows the whole assessment.

The other likelihood sub-factors were practical. On format and media, the memo contrasted a spreadsheet on a USB drive, searchable by anyone, with one tape out of a set of 30 holding unstructured data. [1] It added that very valuable PII may be worth the effort to extract whatever its format. [1]

On duration, it compared a briefcase recovered from a hotel lobby after an hour with one recovered after three days. [1] It made the same point about PII posted to a public web page for an hour or for a week. [1] On evidence of misuse, it allowed both directions. Law enforcement might find the data offered for sale, or forensic analysis might show a recovered device was never accessed. [1]

Type of breach turned on intent and recipient. Where intent was unknown, the SAOP was to consider the possibility that the breach was intentional. [1] Where the recipient was a known employee inside the agency’s network, the memo said it might be reasonable to conclude the risk of harm was negligible. [1]

Some sub-factors need records only the privacy office holds. Context depends on the purpose for which the PII was collected. [1] The memo’s example was a list of office phone numbers, which becomes sensitive when it lists people in sensitive law enforcement positions. [1] The breach plan also had to make the SAOP identify which system of records notices, privacy impact assessments and notices applied to the information. [1]

Aggregation and permanence

Two sub-factors stand out for agencies holding large datasets. The memo told the SAOP to assess data elements together as well as one by one. [1] Date of birth, place of birth, address and gender might not be sensitive alone but pose greater risk combined. [1] It also told the SAOP to consider information exposed in earlier breaches that could be combined with the new one. [1]

Permanence asked whether the data could be replaced. A health insurance number can be reissued; family health history cannot. [1] The memo gave special attention to biometrics, saying future science could create uses not yet contemplated. [1] An agency that holds fingerprints or DNA faces a harm assessment that a credit card issuer does not.

The memo’s list of vulnerable populations was broad. It included children, active duty military, officials in sensitive positions, senior citizens, people with disabilities, informants, witnesses, certain immigrant populations and victims of certain crimes. [1] An agency serving any of those groups had to weigh their exposure as part of the assessment. [1]

From assessment to response

The assessment drove what came next. Mitigation could include countermeasures, guidance to affected people and services such as identity monitoring. [1] Where an agency bought those services, the memo pointed it to the GSA identity protection blanket purchase agreements required by M-16-14, except in limited circumstances. [1]

Notices had a minimum content. They had to describe what happened, including the dates of the breach and its discovery, and the types of PII involved. [1] Where helpful and safe, they had to say whether the information was encrypted or otherwise protected. [1] The memo asked for concise notices and, where needed, different versions for different affected groups. [1]

Who outside the agency is bound: contractors, grantees and other agencies

Contract terms

M-17-12 required agencies to include contract terms needed to respond to a breach. [1] The duty applied when a contractor collected or maintained federal information for the agency or operated a system on its behalf. [1] It extended to cooperative agreements and similar instruments that had another entity perform those functions. [1]

The memo listed the minimum terms. Contractors had to cooperate and exchange information with agency officials to report and manage a breach. [1] Contractors and subcontractors at any tier had to encrypt PII as OMB Circular A-130 required, train their staff and report suspected or confirmed breaches in any medium. [1]

The forensic terms were demanding. Contractors and subcontractors had to maintain the capability to determine what federal information was or could have been accessed and by whom. [1] They had to be able to construct a timeline of user activity, determine the methods used and identify the initial attack vector. [1] The contract also had to allow inspection, investigation and forensic analysis. [1]

One term protected contractors. Contracts were to say that reporting a breach was not, by itself, evidence that the contractor had failed to safeguard PII. [1] That clause aimed at a known tension. A contractor that fears a report will be read as an admission has a reason to wait, and the memo wanted reports early. [1]

Uniformity and approval

The memo asked for consistent clauses across each agency. The Chief Acquisition Officer, with the SAOP, was to make breach provisions uniform and consistently included. [1] The memo warned that a lack of uniformity would complicate breach response. [1] The SAOP and CIO also had to define contractor roles in the breach plan and in system security authorization documents. [1]

A contractor could be asked to notify affected people, run call centers or provide resources. [1] But when a contractor notified people for an agency, it had to follow OMB guidance and the agency plan, with prior written approval from the agency head. [1] The decision on notice stayed where part one put it.

Grants and other agencies

Grant recipients were covered in a separate clause. Where a recipient used or operated a federal system or handled PII within the scope of a federal award, the agency had to make sure the recipient had breach response procedures. [1] The award terms had to require the recipient to notify the awarding agency of a breach. [1]

The memo also reached across agencies through the Privacy Act. The SAOP had to make sure every system of records notice included routine uses for disclosures needed to respond to a breach. [1] One routine use covered the agency’s own breach. The other let it share records to help another agency respond to a breach. [1] The memo gave suggested wording for both. [1]

The breach plan had to address information sharing too. The SAOP had to consider whether sharing fit existing data use agreements or needed new ones, and how shared PII would be protected and retained. [1] A breach can require an agency to combine data from different systems, or obtain it from another agency, simply to find and contact the people affected. [1]

The memo also asked whether that extra PII would itself need new or revised notices or impact assessments. [1] An agency that discovers in the middle of a breach that it cannot lawfully use a contact database has lost days. The routine uses and the sharing review were meant to settle those questions before a breach, not during one. [1]

The clause the FAR Council was asked to write

M-17-12 did not leave the contract terms to each agency forever. It directed the FAR Council, with OMB, to work promptly on contract clauses and regulatory coverage for contractor breach response. [1] In our reading, until such clauses existed in the FAR, the duty to write them fell on each agency’s own contracts. [1] That left agencies drafting their own versions of the same eight terms.

How the memo lands on different public bodies

M-17-12 applied to executive departments and agencies. [1] Its effect still varied with an agency’s size and how much of its work ran through others.

A large department with many components

A large department could let components write their own plans. With SAOP approval, a sub-agency or component could adopt its own breach plan, consistent with the agency plan. [1] The SAOP had to review those plans at least annually and document the review date. [1] For a department with many components, the work is coordination: one definition, one escalation path and several plans that agree.

Such a department also has more contracts to amend. The memo’s call for uniform clauses through the Chief Acquisition Officer is easier to meet with a central acquisition office than with buying spread across components. [1]

A small agency

A small agency faced the same minimums with fewer people. Its team still needed the six required members, and the memo acknowledged that a large breach can take hundreds of hours of effort. [1] The CIO might find no internal forensic capability and have to arrange contracts in advance. [1] The memo pointed agencies to US-CERT for technical help and to GSA vehicles for incident response services. [1]

A contractor running agency systems

For a contractor, the memo arrived through contract modifications. The forensic capability terms meant logging, retention and analysis capacity sufficient to build a timeline of user activity and find the initial attack vector. [1] A contractor serving several agencies could face several versions of those terms until a single FAR clause existed. [1]

A state agency or grantee

M-17-12 did not regulate state agencies directly. It reached them where they received federal awards that involved federal systems or PII within the award’s scope. [1] In those cases the award terms required breach procedures and notice to the federal agency. [1] A state program office then answers to its own state breach law and to the federal award terms, which may set different triggers.

An inspector general reviewing the agency

For an inspector general, the memo created a trail to audit. The plan had to be submitted with the annual FISMA report and certified as reviewed within 12 months. [1] The team roster, with additions and removals, went in the same report. [1] Tabletop participation had to be confirmed or explained. [1]

Each breach also left records. The memo’s section on tracking required agencies to document the response to each breach, including whether services were provided and whether the breach was reported to US-CERT or Congress. [1] A reviewer can compare those records with the plan’s escalation criteria and see whether the agency followed its own rules.

The same trail serves the agency. An SAOP who can show that a decision not to notify rested on a documented harm assessment is in a stronger position than one who cannot. [1] The memo did not say so in those words. It follows from the documentation it required.

Objections, in order

1. A privacy-led response slows down containment

The memo did not put containment under the SAOP. It expressly left information security, containment and threat response outside its scope. [1] The principal security operations center still reported to US-CERT, and the CIO still owned forensic capability. [1] What the SAOP led was the response to the people affected: assessment, mitigation and notice. [1]

2. The definition of breach is too broad to manage

A definition that counts potential access and misuse by authorized users will capture many small events. The memo answered with escalation, not narrowing. The SAOP decided case by case whether staff could handle a report or the team had to meet. [1] The documented exception for negligible-risk circumstances also existed. [1] The breadth served reporting; the triage served workload.

3. Agency-by-agency contract terms are a poor substitute for a regulation

This objection has force, and the memo agreed with part of it. It asked the FAR Council to create clauses because non-uniform terms would complicate response. [1] Until then, agencies had to include the terms themselves. [1] The memo chose a working duty now over waiting for a rule.

4. The memo is guidance and creates no rights

M-17-12 said it did not create any right or benefit enforceable at law against the United States. [1] That limits what affected individuals can do with it. It does not limit what OMB can ask of agencies. FISMA required agencies to describe their implementation of the memo in annual reports, and the memo listed what those reports had to contain. [1] [3]

5. Agencies had breach plans already

They did, under M-07-16 and the 2006 memos the new one rescinded. [1] The change was in what the plan had to contain and who owned it. M-17-12 added required team members, a documented harm assessment, contract and grant terms, routine uses, tabletop exercises and annual reporting. [1] It also tied the plan to FISMA’s 2014 reporting duties. [1] [3]

6. Identity monitoring will be bought by reflex whatever the assessment says

The memo treated services as one possible outcome of the assessment, not a default. [1] Its mitigation section listed countermeasures, guidance and services as separate options. [1] It also routed purchases through GSA blanket purchase agreements under M-16-14, which limits how each agency buys. [1] Whether agencies used the discretion is a question for their records. The memo itself asked them to choose.

What CIOs, CISOs and privacy officials could check

The checks below follow the four parts. They are good practice drawn from the memo’s structure, not additional requirements.

  • Does the incident response plan name the principal security operations center and show how it hands a suspected breach to the privacy official? [1]
  • Does the breach team roster include all six required roles by name, and was it updated in the last year? [1]
  • Can the security team answer the encryption questions the memo assigns to the CIO, such as level of encryption and key control, within hours for a given device or system?
  • Do current contracts for systems that hold PII carry the forensic capability terms, including a timeline of user activity and the initial attack vector? [1]
  • Confirm that grant terms for programs that handle PII require notice to the awarding agency. [1]
  • Confirm that the rules-of-behavior form staff and contractors sign before access states the consequences of failing to report a suspected breach. [1]
  • Publish a short, memorable reporting address or toll-free number, and test whether people on travel or telework know it. [1]
  • Do the agency’s system of records notices carry both breach routine uses, so it can share records to respond to its own breach and to help another agency? [1]

Two further checks are about evidence. The memo required at least one tabletop exercise a year and confirmation of it in the annual FISMA report. [1] It also required a formal lessons-learned review whenever a breach was reported to Congress. [1] An agency that keeps the exercise records and the lessons-learned documents can show an inspector general what changed as a result.

A last check concerns thresholds. The memo’s definition of breach and OMB’s separate major-incident threshold answer different questions. [1] [2] One decides whether to assess harm; the other decides whether to tell Congress quickly. A response plan that blurs them risks either missing a congressional deadline or treating every small breach as a crisis.

With hindsight

M-17-12 lasted. OMB’s fiscal year 2025 FISMA guidance, M-25-04 of January 15, 2025, still defined “breach” by reference to section III(C) of M-17-12. [4] It applied that definition throughout. [4] M-25-04 rescinded its fiscal 2024 predecessor, M-24-04, but left M-17-12 in place as the source of breach policy. [4]

The roles held as well. M-25-04 said CIOs, CISOs and SAOPs must coordinate on the agency head’s annual FISMA letter, including reporting on breaches. [4] It pointed to the roles for tracking and documenting breaches set out in section VIII of M-17-12. [4] When a breach is a major incident, M-25-04 said the principal security operations center and the SAOP must coordinate on tracking and documenting it under M-17-12. [4]

The reporting clock moved to the agency. M-17-12 had asked agencies to report a major-incident designation to US-CERT as soon as they had a reasonable basis to conclude one had occurred. [1] M-17-05 had given DHS one hour to notify OMB after an agency told DHS of a major incident. [2] M-25-04 required agencies themselves to report to CISA and the OMB Federal CIO’s office within one hour of determining that a major incident had occurred. [4] It kept the 100,000-person threshold for a breach that is a major incident. [4] It also kept the separation M-17-05 had drawn: the analysis for reporting a major breach to Congress is distinct from the assessment of risk of harm to individuals. [2] [4] For the second, M-25-04 referred agencies to M-17-12. [4]

The contract clauses took a longer road. M-17-12 had asked the FAR Council to work promptly on breach response clauses. [1] On January 15, 2025, the FAR Council proposed a rule in FAR Case 2017-016 to apply the controlled unclassified information program to federal contracts. [5] Comments were due by March 17, 2025. [5]

That proposal’s incident terms echo M-17-12. On discovering a suspected incident involving controlled unclassified information, a contractor would have to determine what was or could have been improperly accessed, construct a timeline of user activity and determine methods and techniques used. [5] For CUI outside a federally controlled facility, it would have to report suspected or confirmed incidents within 8 hours of discovery. [5] The wording of the capability terms is close to the memo’s contract list. [1] [5]

The two are not the same instrument. M-17-12 dealt with PII. [1] The proposed rule defined a CUI incident as suspected or confirmed improper access, use, disclosure, modification or destruction of controlled unclassified information. [5] In our reading, the proposal would standardize much of the forensic capability M-17-12 asked contractors to keep, for a category of information defined by the CUI program.

The FAR Council’s regulatory agenda published on September 22, 2025 listed the case at the final rule stage. [6] It said the Council had received comments on the January 2025 proposal and was considering them in developing the final rule. [6] It projected a final rule for December 2025. [6] As checked on November 15, 2026, we found no final rule in FAR Case 2017-016 in the Federal Register.

So the outcome splits along the memo’s own parts. The governance parts, who decides and what counts, carried forward into later OMB guidance with little change. [4] The harm assessment remained the reference point for decisions about individuals. [4] The contractual part still rested, as checked, on agency contract terms and a proposed government-wide clause. [1] [5] [6]

What held up best was the decision to name owners. M-25-04 relied on the coordination roles M-17-12 assigned instead of rebuilding them. [4] What held up least was the expectation of a prompt government-wide clause. [1] Agencies and contractors that wrote the memo’s terms into contracts in 2017 had the protections the memo described. Those that waited for the FAR were still waiting, as checked on November 15, 2026. [6]

Spotted an error? Tell us and we will check it and correct the article where needed.

  • OMB M-17-12
  • breach response
  • FISMA
  • privacy officials
  • federal contractors
  • PII