Security engineer working through evidence in a data center

SAMPLENIST 800-53 assessment sample report

NIST 800-53 assessment sample report

Every deliverable of a real NIST SP 800-53 assessment, built for a fictional company, page by page.

25+ yearsIT and cybersecurity leadership
CISO, CISSPC|CISO certified assessor
Southern CaliforniaOn-site from Irvine
NationwideRemote assessments

Our deliverables

Five deliverables from one NIST 800-53 assessment

This is what a NIST 800-53 assessment from OC Security Audit produces. The sample was built for a fictional organization that runs a case-management platform for state and county agencies on Microsoft Azure, categorized FIPS 199 Moderate. This NIST 800-53 sample report lets you step through every key page below; open any page full size and zoom in to read it.

Sample report. Fabrikam Civic Systems is a fictional organization. Every name, account, address and figure in these pages is invented for illustration and does not describe any real customer.

51.3implementation score out of 100
35controls in 9 families
28findings, 3 of them Critical
17business risks with owners
31actions in a 180-day plan
01

PDF and Word · 9 pages

Executive Security Report

The decision document for leadership. It gives the overall implementation score and rating, the business risks that matter most, how an attacker could chain the weaknesses, posture by control family, what already works, the ten priority actions and the decisions only leadership can make. It is written in plain language for people who will not read the technical detail.

Who uses it

Owners, executives and the board; also what you share with a government customer that asks for a summary.

What is included

  • Executive summary and implementation score
  • Top business risks with scores
  • Attack chain built from real findings
  • Posture by control family
  • What is working well
  • Ten priority recommendations
  • 180-day roadmap at a glance
  • Decisions requested from leadership
  • Scope, method and limits

Sample · Fabrikam Civic Systems (fictional)

1 / 8

Executive Security Report: Cover page (fictional company, illustrative data)
Page 1 of 8Cover pageThe report is written for the leadership of Fabrikam Civic Systems, a fictional provider of a case-management platform for state and county agencies.
Executive Security Report: Executive summary and score (fictional company, illustrative data)
Page 2 of 8Executive summary and score35 controls in nine families give an implementation score of 51.3 out of 100 (Needs improvement): 7 implemented, 22 partial and 6 not implemented, with 28 findings in 17 business risks.
Executive Security Report: Top business risks and attack chain (fictional company, illustrative data)
Page 3 of 8Top business risks and attack chainThe three Critical risks, administrator takeover, ransomware through known vulnerabilities and backups that can be deleted with production, and how an attacker could chain the weaknesses.
Executive Security Report: Security posture by control family (fictional company, illustrative data)
Page 4 of 8Security posture by control familyAn implementation score for each of the nine families against a target of 85, with a plain-language assessment of each.
Executive Security Report: What is working well (fictional company, illustrative data)
Page 5 of 8What is working wellControls that already hold up, such as account lockout, server-side access enforcement in the platform, protected cryptographic keys and laptop patching.
Executive Security Report: Ten priority recommendations (fictional company, illustrative data)
Page 6 of 8Ten priority recommendationsThe ten actions that remove most Critical and High exposure, each with its risks and timeframe, followed by the 180-day roadmap.
Executive Security Report: Decisions requested from leadership (fictional company, illustrative data)
Page 7 of 8Decisions requested from leadershipSeven decisions only leadership can make, from approving the first 30 days of work to after-hours alert monitoring and backup separation.
Executive Security Report: Scope and approach (fictional company, illustrative data)
Page 8 of 8Scope and approachFramework, environment, method and scoring, the families recommended for a second phase and the limits of the assessment.

Click the page in the centre to open it full size, then zoom in to read every line.

02

PDF and Word · 36 pages

Technical Security Report

The working document for IT, security and engineering. After the scope, result definitions and environment overview, it summarizes the results, shows the evidence behind the key observations and gives one finding card per control gap: what we observed, the business impact, the recommendation, how to validate the fix, framework mappings, owner and target date.

Who uses it

IT director, security lead, engineers and the people who will close each finding.

What is included

  • Scope, method and result definitions
  • Environment overview
  • Results by severity and family
  • Key observations with evidence tables
  • One finding card per control gap
  • Validation steps for every fix
  • Owner, window and target date
  • Controls meeting the benchmark
  • NIST CSF 2.0, ISO 27001 and SOC 2 mapping

Sample · Fabrikam Civic Systems (fictional)

1 / 15

