Skip to main content
v2026.11,986 entries · CC-BY 4.0

NIST SP 800-115: Security Testing and Assessment

Technical guide to NIST SP 800-115: security assessment phases, penetration testing methodologies, rules of engagement, and federal compliance workflows.

Written and maintained by CASRAI Editorial Board

Published · Last updated

On this page

NIST Special Publication 800-115 (SP 800-115), titled Technical Guide to Information Security Testing and Assessment, provides the foundational methodology for technical security evaluations across federal and commercial information systems. Issued by the National Institute of Standards and Technology (NIST), the guide defines repeatable procedures to uncover vulnerabilities, verify security configuration efficacy, and validate operational controls through hands-on testing. As described on the official page on 2026-11-10, SP 800-115 serves as the operational execution baseline for federal civilian agencies, cloud service providers, and research facilities.

Ask CASRAI · free to tryQuestion about this guide? Ask CASRAI answers with linked sources. 2 free questions a day, no account.

Ask your first question freeSubscribe

What it is and who runs it

NIST SP 800-115 is published and maintained by the Computer Security Division within NIST’s Information Technology Laboratory (ITL), a non-regulatory agency of the U.S. Department of Commerce in Gaithersburg, Maryland. Released in September 2008 by authors Karen Scarfone, Murugiah Souppaya, Amanda Cody, and Angela Orebaugh, the publication formally superseded NIST SP 800-42 (Guideline on Network Security Testing).

Under statutory authority derived from FISMA, SP 800-115 organizes technical security assessment activities into three primary categories:

  • Review Techniques: Passive assessment methods including documentation reviews, log audits, firewall and router ruleset checks, system configuration audits, network sniffing, and file integrity monitoring.
  • Target Identification and Analysis Techniques: Active reconnaissance to discover live devices, identify open ports and services, execute vulnerability scans, and map wireless networks.
  • Target Vulnerability Validation Techniques: Controlled exploitation procedures that confirm whether identified weaknesses can be exploited, covering password cracking, penetration testing, and social engineering.

Eligibility (summary, with the official source)

As described on the official page on 2026-11-10, NIST SP 800-115 is a technical guidance standard rather than a financial grant. Its testing methodologies apply across several sectors:

  • Federal Civilian Agencies: Mandated under FISMA to perform regular security control assessments and continuous technical monitoring on all federal systems.
  • Cloud Service Providers (CSPs): Required under FedRAMP to execute annual penetration testing via an accredited Third-Party Assessment Organization (3PAO) using SP 800-115 procedures.
  • Academic Research Institutions: Universities handling sensitive federal research data or defense awards must conduct technical assessments to validate NIST SP 800-171 controls and support broader research security posture.
  • Defense Contractors: Organizations seeking CMMC compliance for research institutions adopt SP 800-115 testing methodologies to verify perimeter defenses and enclave security.
  • Commercial Enterprises: Private firms apply the framework to satisfy technical testing requirements under ISO 27001 security standards, HIPAA, and PCI-DSS.

What it funds or requires

NIST SP 800-115 does not disburse grant funding; instead, it establishes procedural standards for executing security tests safely and effectively:

  • Formal Rules of Engagement (ROE): Appendix B requires a signed ROE agreement prior to testing, specifying authorized IP targets, excluded subnets, operational testing hours, emergency abort contacts, and allowed exploit methods.
  • Designated Testing Viewpoints: Assessments must specify internal versus external perspectives (behind firewalls versus public internet vectors) and overt versus covert postures (collaborative white-box testing versus unannounced adversary simulations).
  • Strict Data Handling Protocols: Section 7.4 governs assessor handling of discovered evidence, requiring encrypted local storage, secure transmission channels, and certified sanitization or data destruction upon project completion.
  • System Protection and Non-Disruption: Testers must avoid causing denial-of-service conditions or data corruption on production environments, substituting non-destructive proof-of-concept verification for destructive payloads.
  • Emergency Incident Escalation: Assessors must immediately notify system owners and the Chief Information Security Officer (CISO) if a critical zero-day vulnerability or signs of an active hostile compromise are discovered during testing.

Application or compliance steps

Executing an assessment aligned with NIST SP 800-115 involves six sequential steps:

  1. Define Objectives and Scope: Establish authorization boundaries, identify target systems, and align testing scopes with FISMA compliance mandates and system owner priorities.
  2. Finalize the Rules of Engagement: Draft and sign the assessment plan and Appendix B ROE, establishing test schedules, tester source IP addresses, emergency communication channels, and prohibited techniques.
  3. Prepare Assessment Logistics: Set up secure assessor workstations, isolated test appliances, and encrypted storage media, ensuring all vulnerability signature databases and tools are current.
  4. Conduct Reviews and Target Identification: Audit configuration baselines, inspect firewall rulesets, and perform network discovery and port scans to catalog active network services and vulnerabilities.
  5. Execute Target Vulnerability Validation: Perform controlled vulnerability exploitation, password cracking, or penetration testing to validate exploitability without disrupting ongoing operations.
  6. Analyze Findings and Issue Remediation Plans: Filter false positives, determine vulnerability root causes, formulate risk ratings, and draft the final assessment report. Findings feed directly into institutional system security plan requirements and Plans of Action and Milestones (POA&M).

