In 1998, the National Security Agency (NSA) Information Assurance Methodology (IAM) was developed to meet the demand for information security (INFOSEC) assessments-a demand that was increasing due to Presidential Decision Directive 63 (PDD-63) while at the same time NSA was downsizing. NSA sought a way to maximize its resources to assist as many customers as possible and so they created a list of organizations that could perform the same service as the NSA. NSA quickly realized that this system would not only provide valuable information to consumers-it would also provide a vehicle for standardization of INFOSEC assessments.
Define What Composes an Assessment
Learn about the NSA’s three-phases: Assessment, Evaluation, and Red teaming
Understand Industry Concerns for the Assessment Site
Review the items that affect your client: Health Insurance Portability and Accounting Act of 1996 (HIPAA), Sarbanes-Oxley, Financial Management and Accountability (FMA) Act, Family Education Rights and Privacy Act (FERPA), and others.
Create the Organizational Information Criticality Matrix (OICM)
Create the OICM, which provides a basis for everything else in the methodology and clarifies the intentions and goals of the assessment process for the customer.
Handle Documentation Identification and Collection
Work with the client to gather and define documents such as policy, guidelines, plans, SOPs, user documentation and see what happens when no documentation exists.
Understand the Technical Assessment Plan (TAP)
Use the TAP to define all dates and scheduling, personnel involvement, understood boundaries, deliverables, priority concerns, and priority constraints.
Review the 18 NSA INFOSEC Baseline Classes and Categories
Use these 18 categories to address the customer’s security posture and determine what questions shou