Technical Security Report: Cover page (fictional company, illustrative data)
Page 1 of 15Cover pageThe detailed report for the people who will fix the findings, with the same fictional organization and report date.
Technical Security Report: Contents (fictional company, illustrative data)
Page 2 of 15ContentsSeven sections, from the introduction and environment overview to one finding card per gap and the framework appendix.
Technical Security Report: Introduction and scope (fictional company, illustrative data)
Page 3 of 15Introduction and scopePurpose, the 35 controls in nine families, the system and supporting environment, and how each result is defined.
Technical Security Report: Environment overview (fictional company, illustrative data)
Page 4 of 15Environment overviewThe size of the environment in scope: 286 identities, 254 laptops, 42 servers, 471 discovered assets and 18 critical suppliers.
Technical Security Report: Control results and findings by severity (fictional company, illustrative data)
Page 5 of 15Control results and findings by severity7 controls implemented, 22 partial and 6 not implemented, and 28 findings: 3 Critical, 15 High, 8 Medium and 2 Low.
Technical Security Report: Findings by family and scores (fictional company, illustrative data)
Page 6 of 15Findings by family and scoresFindings stacked by severity for each family, the implementation score per family and the start of the findings index.
Technical Security Report: Identity and privileged access (fictional company, illustrative data)
Page 7 of 15Identity and privileged accessMFA registered for 260 of 286 identities and the 11 Global Administrators, three of them without MFA.
Technical Security Report: Oldest vulnerabilities and server baselines (fictional company, illustrative data)
Page 8 of 15Oldest vulnerabilities and server baselinesThe 15 oldest critical and high vulnerabilities, up to 214 days open, and each server's alignment with the CIS Benchmark sample.
Technical Security Report: Server weaknesses, backup and suppliers (fictional company, illustrative data)
Page 9 of 15Server weaknesses, backup and suppliersServers with unsupported systems or SMBv1, recovery objectives and restore tests for the 7 critical systems, and supplier assessment status.
Technical Security Report: Finding card: Least Privilege (AC-6) (fictional company, illustrative data)
Page 10 of 15Finding card: Least Privilege (AC-6)A Critical finding: 11 permanent Global Administrators, with business impact, recommendation, validation, framework mapping and owner.
Technical Security Report: Finding card: MFA (IA-2) (fictional company, illustrative data)
Page 11 of 15Finding card: MFA (IA-2)MFA missing for 26 identities and legacy authentication still allowed, with the fix and how to verify it.
Technical Security Report: Finding cards: backup and contingency plan (fictional company, illustrative data)
Page 12 of 15Finding cards: backup and contingency planBackups that production administrators could delete (CP-9) and a contingency plan written before the move to Azure (CP-2).
Technical Security Report: Finding card: vulnerability scanning (RA-5) (fictional company, illustrative data)
Page 13 of 15Finding card: vulnerability scanning (RA-5)47 critical and high vulnerabilities open more than 30 days, and an internet-facing web application that is not scanned.
Technical Security Report: Controls meeting the benchmark (fictional company, illustrative data)
Page 14 of 15Controls meeting the benchmarkThe 7 controls assessed as implemented, with the evidence behind each.
Technical Security Report: Framework reference (fictional company, illustrative data)
Page 15 of 15Framework referenceEvery finding mapped to NIST CSF 2.0, ISO/IEC 27001:2022 and the SOC 2 Trust Services Criteria.

Click the page in the centre to open it full size, then zoom in to read every line.

03

PDF and Word · 17 pages, landscape

Risk Register

The register that turns 28 findings into 17 business risks. Each risk is scored for likelihood and impact, rated, given an owner, a treatment and a target date, and shown on heat maps today and after the roadmap. A traceability table proves every finding is covered by at least one risk.

Who uses it

Leadership and risk owners for decisions; customers who ask how you manage risk; your plan of action and milestones.

What is included

  • Scoring method and rating bands
  • Risk profile and counts
  • Heat maps today and after remediation
  • Summary table with owners and dates
  • A detail card for every risk
  • Treatment and target after treatment
  • Finding-to-risk traceability

Sample · Fabrikam Civic Systems (fictional)

1 / 7

Risk Register: Cover page (fictional company, illustrative data)
Page 1 of 7Cover pageA landscape register built for review meetings, with the same sample notice on the cover.
Risk Register: Risk scoring method (fictional company, illustrative data)
Page 2 of 7Risk scoring methodLikelihood and impact definitions from 1 to 5 and the four rating bands, each with its expected response.
Risk Register: Risk profile and heat maps (fictional company, illustrative data)
Page 3 of 7Risk profile and heat maps17 risks, 3 Critical, 12 High and 2 Medium, plotted today and after the roadmap, when none remains Critical or High.
Risk Register: Summary table (fictional company, illustrative data)
Page 4 of 7Summary tableEvery risk with likelihood, impact, score, rating, owner, target date and target rating.
Risk Register: Risk detail cards (fictional company, illustrative data)
Page 5 of 7Risk detail cardsThe first risk cards in full: statement, likelihood times impact, linked findings, treatment, target after treatment, owner and due date.
Risk Register: Risk detail: backups and accounts (fictional company, illustrative data)
Page 6 of 7Risk detail: backups and accountsPermanent data loss because backups can be deleted with production (R-03) and misuse of former staff and shared accounts (R-04).
Risk Register: Finding-to-risk traceability (fictional company, illustrative data)
Page 7 of 7Finding-to-risk traceabilityEvery one of the 28 findings linked to at least one business risk.

