Bruce Weygandt
All posts

Working with FedRAMP's new JSON schemas

FedRAMP 20x, Change management, React. 2 min read.

Fitting change requests into the Significant Change Notification schema, and building a viewer for Security Decision Records.

FedRAMP 20x published JSON schemas for significant change notifications (SCN) and security decision records (SDR). Both are a real improvement for automation. Neither fit neatly into how teams were already working.

Change requests

Change requests lived in a markdown merge request template. I compared each field against the SCN schema and found nine fields the template had nowhere to put.

certificationPackageOverviewUri
changeType
changeTypeExplanation
assessorName
relatedVulnerability
customerImpact
planAndTimeline.plannedCompletion
planAndTimeline.milestones[]
impactedControls[]
Schema fields the old template had no place for.

I rewrote the template with collapsible sections so engineers only open the parts their change needs. A long flat form would have been skipped. The next step is a small script that turns a completed merge request into valid SCN JSON.

A viewer for SDR files

An SDR describes a system boundary in JSON, which is great for machines and hard for reviewers. I built a React dashboard that turns one into something readable: systems by type and tier, encryption posture, a swim-lane boundary diagram, ports and protocols, and a control cross-reference.

Reviewers drag a file onto the page. It's checked against the schema structure first, and every number on screen is calculated from the file when it loads, so nothing goes stale.

The control cross-reference also separates controls the SDR fully supports, like boundary and encryption, from ones it only partly supports. I didn't want the dashboard to suggest more than the data shows.