Cross-sector · Economics & Procurement
Across sectors: economics and procurement
What to know now
Each number links to the point's source. Points checked unless the point shows another date.
- In its 2025 annual report, the FBI's Internet Crime Complaint Center says losses reported to it in 2025 passed $20 billion. Investment fraud was the largest part, followed by business email compromise and tech support scams.1
- Executive Order 14275 of April 15, 2025 directed that the Federal Acquisition Regulation be amended, within 180 days, so that it contains only provisions required by statute or otherwise necessary to support simplicity and usability, strengthen the efficacy of the procurement system, or protect economic or national security interests.2
- Executive Order 14402 of April 30, 2026 directs agencies to use fixed-price contracts to the maximum extent consistent with law. The contracting officer must justify any non-fixed-price contract in writing to the agency head, and the agency head must approve it in writing above set values, such as $10 million for agencies other than the Departments of War and Homeland Security and NASA.3
- The Defense Department's DFARS rule bringing Cybersecurity Maturity Model Certification requirements into contracts took effect November 10, 2025.4
- Executive Order 14412 of June 22, 2026 directs the FAR Council to publish, within 180 days, a proposed rule requiring covered contractors to comply by December 31, 2030 with NIST's FIPS, including all applicable FIPS incorporating post-quantum algorithms.5
- Under the Justice Department's data security rule, 28 CFR part 202, vendor, employment and investment agreements that are covered data transactions with a country of concern or covered person are restricted transactions. They are allowed only if the U.S. person meets the rule's security requirements.6
License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.
Sources
- Federal Bureau of Investigation, Internet Crime Complaint Center. 2025 IC3 Annual Report. Checked .
- Office of the Federal Register (Executive Office of the President). Executive Order 14275: Restoring Common Sense to Federal Procurement. Checked .
- Office of the Federal Register (Executive Office of the President). Executive Order 14402: Promoting Efficiency, Accountability, and Performance in Federal Contracting. Checked .
- U.S. Department of Defense. Defense Federal Acquisition Regulation Supplement: Assessing Contractor Implementation of Cybersecurity Requirements (DFARS Case 2019-D041), final rule. Checked .
- Office of the Federal Register (Executive Office of the President). Executive Order 14412: Securing the Nation Against Advanced Cryptographic Attacks. Checked .
- U.S. Department of Justice (eCFR). 28 CFR part 202: Access to U.S. Sensitive Personal Data and Government-Related Data by Countries of Concern or Covered Persons. Checked .
How we source and check every fact: Editorial standards · Corrections
Last reviewed .
Spotted an error? Tell us and we will check it and correct the page where needed.
Looking Back
Week of February 2, 2026
Vendors repriced in a day, contracts run for years: the buyer’s side of the software selloff
In February, investors dumped software stocks on fears that AI agents would upend the business. Buyers in banks, hospitals and agencies faced a slower-moving problem: contracts priced per human user, locked for years, closed to automation and hard to exit.
Week of November 25, 2024
Blue Yonder put process-running vendors at the top of the risk register
A ransomware attack on Blue Yonder disrupted customers that ran scheduling and warehouse work on its hosted service, and exposed a blind spot. We think most vendor checks ask who holds your data. The better question is whose failure would stop your work.
Week of December 25, 2023
Someone else’s lawsuit, your contracts: how the Times case reached regulated AI buyers
Banks, health systems and agencies were not parties to The New York Times’s December 2023 lawsuit against OpenAI and Microsoft. It still reached them in three ways: through the vendor promises they relied on, the content they published and the prompts their vendors kept.
Week of November 20, 2023
Why the useful response to OpenAI’s board crisis was a days-to-switch number
No vendor questionnaire could have predicted OpenAI’s November 2023 boardroom upheaval. What regulated buyers could control was how costly it would be to move away from any one AI provider, and that came down to contracts, architecture and fallbacks.
Week of July 25, 2022
Chip policy ran on a decade’s clock; IT backlogs ran on a quarter’s
The CHIPS and Science Act passed while network switches and servers sat on back order. It was about where chips would be made in the 2030s. IT leaders needed separate answers, on separate timescales, for the backlog, the refresh plan and provenance.
Week of May 23, 2022
An acquisition announcement is a free option on your exit plan
Broadcom’s deal to buy VMware gave customers eighteen months before anything changed. The organizations that fared best treated that time as a cheap option: they priced a way out, kept it alive with small investments, and used it, on evidence, at renewal.
Week of October 19, 2020
Antitrust moves in years; vendor dependency is set at signing
The Justice Department’s case against Google opened a long fight over platform power. It offered regulated buyers no relief on their own dependence on vendors, which is settled in contracts, system design and tested exit plans, far faster than any court moves.
Week of November 25, 2019
Commerce’s proposed supply chain rule reached into old contracts
Commerce’s November 2019 proposal would let it block or unwind technology deals case by case, including updates and managed services under contracts signed years earlier. For regulated buyers, the exposure lived in the installed estate and existing contracts, so four preparations could not wait.
Week of April 30, 2018
BLU’s 2018 FTC order treated a phone’s update software as a supplier someone had to oversee
The FTC’s April 2018 complaint against phone seller BLU listed four failures in overseeing the company that pushed its firmware updates. Read as a procurement checklist, the four steps fit any bank, health system or agency that buys devices.
Explainers, checklists and data
Explainer · November 14, 2026
OMB M-26-05 and the end of the federal secure software attestation requirement, explained
OMB Memorandum M-26-05 rescinded M-22-18 and M-23-16 in January 2026, so a single government-wide attestation no longer applies; each agency now sets software and hardware assurance terms from its own risk determinations, with the attestation form and SBOM terms as options.
Explainer · November 14, 2026
Section 889 in federal contracts: the covered telecommunications and video surveillance prohibition (FAR 52.204-24, 52.204-25 and 52.204-26), explained
Section 889 bars agencies from buying covered Chinese telecommunications and video surveillance equipment and from contracting with companies that use it anywhere. The FAR carries it into every solicitation through two representations and a reporting clause.
Checklist · November 14, 2026
Checklist: buying AI under OMB M-25-22, from scoping the purchase to contract closeout
Fourteen steps that follow OMB Memorandum M-25-22 through the acquisition lifecycle, each labeled as a requirement, a memo recommendation or our suggestion: scope, high-impact determination, solicitation terms on data and lock-in, pre-award testing, monitoring and closeout.
Checklist · November 14, 2026
Checklist: FAR section 889 representations, reasonable inquiry and one-business-day reports
Twelve steps for any company that sells to federal agencies, from SAM representations and a company-wide reasonable inquiry to the one-business-day report and flowdown in FAR 52.204-25, with the status of the FAR Council’s June 2026 proposal.
Checklist · November 14, 2026
Checklist: counterparty due diligence for vendors and data brokerage under the DOJ Data Security Program
Ten steps under 28 CFR part 202 for checking who is on the other side of a data deal: the knowingly standard, covered-person screening, looking through vendors to their staff, refusing and reporting prohibited brokerage, the onward-transfer clause, CISA’s vendor-agreement requirement, and the diligence records the rule requires.