Click the page in the centre to open it full size, then zoom in to read every line.

04

PDF and Word · 13 pages

Next Steps and Security Roadmap

The 180-day plan. It sets today's measures against 30-day and 180-day targets, lays out 31 actions in four phases on a timeline, groups them into eight security projects with effort and success measures, and shows the expected reduction in risk and the operating rhythm that keeps the plan moving.

Who uses it

IT leadership and project owners who run the work; leadership who approve budget and owners.

What is included

  • Where you are and where you should be
  • 180-day timeline in four phases
  • 31 actions with their risks
  • Eight prioritized security projects
  • Effort, duration and success measures
  • Expected outcome and residual risk
  • Future goals for 6 to 18 months
  • Governance and operating rhythm

Sample · Fabrikam Civic Systems (fictional)

1 / 9

Next Steps and Security Roadmap: Cover page (fictional company, illustrative data)
Page 1 of 9Cover pageThe plan that follows the assessment, for the people who will carry it out.
Next Steps and Security Roadmap: Where you are and where you should be (fictional company, illustrative data)
Page 2 of 9Where you are and where you should beEleven measures with today's value and the 30-day and 180-day targets, from MFA coverage to restore testing.
Next Steps and Security Roadmap: 180-day roadmap and Phase 0 (fictional company, illustrative data)
Page 3 of 9180-day roadmap and Phase 031 actions in four phases on a timeline, and the five Phase 0 actions for the first seven days.
Next Steps and Security Roadmap: Phase 1 actions (fictional company, illustrative data)
Page 4 of 9Phase 1 actionsSeven actions for days 7 to 30 that reduce the three Critical risks to Medium.
Next Steps and Security Roadmap: Phase 2 and Phase 3 actions (fictional company, illustrative data)
Page 5 of 9Phase 2 and Phase 3 actionsSixteen actions for days 30 to 90 and three governance actions for days 90 to 180.
Next Steps and Security Roadmap: Recommended security projects (fictional company, illustrative data)
Page 6 of 9Recommended security projectsThe actions grouped into eight projects in priority order, starting with privileged access and identity hardening.
Next Steps and Security Roadmap: Project cards (fictional company, illustrative data)
Page 7 of 9Project cardsEach project's objective, key activities, risks addressed, success measures, duration and effort.
Next Steps and Security Roadmap: Expected outcome (fictional company, illustrative data)
Page 8 of 9Expected outcomeCurrent and target scores for the top 12 risks and the residual heat map after the roadmap.
Next Steps and Security Roadmap: Governance and operating rhythm (fictional company, illustrative data)
Page 9 of 9Governance and operating rhythmWeekly, monthly, quarterly and annual reviews, a licensing check and how OC Security Audit can help.

Click the page in the centre to open it full size, then zoom in to read every line.

05

Excel · 26 sheets

Technical Findings Workbook

Everything in the reports, in a workbook your team keeps working in. It includes the completed OC Security Audit NIST 800-53 template, one sheet per control family, the remediation tracker, all findings, the risk register with live scoring, the remediation plan, the evidence inventories and domain scores. Yellow columns are for your team to maintain.

Who uses it

Whoever tracks remediation; the source for your plan of action and milestones and for customer follow-up questions.

What is included

  • Completed NIST 800-53 template
  • One sheet per control family
  • Remediation tracker
  • All findings with status columns
  • Risk register with live formulas
  • Remediation plan with percent complete
  • Accounts, privileged access and vulnerabilities
  • Servers, suppliers and critical systems
  • Strengths and domain scores

Sample · Fabrikam Civic Systems (fictional)

1 / 10

