Cross-sector · Operations & Workforce
Across sectors: operations and workforce
What to know now
Each number links to the point's source. Points checked unless the point shows another date.
- NIST finalized SP 800-61 Revision 3 on April 3, 2025. It treats incident response as part of cybersecurity risk management under CSF 2.0 and supersedes Revision 2 of 2012.1
- CISA's CPG 2.0 Report carries a revision date of December 11, 2025. It provides a select list of attestable goals to reduce cyber threats.2
- CISA says the Cross-Sector Performance Goals 2.0 add a GOVERN function, mirroring CSF 2.0, that regroups existing goals and creates new ones covering leadership accountability, oversight and risk management. Version 2.0 removes three duplicative goals, and the CPG 2.0 Report includes improved cost, impact and ease-of-implementation ratings for each goal.3
- The current NICE Framework components (work role categories, work roles, competency areas, and task, knowledge and skill statements) are version 2.2.0, dated April 28, 2025. NIST also publishes a mapping of NICE Framework components v2.0.0 to CSF 2.0.4
- Executive Order 14431 of September 18, 2026 directs the Secretaries of State, Labor and Homeland Security to coordinate with Commerce, Education and the Small Business Administration on H-1B labor condition applications, petitions and visas, and to take into account whether the sponsoring employer had layoffs within the previous year, or plans layoffs, that negatively affect similarly situated U.S. workers. It directed the Labor Department to begin, within 30 days, reviewing previously submitted labor condition applications for possible action against sponsoring employers.5
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
- National Institute of Standards and Technology. SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile. Checked .
- Cybersecurity and Infrastructure Security Agency. CPG 2.0 Report. Checked .
- Cybersecurity and Infrastructure Security Agency. Cross-Sector Cybersecurity Performance Goals. Checked .
- National Institute of Standards and Technology. NICE Framework: Current Versions. Checked .
- Office of the Federal Register (Executive Office of the President). Executive Order 14431: Enhancing Program Integrity and Interagency Coordination in the Administration of the H-1B Nonimmigrant Visa Program. 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 September 29, 2025
How the lapse of a 2015 law put counsel in the threat-sharing loop
The 2015 law protecting cyber threat sharing expired as the October 2025 shutdown began, and sharing did not stop. But every warning sent outside the building picked up a legal question, and teams without written rules found analysts waiting on lawyers.
Week of July 15, 2024
Channel File 291 measured every recovery plan in hands per device
One faulty CrowdStrike update turned millions of remotely managed Windows computers into a hands-on repair job. How fast each organization recovered came down to three things few plans covered: access to recovery keys, people at keyboards, and the order of repair.
Week of February 26, 2024
CSF 2.0’s biggest addition was the one a security team could not deliver
NIST’s refreshed cybersecurity framework added a new function called Govern. It looked like a technical update. In fact it hands work to executives, HR, procurement and the board, and organizations that left it to the security chief missed what had changed.
Week of February 21, 2022
Shields Up had no end date, so vigilance needed a staffing plan
Russia’s invasion of Ukraine brought a request from CISA for every US organization to raise its guard, with no date to lower it. Staying alert for months turned out to be a management problem: who watches, who decides, and what work stops.
Week of September 6, 2021
Vaccination status was the easy record; exemptions were the hard one
President Biden’s September 2021 vaccination plan sent employers scrambling to collect proof. It demanded three things: status records, weekly testing and exemption decisions. The third carried the lasting legal risk, and it was the easiest to leave until last.
Week of February 15, 2021
Why working from home failed when Texas froze
A year into the pandemic, many continuity plans answered every site outage with “work from home.” Winter Storm Uri took out power, water, roads and home internet together, showing that one fallback fails when people, sites, networks and suppliers all fail at once.
Week of October 12, 2020
Why one phone call beat Twitter’s login controls
No clever code, no exotic exploit. New York’s report on the Twitter hack traced it to a phone call and a fake login page. The people who verify callers and reset logins turned out to be a security control few had designed or measured.
Week of February 24, 2020
Buildings intact, workforce gone: the scenario continuity plans skipped
As the Fed flagged economic risks and health officials warned of community spread, plans written for losing a building faced a different emergency. A pandemic takes away people, suppliers and tools at once, and plans had to be rebuilt and tested around those three losses.
Week of November 19, 2018
Commerce’s 2018 AI list made export control a staffing question
In November 2018, Commerce asked which emerging technologies, from neural networks to speech recognition, needed export controls. For banks, hospitals and agencies, exposure ran through people and access: who builds, where work happens, what gets published and what suppliers pass on.
Week of October 15, 2018
Spoofed emails, real wires: the SEC put business email fraud inside payment controls
The SEC’s October 2018 report on nine companies that wired nearly $100 million to impostors placed the fraud in internal accounting controls. Its lasting value was the line it kept: controls over moving cash, not cybersecurity at large.
Explainers, checklists and data
Explainer · November 14, 2026
OFAC reports and records: blocked property, rejected transactions and the 10-year recordkeeping rule (31 CFR part 501, subpart C), explained
OFAC’s reporting rules apply to every U.S. person that blocks property or rejects a prohibited transaction, whether or not it is a bank. Reports are due within 10 business days, and transaction records must be kept for at least 10 years.
Explainer · November 14, 2026
CISA’s Known Exploited Vulnerabilities catalog: how entries are added, how BOD 26-04 uses it, and the feed, explained
CISA’s KEV catalog lists vulnerabilities with a CVE ID, reliable evidence of exploitation and a clear remediation. Federal civilian agencies must act on it under BOD 26-04; everyone else can use the public JSON and CSV feeds as a prioritization input.
Checklist · November 14, 2026
Checklist: building and using a NIST CSF 2.0 Organizational Profile, with the Govern Function and Tiers
Twelve steps for putting the voluntary NIST Cybersecurity Framework 2.0 to work: scoping a profile, recording current and target outcomes, starting with Govern, choosing Tiers, and turning the gaps into an action plan the executive team owns.
Checklist · November 14, 2026
Checklist: mapping cybersecurity jobs, skills and training to the NICE Framework
Twelve steps for putting NIST’s voluntary Workforce Framework for Cybersecurity (SP 800-181 Rev. 1) to work: pinning the component version, mapping jobs to Work Roles, checking the 2025 and 2026 changes, assessing competencies and tying it all to CSF 2.0.