M-16-14 made buying breach identity services off GSA’s vehicle a written case the privacy official signed
OMB’s July 1, 2016 memo named GSA’s identity protection agreements the preferred source. In our reading, its working parts were the written comparison, privacy official approval and prices-paid reports required of any agency that bought elsewhere.
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 July 1, 2016 memo named GSA’s identity protection agreements the preferred source. In our reading, its working parts were the written comparison, privacy official approval and prices-paid reports required of any agency that bought elsewhere.
- The week The memo gave some history.
- The default: a shared vehicle ready before the breach The memo’s first move was to name a preferred source.
- The exception file: a written case and a privacy official’s signature The second part is what an agency had to do to leave the default.
- The price record: contract copies and prices paid The third part concerns information flowing to the center.
- The carve-out: when a contractor provides the services The fourth part covers cases outside the memo.
- What the memo left undecided The memo answered the buying question.
- How the memo plays out across agencies The same rules land differently on different agencies.
- Objections to this reading Three objections deserve an answer, in order.
- Checks an agency leader can run now These checks follow from the memo’s structure.
- With hindsight OMB’s breach response guidance followed in January 2017.
The week
On July 1, 2016, the Office of Management and Budget issued memorandum M-16-14 to the heads of departments and agencies. [1] Its subject was Category Management Policy 16-2: Providing Comprehensive Identity Protection Services, Identity Monitoring, and Data Breach Response. [1] It was signed by the United States Chief Acquisition Officer. [1]
The memo said it updated a longstanding OMB policy, first implemented in 2006, to maximize agency use of a government-wide solution for buying identity protection services when needed. [1] It required, with limited exceptions, that agencies needing such services use the government-wide blanket purchase agreements awarded by the General Services Administration. [1] The memo called them the IPS BPAs, for Identity Monitoring, Data Breach Response and Protection Services. [1]
The memo gave some history. For the past decade, it said, GSA had offered commercial credit monitoring through government-wide BPAs under its Federal Supply Schedules program. [1] When those BPAs launched, OMB had told agencies to review their pricing and terms and to notify OMB before making an award outside them. [1] A footnote cited OMB memorandum M-07-04 for that earlier instruction. [1]
The memo said that the previous year GSA had partnered with other agencies on requirements for new BPAs. The aim was to give all agencies access to a pool of qualified contractors able to provide a comprehensive range of identity protection services, including credit monitoring. [1]
It gave reasons for using them: expeditious delivery from pre-approved and vetted companies, competitive pricing and reduced administrative costs. [1] For those reasons, it said, the IPS BPAs shall be treated as a preferred source when agencies need credit monitoring, breach response and identity protection services. [1]
GSA, as contract manager, would work with an interagency team to periodically review and refresh the contract terms and requirements. [1]
The memo then set steps, effective immediately, to ensure use of the BPAs to the maximum extent practicable. [1] An agency with an existing vehicle that overlapped the BPAs, and planning to exercise an option, had to analyze the option against the BPAs under Federal Acquisition Regulation 17.207. [1] The analysis covered terms and conditions, pricing, performance, fees and savings, and could consider the impact on an incumbent small business. [1]
If the agency exercised the option anyway, it had to give the final analysis to GSA and OMB. The Senior Agency Official for Privacy had to approve that analysis, along with any other officials named by agency policy. [1] The agency also had to submit a copy of the option and underlying contract and, at the end of the option period, the prices paid. [1]
For planned procurements, an agency considering a different vehicle had to compare it with the BPAs on scope, period of performance, terms, pricing, performance, administrative costs, customer satisfaction and small business impact. [1] Administrative cost meant the cost of staff supporting the award against the fees for using the BPAs. [1]
If the planned vehicle’s value exceeded the simplified acquisition threshold, the agency had to share a draft analysis with the Category Manager for Professional Services and OMB for a five-business-day review. [1] Approval had to come at a minimum from the Senior Agency Official for Privacy and, above the threshold, the agency’s Senior Procurement Executive. [1]
Agencies that require contractors to provide identity protection services as part of their security or safeguarding requirements were exempt from the guidance. [1] The memo noted that agencies could authorize some contractors to use GSA sources, including the BPAs, under FAR Part 51.1. [1]
M-16-14 reads as a routine category management memo. It named a preferred contract vehicle for a common service and asked agencies to use it. [1] The service was the identity protection an agency offers people after their personal information is exposed.
Our argument is that the memo’s working parts were about paper and data. Using the GSA vehicle required no extra steps. Leaving it required a written analysis on set factors, approval by the privacy official, and the sharing of contract copies and prices paid. [1] In our reading, the memo made every departure a record and every price a data point.
That matters for agency leaders because breach response is a moment of pressure. The memo set the procurement decision before the breach, so that when one came, the agency would either use the shared vehicle or already have a documented reason not to. [1]
We take the memo in four parts, each a distinct decision it shaped:
- The default: what the agency buys, from whom, when nothing special applies.
- The exception file: what an agency must write and who must sign when it chooses another vehicle.
- The price record: what contract and price information flows to GSA and OMB.
- The carve-out: when the duty falls on a contractor rather than the agency.
The parts do not overlap. The first concerns the normal path, the second the decision to leave it, the third the information that leaving it creates, and the fourth the cases outside the memo’s reach. Together they cover every way an agency could buy these services.
After the four parts we look at what the memo left undecided, how it plays out across agencies, the strongest objections, and checks an agency leader can run. The memo applied to federal departments and agencies. It did not address state or local governments, and we draw no conclusions about them. [1]
The default: a shared vehicle ready before the breach
The memo’s first move was to name a preferred source. When agencies need credit monitoring, breach response and identity protection services, the IPS BPAs shall be treated as that source. [1]
A preferred source works differently from a mandatory one. An agency may still use another vehicle, but it must justify doing so. The memo described its steps as ensuring use of the BPAs to the maximum extent practicable. [1]
Why a default helps after a breach
A breach creates urgent work: assessing what was exposed, deciding whom to notify, and arranging services if they will be offered. Buying services from scratch at that moment means writing requirements, soliciting offers and evaluating them while affected people wait.
The memo’s reasons for the BPAs addressed that pressure. It cited expeditious delivery from pre-approved and vetted companies. [1] A vehicle already competed and awarded lets the agency move to a task order. The time saved comes at the start of the response, when it matters most.
GAO later described FISMA performance metrics that OMB and DHS issued in October 2015 and October 2016. [3] They required agencies either to have contracts for identity theft services in place or to have assessed the scope, cost and time to execute one. [3] Those metrics referred agencies to the BPAs as a resource. [3] In our reading, the memo and the metrics together pushed agencies to settle the buying question before any breach.
What the vehicle covered
The memo described the BPAs as giving agencies access to contractors able to provide a comprehensive range of identity protection services, including credit monitoring. [1] Its title named identity protection, identity monitoring and data breach response. [1]
Breadth matters because the services an agency needs vary by breach. A breach of tax records, health records and background investigation files exposes different data and creates different risks. A vehicle with several kinds of service lets the agency match the response to the exposure.
Vetted suppliers and their own security
The memo said the BPAs offered pre-approved and vetted companies. [1] Vetting matters in this market because the supplier receives the personal information of the people affected. An identity protection provider handles names, Social Security numbers and contact details to deliver its service.
GAO later reported that, according to GSA, the requirements for the new BPAs were changed after the first 2015 OPM breach was discovered, to require providers to have more stringent information technology security protections. [3] A shared vehicle lets one set of security requirements apply across every agency order. An agency buying alone would need to set and check those requirements itself.
The cost of a shared default
A shared vehicle has costs too. Its terms are set for the average buyer. An agency with unusual needs, such as a population abroad or people without credit files, may find the standard services fit poorly.
The memo anticipated this. It allowed exceptions and asked agencies to highlight any unique features or requirements in their analysis of alternatives. [1] The default was strong, not absolute.
Category management as the frame
The memo was numbered as category management policy 16-2. [1] Category management treats common purchases as categories to be managed across government, with shared vehicles, shared data and shared terms.
Identity protection services fit that frame. Any agency might need them, each need is occasional, and the services are similar from one agency to the next. A shared vehicle spreads the cost of competing and managing the contract across all users. That is the economic case, in our reading, and the memo’s reference to reduced administrative costs reflects it. [1]
An order ready to place
A preferred vehicle saves time only if the agency can use it quickly. Placing an order still needs a statement of work, a warranted contracting officer, funding and an understanding of which services fit the breach.
An agency can prepare those pieces in advance. It can draft a statement of work for common breach types, name a contracting officer familiar with the vehicle, and agree with its budget office where the money would come from. The memo does not mention these steps. It follows from the memo’s purpose of expeditious delivery, in our reading. [1]
Funding deserves particular thought. Breaches are unplanned, and services for a large population can be expensive. An agency that has not identified a funding source may find the procurement ready and the money not. That gap can delay services as surely as a missing contract.
Notice and services travel together
Services only help people who know about them. OMB’s later breach guidance made the link explicit: an agency that decides to provide identity or credit monitoring would need to notify the people affected so they can use it. [2]
That link affects buying. Some service offerings include notification, call centers and websites for affected people. GSA’s current page lists call center and website services among those on its identity protection SIN. [5] An agency choosing a vehicle should consider whether it covers notice as well as monitoring, so that the two arrive together.
Breaches that cross agency lines
Some breaches affect people across agencies. A shared service, a central personnel system or a contractor serving several agencies can expose people whose relationship is with many offices at once. Each office may feel responsible for offering services.
Uncoordinated responses can buy the same service twice for the same person. GAO later found that OPM provided duplicative identity theft services for about 3.6 million people affected by both of its 2015 breaches. [3] That was one agency with two breaches. Several agencies responding to one breach face the same risk on a larger stage.
A shared vehicle helps in one respect: orders placed through it can be compared. It does not by itself stop duplication. That needs coordination about who will offer services to whom, which belongs in breach response planning. GAO recommended that OMB explore options to address duplication across agencies. [3]
Reading the memo alongside the breach response plan
The memo was a procurement document. An agency’s breach response plan is an operational one. The two meet at the moment of purchase.
In our reading, the plan should carry a short section derived from the memo: the vehicle to use, the person who orders, the factors that would justify using another vehicle, and the approvals needed. Keeping that section current, as vehicles change, is a small task that saves time when it counts. [1]
The exception file: a written case and a privacy official’s signature
The second part is what an agency had to do to leave the default. The memo split agencies into two groups: those with existing contracts and those planning new procurements. [1]
Existing contracts at the option decision
An agency with an existing vehicle overlapping the BPAs had to act at its next option decision. Before exercising an option, it had to analyze terms and conditions, pricing, performance, fees and savings against the BPAs, under FAR 17.207. [1] It could also consider the impact on an incumbent small business. [1]
Tying the analysis to the option decision used a moment that already existed. Agencies decide whether to exercise options anyway. The memo added a comparison to that decision without creating a new review cycle. In our reading, that made compliance cheaper than a standalone review would have been.
New procurements and the list of factors
An agency planning a different vehicle had to compare it with the BPAs on a set list of factors. [1]
- Scope and period of performance. [1]
- Terms and conditions, pricing and performance. [1]
- Administrative costs, comparing staff time to award and run the vehicle with the fees for using the BPAs. [1]
- Customer satisfaction, where the organization had managed a similar vehicle before. [1]
- Small business impact, if any, and any unique features or requirements. [1]
An agency planning an interagency contract also had to include a market analysis and a description of its suitability for managing the vehicle. [1]
Administrative cost as a stated factor
The administrative cost factor deserves attention. The memo asked agencies to compare the cost of full-time equivalent employees supporting their own vehicle with the fees they would pay to use the BPAs. [1]
That comparison puts a number on something agencies might otherwise ignore. A separate contract needs contracting officers, program staff and oversight. Those costs do not appear in the contract price. Writing them into the analysis makes a cheaper-looking contract carry its full cost, in our reading.
Review before the decision
Above the simplified acquisition threshold, the agency had to share a draft analysis with the Category Manager for Professional Services and OMB for a five-business-day review. [1] The reviewers could offer input. The agency then decided, after considering it. [1]
The review was short and advisory. It did not give OMB or GSA a veto. It did put the agency’s reasoning in front of people who knew the shared vehicle well, before the agency committed. A weak analysis would be visible to them.
Who signs
The memo required the Senior Agency Official for Privacy to approve the final analysis, both for options on existing contracts and for new vehicles. [1] Above the simplified acquisition threshold, the Senior Procurement Executive also had to approve a new vehicle. [1]
Putting the privacy official on the approval line is the memo’s most distinctive choice, in our reading. The memo could have routed approval through acquisition officials alone. Instead it recognized that identity protection services are part of the agency’s privacy response, and made the privacy official answerable for the choice of vehicle.
That choice also creates accountability after a breach. If an agency’s own vehicle performed poorly, the record would show who approved leaving the shared one and on what analysis. The signature turns a procurement preference into a decision someone owns.
What the file does for the agency
The exception file protects the agency as well as constraining it. An agency that departs from a preferred source without a record may face questions from auditors, inspectors general or oversight committees. An agency with a documented comparison and the right approvals can show it decided deliberately.
The file is also useful the next time. A comparison done for one option period gives the next period’s team a starting point. Over time, a series of analyses shows whether the agency’s own vehicle continues to justify itself.
What makes a comparison credible
The memo set the factors. It did not say what a good analysis looks like. In our reading, a credible comparison uses real numbers from the agency’s own past orders, states its assumptions about breach size and enrollment, and shows how the answer changes if those assumptions are wrong.
A comparison that states only that the agency’s own contract is cheaper, without saying for what population or enrollment rate, would be hard to rely on. The five-business-day review above the threshold gave reviewers a chance to ask for those details before the decision was final. [1]
The incumbent small business
The memo let agencies weigh the impact on an incumbent small business when deciding whether to exercise an option. [1] That factor reflects a broader federal policy interest in small business participation. It also creates a tension.
A preferred-source policy can move work away from small incumbents toward the vehicle’s holders. The memo did not resolve that tension. It made the agency state the impact and weigh it, with the privacy official and, for larger buys, the senior procurement executive signing off. [1]
Who reads the file later
The exception file has readers beyond OMB and GSA. An inspector general reviewing a breach response may ask how the agency chose its services and at what price. A congressional committee may ask the same after a large breach.
A file that shows the comparison, the reviewers’ input and the approvals answers those questions with documents. A file that is missing pieces leaves the agency to reconstruct its reasons after the fact. The memo’s steps, followed carefully, produce the first kind of file. [1]
The price record: contract copies and prices paid
The third part concerns information flowing to the center. Whenever an agency used its own vehicle, the memo required it to submit contract and price information. [1]
What had to be shared
An agency that exercised an option on an existing contract had to submit a copy of the option and the underlying contract vehicle. [1] At the end of the option period, it had to submit the prices paid under the option. [1]
An agency that proceeded with a new vehicle had to submit a copy of the vehicle and, at the end of the base period and each option period, the prices paid. [1] Both kinds of submission went to GSA and OMB through a shared site named in the memo. [1]
Why prices paid, not prices offered
Contract prices and prices paid can differ. A contract may price per enrolled person, while the agency pays only for those who sign up. A contract may include services the agency never orders. The memo asked for what was actually paid. [1]
In our reading, that choice gave OMB and GSA the data needed to compare vehicles on outcomes. Prices offered show what a supplier would charge. Prices paid show what the government spent for the services actually delivered. Only the second supports a judgment about value.
How pricing structures shape the record
Identity protection is priced in units of people. GSA’s current ordering guide describes two pricing methods for its total solution: a firm fixed price per year per enrollee, and a firm fixed price per year per impacted individual. [6]
The guide says the per enrollee rate fits cases where most or all affected people will enroll, such as a small, well-defined group. [6] It says the per impacted individual rate fits cases where the enrollment rate is unknown, and is not appropriate for a small breach or where enrollment will be near complete. [6]
Those choices change what prices paid mean. Under per impacted individual pricing, the agency pays for everyone notified, enrolled or not. Under per enrollee pricing, it pays for those who sign up. A comparison of prices paid across agencies needs to know which model each used, in our reading.
A refreshed contract
The memo said GSA, as contract manager, would work with an interagency team to periodically review and refresh the BPAs’ terms and requirements. [1] The price and contract data agencies submitted would inform that work.
That loop is the economic heart of category management. Agencies use the shared vehicle or explain why not. Their explanations and prices reach the contract manager. The contract manager adjusts the vehicle. The memo set up each step, though it did not report on how the loop performed. [1]
Limits of the record
A price record shows cost. It does not show whether the services helped the people who received them. The memo did not ask agencies to report enrollment rates, claims or outcomes. [1]
That gap matters because the value of identity protection depends on use and effect. A low price for a service few people use may cost more per person helped than a higher price for a service many use. The memo’s data could answer the cost question, not the value question. GAO took up the value question in March 2017. [3]
What the center can do with the data
Price and contract data in one place make comparisons possible that no single agency could make. GSA could see whether agency vehicles undercut the shared one, and on what terms. OMB could see which agencies departed and why.
Those comparisons inform the next refresh of the shared vehicle. If several agencies justify departures on the same ground, such as a missing service, the contract manager can add it. If departures cost more per person, the case for the default strengthens. The memo set up the data flow. It did not promise results from it. [1]
Enrollment as the missing number
The number that would most change the analysis is enrollment: how many affected people sign up. GSA’s guide uses enrollment expectations to choose between its two pricing methods. [6]
An agency that records enrollment after each breach builds its own evidence for the next pricing choice. An agency that does not must guess. In our reading, that record is cheap to keep and among the most useful an agency can hold for future breach buys.
An agency can close part of that gap on its own. After each breach, it can record how many people were notified, how many enrolled, and how many used restoration or insurance. Those figures, kept beside the prices paid, turn the memo’s cost record into a rough record of value for the agency’s next decision. The memo did not ask for these figures, and nothing in it stops an agency from keeping them. [1]
The carve-out: when a contractor provides the services
The fourth part covers cases outside the memo. Agencies that require contractors to provide identity protection services, or a subset of them, as part of the security or safeguarding requirements in their contracts were exempt from the guidance. [1]
Why the carve-out exists
Federal contractors hold federal information. If a contractor’s breach exposes it, the contract may require the contractor to respond, including by paying for services. In that case the contractor, not the agency, is buying.
The memo did not try to control a contractor’s own purchases. It left the contract terms in place. In our reading, that kept the memo’s rules focused on agency spending, which OMB could direct.
Letting contractors use the government’s vehicle
The memo then opened a door. Under FAR Part 51.1, agencies may at their discretion authorize certain contractors to use GSA sources, including the BPAs, when in the government’s best interest. [1] The memo named contractors under cost-reimbursement contracts, and under fixed-price contracts for protecting classified information and related equipment. [1] Agencies could also seek a deviation under FAR Subpart 1.4 for other situations where contractor access would help. [1]
That door matters for cost and quality. A contractor using the government’s vetted vehicle gets the same security requirements and pricing. Under a cost-reimbursement contract, where the government bears the cost, the government benefits from the lower price too.
What the carve-out leaves to the agency
The exemption put weight on contract terms. If a contractor must provide services after a breach, the contract should say what services, for how long, to what standard, and how the agency will oversee them.
An agency that writes vague terms may find that its contractor’s response differs from what the agency would have bought. The people affected do not care who bought the services. They care whether the services work. In our reading, the carve-out made the agency’s contract language part of its breach response plan.
Grants and other arrangements
The memo addressed contracts. It did not mention grants or cooperative agreements, under which recipients may also hold personal information collected for federal programs. [1] How an agency handles a recipient’s breach depends on the award terms and other rules, which this memo did not cover.
Contractors’ own suppliers
A contractor required to provide services after a breach must buy them somewhere. Unless the agency authorizes use of GSA sources, the contractor buys on the open market. [1]
The agency then depends on the contractor’s choice of supplier for the security of the affected people’s information. The agency can address that in the contract by requiring that any service provider meet stated security requirements, or by authorizing use of the vetted vehicle where the FAR allows. [1]
Overseeing what the contractor provides
Oversight after a contractor breach is harder than after an agency breach. The agency may not see the notices sent, the call center scripts or the enrollment numbers unless the contract requires the contractor to share them.
Contract terms can require those reports. An agency that has written them in advance can confirm that affected people were served. An agency that has not may learn of problems only through complaints. That difference is set when the contract is signed, long before any breach.
What the memo left undecided
The memo answered the buying question. It left several other questions open, and some were answered later.
Whether to offer services at all. M-16-14 governed how to buy services when needed. [1] It did not say when they are needed. That question went to OMB’s breach response guidance, issued in January 2017. [2]
Which services fit which breach. The memo described a comprehensive range of services but did not match them to types of exposure. [1] An agency had to decide whether credit monitoring, identity monitoring, restoration or insurance fit the data lost.
How much coverage to buy. The memo set no coverage periods or insurance levels. [1] Congress later did so for the OPM breaches. [4]
Whether the services worked. The memo’s data flows concerned contracts and prices. [1] It did not ask for evidence that the services reduced harm. GAO later questioned the effectiveness of some services. [3]
How the memo plays out across agencies
The same rules land differently on different agencies.
Large departments with their own vehicles
A large department with an existing identity protection contract faced the analysis at its next option. It may have had the staff to write a good comparison and the volume to justify a separate vehicle if the numbers supported one.
For such a department, the memo’s main effect was transparency. Its decision to keep its own vehicle would now be documented, signed by the privacy official, and visible to GSA and OMB with prices attached. [1]
Small agencies and commissions
A small agency may need these services infrequently and may have no contract at all. For it, the BPAs offered a ready vehicle and freed it from writing requirements under pressure. [1] The memo’s default fit the small agency’s situation most naturally, in our reading.
The small agency’s risk is unfamiliarity. If the vehicle is used once in several years, the people who know how to order from it may have left. A short internal procedure, stored with the breach response plan, keeps that knowledge.
Components inside a department
Large departments contain components with their own contracting offices and their own systems. A breach in one component may be handled by that component, by the department, or by both.
The memo addressed departments and agencies. It did not say how a department should divide the decision among its components. [1] A department can settle that internally: which office decides whether to depart from the default, whose privacy official approves, and how the component’s orders are reported to the department.
Without that settlement, two components could analyze the same question differently, or one could depart from the default without the department’s privacy official knowing. The memo’s approval line assumes a single privacy official per agency. Departments with layered privacy offices need to decide which one signs, in our reading.
Agencies whose populations are unusual
Some agencies serve people who may fit standard services poorly, in our view: children, people abroad, people without credit histories, or patients in federal health programs. An agency with such a population may need services the standard vehicle does not offer well.
The memo allowed that agency to make its case. Its analysis would highlight unique features or requirements. [1] The privacy official’s approval would confirm that the departure served the people affected.
The privacy office as a buyer
Across all of these agencies, the memo gave the privacy office a role in buying. The Senior Agency Official for Privacy approves departures from the default. [1] Later breach guidance made the same official responsible for choosing which services to provide. [2]
A privacy office that has never worked with acquisition may need help to play that role. Pairing it with a contracting officer who knows the vehicle, before a breach, is a practical step. The memo did not require such pairing. It made it useful. [1] [2]
Objections to this reading
Three objections deserve an answer, in order.
- The memo was only a procurement preference. In form, yes. It named a preferred source and set steps for using it. [1] Our argument is that the steps for leaving it, the written analysis, the privacy official’s approval and the price submissions, were the memo’s working parts. A preference with those steps attached shapes behavior more than a bare preference would.
- A shared vehicle limits competition. The memo described the BPAs as giving access to a pool of contractors, and GAO later reported three contractors on the agreement; the memo also allowed agencies to compete their own vehicles when justified. [1] [3] The memo also asked agencies to consider small business impact. [1] The concern is real, but the memo addressed it inside the analysis rather than ignoring it.
- The services may not be worth buying at all. This is the strongest objection, and GAO later raised it. [3] It goes to the memo’s scope, not its design. M-16-14 assumed a need and governed how to meet it. The question of when services help belonged in breach response policy, where OMB placed it in January 2017. [2]
Checks an agency leader can run now
These checks follow from the memo’s structure. They are good practice, not requirements stated in this form, and each agency should confirm its current obligations with its general counsel and acquisition office.
The default
- Confirm that the breach response plan names the vehicle the agency would use to buy identity protection services, and how to order from it.
- Confirm who in the agency holds the warrant and the knowledge to place that order quickly.
The exception file
- If the agency uses its own vehicle, find the most recent analysis comparing it with the GSA vehicle and the privacy official’s approval.
- Confirm that the next option decision has the comparison scheduled before the option deadline.
The price record
- Confirm which pricing model the agency would choose for a small and for a large breach, and why.
- Keep a record of prices paid and enrollment for past breaches, so the next decision can use them.
The carve-out
- Review breach terms in contracts with contractors that hold personal information, including who pays for services and to what standard.
- Decide in advance whether contractors under cost-reimbursement contracts should be authorized to use GSA sources after a breach.
With hindsight
OMB’s breach response guidance followed in January 2017. On January 3, 2017, OMB issued M-17-12, Preparing for and Responding to a Breach of Personally Identifiable Information. [2]
M-17-12 said that any countermeasures an agency required of a contractor should be consistent with M-16-14, which, except under limited circumstances, requires use of GSA’s IPS BPAs. [2] It said the BPAs’ requirements had been developed jointly with officials from OPM, the Department of Defense and other agencies. [2]
M-17-12 also answered the question M-16-14 had left open. It made the Senior Agency Official for Privacy responsible for identifying the services that best mitigate the specific risk of harm from a particular breach. [2] It said that if no available service mitigates a specific risk, the agency may choose not to provide services. [2]
GAO then examined the services themselves. In a March 2017 report, GAO-17-254, it found that identity theft services offer some benefits but have limitations. [3] It said credit monitoring helps detect new-account fraud but does not prevent it or address existing-account fraud, and that consumers could use a low-cost credit freeze instead. [3]
GAO reported that, in response to its 2015 breaches, OPM had awarded two contracts obligating about $240 million for identity theft services. [3] It found that OPM provided duplicative services for about 3.6 million people affected by both breaches. [3]
GAO recommended that Congress consider letting agencies set the coverage level for identity theft insurance they offer after breaches. [3] It recommended that OMB analyze the effectiveness of these services relative to alternatives and explore options to address duplication. [3]
Congress set terms for OPM’s case in law. Section 633 of the Consolidated Appropriations Act, 2017, approved May 5, 2017, required OPM to provide complimentary identity protection coverage to affected individuals for fiscal years 2016 through 2026. [4] The coverage had to be effective for not less than 10 years and include not less than $5,000,000 in identity theft insurance. [4]
GAO had reported that this level of insurance was likely unnecessary because claims paid rarely exceed a few thousand dollars. [3] It also reported that, as of February 2017, all three contractors on the IPS BPA had updated their offerings to include $5 million in coverage without raising prices. [3]
The vehicle itself changed form. GSA now offers these services through Special Item Number 541990IPS on its Multiple Award Schedule. [5] GSA’s page says that, in accordance with M-16-14 and like the former BPA, the SIN is the preferred source for data breach services, and that OMB has designated it Best-in-Class. [5] The page showed a last-updated date of August 20, 2026 when we checked it. [5]
GSA’s ordering guide, updated December 2025, still lists M-16-14 among its resources. [6] It sets a maximum order limitation of $1 million, the price at which an ordering agency must seek additional discounts. [6]
Consolidation went further in 2025. Executive Order 14240, signed March 20, 2025, directed agency heads to submit proposals for GSA to conduct their domestic procurement of common goods and services, where permitted by law. [7] It defined common goods and services by reference to categories set by the Category Management Leadership Council led by OMB. [7]
So what held up? The memo’s structure did. As checked on 2026-11-16, GSA still describes its identity protection vehicle as the preferred source under M-16-14, and its ordering guide still cites the memo. [5] [6] What moved was the question the memo did not ask: whether the services help. M-17-12 put that judgment on the privacy official, and GAO showed why it matters. [2] [3]
Spotted an error? Tell us and we will check it and correct the article where needed.