Technical Findings Workbook: Cover and Executive Scorecard (fictional company, illustrative data)
Page 1 of 10Cover and Executive ScorecardThe completed assessment template: client, scope and scorecard counts, 18 Critical and High items, 8 Medium, 2 Low and 7 implemented controls.
Technical Findings Workbook: Summary sheet (fictional company, illustrative data)
Page 2 of 10Summary sheetLive tables of findings by severity and risks by rating, with open, closed and percent closed, beside the charts.
Technical Findings Workbook: Access Control family sheet (fictional company, illustrative data)
Page 3 of 10Access Control family sheetOne sheet per family: answer, evidence, impact, likelihood, score and status for each control.
Technical Findings Workbook: Remediation Tracker (fictional company, illustrative data)
Page 4 of 10Remediation TrackerEvery control with its score, severity, status, owner, target date and finding and risk references.
Technical Findings Workbook: Findings sheet (fictional company, illustrative data)
Page 5 of 10Findings sheetAll 28 findings with observation, linked risks, owner and target date, and status columns your team maintains.
Technical Findings Workbook: Risk Register sheet (fictional company, illustrative data)
Page 6 of 10Risk Register sheet17 risks with likelihood and impact as inputs; score, rating and target rating recalculate automatically.
Technical Findings Workbook: Remediation Plan sheet (fictional company, illustrative data)
Page 7 of 10Remediation Plan sheetAll 31 roadmap actions by phase, with status, owner, due date and percent complete.
Technical Findings Workbook: Privileged Access sheet (fictional company, illustrative data)
Page 8 of 10Privileged Access sheetEvery privileged role assignment with MFA status and a review-decision column.
Technical Findings Workbook: Vulnerabilities sheet (fictional company, illustrative data)
Page 9 of 10Vulnerabilities sheetCritical and high vulnerabilities open more than 30 days, by server, with days open.
Technical Findings Workbook: Domain Scores sheet (fictional company, illustrative data)
Page 10 of 10Domain Scores sheetImplementation score, control counts and findings for each of the nine families.

Click the page in the centre to open it full size, then zoom in to read every line.

Want this for your own system?

Book a short scoping call. We will confirm your system, your baseline and a fixed price in writing before any work starts.

One gap, traced

How one finding flows through all five deliverables

Every number is consistent across the reports. Here is one control gap from the sample, followed from the technical finding to the row your team tracks.

F-01 · AC-6

Technical finding

Least Privilege, Critical: 11 permanent Global Administrators, including a shared account and a former employee.

R-01

Business risk

Takeover of the cloud environment through an administrator account: score 20 today, 10 after treatment.

PHASE 0-1

Roadmap actions

Actions 1 and 3 in the first seven days, action 7 by day 30: fewer administrators and just-in-time access.

WORKBOOK

Tracked to closure

The Findings and Remediation Plan sheets carry status, owner, due date and closure evidence.

Coverage

Control families covered in the sample

The sample is a focused assessment of 35 Moderate-baseline controls. The remaining families are recommended for a second phase, which the reports say plainly.

FamilyControlsImplemented / partial / notScoreFindings
AC Access Control62 / 3 / 1614
IA Identification and Authentication41 / 3 / 0683
CM Configuration Management40 / 3 / 1414
CP Contingency Planning40 / 3 / 1384
IR Incident Response41 / 3 / 0603
RA Risk Assessment31 / 2 / 0602
PL Planning31 / 1 / 1482
SI System and Information Integrity41 / 2 / 1543
SR Supply Chain Risk Management30 / 2 / 1223

Overall implementation score 51.3 out of 100 (needs improvement). Families recommended for a second phase: AU, SC, AT, PS, PE, MP, MA, CA, SA and PM.

Ali Hassani, CISO and CISSP, founder of OC Security Audit

Who leads the assessment

Led by Ali Hassani, CISO

Certified CISO (C|CISO) and CISSP with 25+ years in IT, cybersecurity, compliance and infrastructure, and dozens of Microsoft and Cisco certifications, including MCSE, MCITP, MCSA Security, CCNP and CCNA.

Every NIST 800-53 assessment is planned, performed and signed by Ali. The reports you receive look like this sample: consistent numbers, plain language for leadership, and enough technical detail for your team to fix each gap.

FAQ

Questions about the sample report

Is the sample report based on a real client?

No. Fabrikam Civic Systems is a fictional organization. Every name, account, server, supplier and figure in the sample is invented for illustration and does not describe any real customer.

Will my report look the same?

Yes. You receive the same five deliverables in the same format, with your own system, controls, findings, risks and roadmap. The number of pages depends on the number of controls in scope.

How many controls does the sample cover?

The sample is a focused assessment of 35 Moderate-baseline controls in nine families. A full Moderate-baseline assessment covers 287 controls and enhancements and produces longer technical and workbook deliverables.

Do we get Word and Excel files, or only PDFs?

Both. The four reports come as editable Word documents and PDFs, and the findings workbook is an Excel file your team keeps working in.

Can we share the report with our customers?

Yes. Many clients share the Executive Security Report or Risk Register with government or enterprise customers. The reports are marked confidential, so share them under your normal agreements.

How much does an assessment like this cost?

NIST 800-53 assessments start at $3,500. The final fixed price depends on the number of systems, the baseline and the controls in scope, and is confirmed in writing after a scoping call.

Does the report certify compliance?

No. It is an independent assessment. It does not certify compliance, it is not a FedRAMP third-party assessment and it is not an authorization decision.

ocsa grc hero fractional ciso

Get these five deliverables for your own system

Book a short scoping call and receive a written scope and fixed price before any work starts.

Or call 949-777-5567