What Is the Federal Information Security Management Act (FISMA)?

The Federal Information Security Management Act (FISMA) was passed by the United States Congress in 2002. It dictates that federal agencies incorporate information security measures designed for the protection of sensitive data. The compliance standards are set by both the National Institute of Standards and Technology (NIST) and FISMA

The NIST is responsible for keeping the compliance documents up to date and ensuring they protect information adequately, include appropriate risk assessment measures, and set forth the security measures necessary to establish a minimum level of protection for sensitive data.

Why Was FISMA Created?

FISMA was created to make sure federal agencies design, document, and apply comprehensive security plans to safeguard and support the safe operation of each agency. In this way, FISMA is similar to the Gramm-Leach-Bliley Act (GLBA), the Health Insurance Portability and Accountability Act (HIPAA), the Federal Risk and Authorization Management Program (FedRAMP), and the Sarbanes-Oxley Act (SOX)—all of which protect the general public from information security dangers.

Who Needs To Follow FISMA Compliance?

FISMA, at first, was designed to only apply to federal agencies. As time went on, it changed and expanded, covering state agencies charged with the management of federal programs, such as Medicaid, Medicare, and unemployment insurance. FISMA also applies to private companies that have contracts with federal agencies. 

Requirements of FISMA Compliance

Information System Inventory

To remain in compliance, an agency has to keep an inventory of all its systems and how they tie in to the agency’s work.

Risk Categorization

The way in which an agency categorizes its security and risk requirements is documented in the Federal Information Processing Standards (FIPS) 199. Every agency has the responsibility of maintaining the highest level of security as outlined in this document.

System Security Plan

Each agency, to remain in compliance, must develop a security plan—and a process that ensures it is regularly updated.

Security Controls

There are 20 security controls outlined in NIST 800-53. Every agency must implement them to remain in compliance.

Risk Assessments

If an agency alters their systems., they have to re-assess their risk according to a three-tier system, as described in the NIST’s Risk Management Framework (RMF).

Certification and Accreditation

To remain in compliance with FISMA, every agency must conduct security reviews at least once a year. They then must show that they can put the measures in place, maintain them, and monitor the relevant systems.

Best Practices of FISMA Compliance

Classify Information as It Is Created

All information must be classified to help those in charge of its management assess which standards apply to it. In this way, they can decide how to make sure the organization remains in compliance.

Automatically Encrypt Sensitive Data

All sensitive data must be encrypted by default. This is so you can eliminate the potentially time-consuming step of retroactively securing FISMA-relevant data.

Maintain Written Evidence of FISMA Compliance

As with all compliance measures, it is important to both show and prove. Maintaining written evidence is useful in the event of a FISMA audit or investigation, as well as for training others regarding compliance standards.

Stay Current with Any Changes To the FISMA Standards

It is crucial to stay current with any adjustments or additions to FISMA standards, not only to remain in compliance but also for the security of your organization’s information systems. To accomplish this, it will be helpful to focus on:

  1. Making updates according to recent information from the NIST’s RMF
  2. Maintaining the privacy and protection of data
  3. Implementing security best practices

Penalties for FISMA Compliance Violations

One of the most impactful penalties for lack of FISMA compliance for a private company is losing federal funding. This can happen as soon as a FISMA-related breach has been identified and proven by an investigating authority. The penalties for government employees include losing employment and censure, which is a type of public condemnation.

Fortinet Compliance Solutions

FortiSIEM, the Fortinet security information and event management solution (SIEM), provides organizations with next-generation SIEM. FortiSIEM can keep you in compliance with FISMA regulations because it combines full visibility into your system and its connected components, automated responses, and remediation measures meant to identify and handle threats as they arise. 

With FortiSIEM, you can leverage the visibility it affords your IT team in identifying vulnerabilities caused by both humans and insufficient digital security—and then act accordingly. Further, FortiSIEM can respond automatically to threats that can result in your organization falling out of FISMA compliance.