Typical timeline phases (no calendar dates as facts)

A NIST SP 800-115 technical assessment moves through four structured phases governed by operational milestones rather than calendar dates:

  • Phase 1: Planning and Logistics: Defining technical boundaries, selecting assessment tools and methodologies, choosing assessors, and securing Authorizing Official approval on the ROE.
  • Phase 2: Active Execution: Conducting passive reviews, network discovery, vulnerability scanning, and controlled validation attacks, with daily briefings to monitor system stability.
  • Phase 3: Analysis and Evaluation: Analyzing test logs, removing false positives, assessing mission impact, and identifying root causes across infrastructure and governance.
  • Phase 4: Post-Testing and Remediation: Delivering executive and technical reports, briefing system owners, drafting remediation roadmaps, and executing post-test data sanitization.

Common mistakes

Common missteps during SP 800-115 technical assessments include:

  • Conflating Scanning with Penetration Testing: Treating automated vulnerability scanner outputs as completed penetration tests without manual validation to confirm exploitability.
  • Operating Under Ambiguous Scope: Testing systems without a signed ROE clearly defining boundary limits, risking outages on production or shared cloud environments.
  • Inadequate Evidence Protection: Leaving captured credentials or configuration dumps unencrypted on assessor laptops in violation of Section 7.4 standards.
  • Bypassing Passive Reviews: Focusing solely on external attacks while skipping configuration audits, firewall ruleset evaluations, and log reviews.
  • Omitting Post-Test Cleanup: Neglecting to remove temporary assessor accounts, test binaries, or altered configurations deployed during validation.
  • Failing to Address Root Causes: Delivering raw vulnerability lists rather than categorizing findings into systemic remediation priorities such as patch cadence or configuration drift.

NIST SP 800-115 operates alongside several federal cybersecurity frameworks as described on the official page on 2026-11-10:

Framework / Standard Issuing Body Core Focus Operational Interconnection
NIST SP 800-53 Rev. 5 NIST ITL Federal security and privacy controls catalog. Mandates control requirements (CA-2 and CA-8), while SP 800-115 provides the tactical testing methods.
FedRAMP Penetration Test Guidance GSA Annual cloud authorization assessment standard. Directly adopts SP 800-115 Appendix B ROE requirements for mandatory 3PAO cloud penetration testing.
NIST SP 800-53A Rev. 5 NIST ITL Assessing security controls in federal systems. Emphasizes administrative examination and interviews, complementing SP 800-115’s technical testing focus.
NIST SP 800-30 Rev. 1 NIST ITL Cybersecurity risk assessment guidance. Provides the overarching risk estimation model using vulnerability findings identified via SP 800-115.
NIST SP 800-171 Rev. 2/3 NIST ITL Controlled Unclassified Information (CUI) protection. Defines contractor security requirements verified through periodic SP 800-115 technical assessments.

FAQ

What is the difference between vulnerability scanning and penetration testing in SP 800-115?

Vulnerability scanning relies on automated tools to identify potential weaknesses, outdated software, and misconfigurations across networked devices without executing exploits. Penetration testing is a hands-on, targeted process where assessors actively validate vulnerabilities through controlled exploitation to determine the extent of unauthorized access, privilege escalation, and lateral movement an adversary could achieve.

How does NIST SP 800-115 define the phases of penetration testing?

Section 5.2.1 defines three core penetration testing phases: Discovery (information gathering, port scanning, and vulnerability identification), Attack (gaining access, escalating privileges, system browsing, and installing additional tools), and Reporting (documenting attack paths, impact analysis, and remediation recommendations).

What must be included in a NIST SP 800-115 Rules of Engagement (ROE)?

According to Appendix B, an ROE must detail target IP address ranges, excluded systems, designated technical contacts, emergency abort protocols, authorized testing timeframes, permitted attack techniques, and specific procedures for protecting and destroying discovered sensitive data.

What is the difference between overt and covert security testing?

Overt testing (white-box testing) is conducted with the advance knowledge of internal IT and security operations personnel, prioritizing comprehensive technical coverage. Covert testing (adversary simulation or black-box testing) is conducted without notifying internal defensive staff to evaluate the organization’s real-time detection, alerting, and incident response capabilities.

Does NIST SP 800-115 allow social engineering testing?

Yes. Section 5.3 recognizes social engineering as a target vulnerability validation technique. Permitted exercises include email phishing simulations, telephone pretexts, and physical site access attempts, provided that strict ethical parameters, management approval, and employee protections are established in the ROE.

What does NIST SP 800-115 require regarding post-assessment data destruction?

Section 7.4.4 mandates that once the security assessment report is accepted by the authorizing official, all sensitive data, captured credentials, and evidentiary files stored on assessor workstations and storage devices must be securely erased or destroyed in accordance with NIST SP 800-88 sanitization standards.

Sources

Follow CASRAI

Research-administration guidance, standards updates and independent tool reviews.

Ask CASRAI · free to try

Ask about NIST SP 800-115: Security Testing and Assessment

2 free questions a day, no account.

An AI assistant for research: funder rules, compliance, methods and publishing. It links the sources behind its answers and labels answers that come from a web search.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays open to read, with no account and no card.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →