Cybernion
← Insights

United States

What Is FISMA? US Federal Information Security Law

30 Aug 2026 · Updated 30 Aug 2026

FISMA, the Federal Information Security Modernization Act, is the US law requiring federal agencies, and the contractors that run systems or hold data for them, to secure government information systems using the NIST Risk Management Framework. Agencies categorise each system by impact, apply the NIST SP 800-53 controls, obtain an Authority to Operate and monitor continuously. FedRAMP is FISMA applied to cloud services, and an Australian company serving a US federal agency typically meets FISMA through FedRAMP.

FISMA is the legal backbone of United States federal cyber security. Most of the well-known US government security machinery, NIST SP 800-53, the Risk Management Framework, FedRAMP, exists to satisfy it.

What is FISMA?

FISMA is the Federal Information Security Modernization Act, the United States law that makes securing government information a legal responsibility across the federal government. It was originally enacted as the Federal Information Security Management Act in 2002 and updated by the Federal Information Security Modernization Act in 2014, which kept the acronym but modernised the emphasis toward continuous monitoring and ongoing risk management rather than point-in-time paperwork.

FISMA requires each federal agency to develop, document and implement an agency-wide program to provide information security for the information and information systems that support its operations, including those operated by another agency, a contractor or another source on its behalf. Importantly, it directs the National Institute of Standards and Technology, NIST, to develop the standards and guidelines that agencies must use, which is why the NIST catalogue is at the centre of US federal security. FISMA also assigns oversight roles, with the Office of Management and Budget overseeing agency compliance and agencies reporting on their security posture, including through annual independent evaluations. In short, FISMA is the law that turns federal information security from good practice into a statutory obligation and points every agency at a common, NIST-defined way of meeting it.

What does FISMA require in practice?

FISMA requires a risk-based information security program built on the NIST Risk Management Framework, or RMF, and in practice this follows a defined lifecycle for each system. First the agency categorises the system by impact level, low, moderate or high, based on the potential harm to confidentiality, integrity and availability if it were compromised, using the FIPS 199 standard. Then it selects and implements the appropriate baseline of controls from NIST SP 800-53, the full catalogue of security and privacy controls, scaled to that impact level. The controls are then assessed to confirm they are in place and working.

On the strength of that assessment, an authorising official makes a risk-based decision to grant an Authority to Operate, or ATO, which is the formal acceptance of the system’s residual risk and permission to run it. After authorisation, the system is not left alone: FISMA’s 2014 update emphasises continuous monitoring, so the agency keeps watching the controls, tracking new weaknesses in a Plan of Action and Milestones, and maintaining the authorisation over time. This categorise, select, implement, assess, authorise and monitor cycle is the RMF, and it is how FISMA is actually met day to day. The result is that a US federal system carries a documented, assessed and monitored security posture with an accountable official standing behind it.

How does FISMA relate to FedRAMP, and does it reach Australian companies?

FedRAMP is best understood as FISMA applied to cloud services. FISMA sets the overarching legal requirement and points to the NIST controls; FedRAMP provides a standardised, government-wide program to assess and authorise cloud products against those same NIST SP 800-53 controls, so that one rigorous authorisation can be reused across many agencies instead of each agency assessing the same cloud service from scratch. A cloud provider selling to the US government therefore meets its FISMA obligations through the FedRAMP process. For traditional, non-cloud federal systems, agencies apply the RMF directly under FISMA without FedRAMP.

FISMA reaches beyond agencies themselves. Because an agency must ensure that systems operated on its behalf meet the same requirements, contractors and service providers that run federal systems or hold federal data are effectively bound by FISMA-derived requirements through their contracts. This includes non-US companies: an Australian business providing a system or service to a US federal agency will typically have to meet FISMA’s requirements, most often through FedRAMP if it is a cloud service, as a condition of winning and keeping the work. For Australian companies, the practical parallel is that FISMA and the RMF play a role in the US similar to the role the ISM and IRAP play here, a government control set applied through a formal authorisation, and the IRAP versus FedRAMP comparison is the useful bridge for anyone who knows the Australian regime and is approaching the US one. Where a company is navigating US federal security requirements alongside its Australian obligations, we can help make sense of how they map through advisory.

Frequently asked questions

What is FISMA?

FISMA is the Federal Information Security Modernization Act, the United States law that requires federal agencies to develop, document and implement programs to secure their information and information systems. Originally enacted in 2002 and updated in 2014, it makes information security a legal responsibility across the federal government and directs NIST to develop the standards agencies must follow. It also extends in practice to contractors and service providers that operate systems or hold data on behalf of federal agencies.

What does FISMA require?

FISMA requires federal agencies to run a risk-based information security program built on the NIST Risk Management Framework. In practice that means categorising each system by impact level, selecting and implementing the NIST SP 800-53 controls appropriate to that level, assessing them, obtaining an Authority to Operate from an authorising official, and then continuously monitoring the system. Agencies also report on their security posture, and their compliance is overseen by the Office of Management and Budget and inspected annually.

How does FISMA relate to FedRAMP?

FedRAMP is essentially FISMA applied to cloud services. FISMA sets the overarching legal requirement for federal information security based on the NIST framework, and FedRAMP provides a standardised, government-wide way to assess and authorise cloud products against those same NIST SP 800-53 controls so that an authorisation can be reused across agencies. A cloud provider selling to the US government meets FISMA’s requirements through the FedRAMP process rather than a separate FISMA scheme.

Does FISMA apply to contractors and non-US companies?

FISMA applies directly to federal agencies, but it reaches contractors and service providers, including non-US companies, that operate information systems or handle federal data on an agency’s behalf, because the agency must ensure those systems meet the same requirements. An Australian company providing a system or service to a US federal agency will therefore typically have to meet FISMA-derived requirements, usually through FedRAMP for cloud services, as a condition of the contract.

What is the difference between FISMA and NIST SP 800-53?

FISMA is the law that requires federal information security; NIST SP 800-53 is the catalogue of security and privacy controls that agencies use to meet it. FISMA directs NIST to produce the standards, and SP 800-53, along with the FIPS 199 impact categorisation and the Risk Management Framework, is how agencies actually implement FISMA. So FISMA is the obligation and SP 800-53 is the control set that satisfies it.


Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.

Talk to us.

Sources:

  1. Federal Information Security Modernization Act, Cybersecurity and Infrastructure Security Agency, 2026
  2. Risk Management Framework, NIST Computer Security Resource Center, 2026
  3. NIST SP 800-53, NIST Computer Security Resource Center, 2026

Last updated: 30 August, 2026

Talk to us about your engagement

A scoped proposal within one business day.