Frameworks

Mapped to FedRAMP 20x and SOC 2.

We use two public frameworks as the yardstick for our own controls: the Key Security Indicators FedRAMP sets for Class C (Moderate) cloud services, and the AICPA Trust Services Criteria behind SOC 2.

FedRAMP 20x

Class C Moderate

46 Key Security Indicators in 10 areas, covering identity and access, cloud architecture, change management, logging, incident response and recovery planning.

  • IAM Identity and access
  • CNA Cloud native architecture
  • SVC Service configuration
  • CMT Change management
  • MLA Monitoring, logging and auditing
  • SCR Supply chain risk
  • PIY Policy and inventory
  • INR Incident response
  • RPL Recovery planning
  • CED Cybersecurity education

Areas from the FedRAMP Consolidated Rules for 2026

SOC 2

Trust Services Criteria

The AICPA criteria behind SOC 2 reports, covering security, availability, processing integrity, confidentiality and privacy. Below are the common criteria our day-to-day controls answer most directly.

CC6
Logical access Required MFA, passkeys and team-scoped access
CC7
System operations Audit events, alerts and vulnerability scanning
CC8
Change management Automated checks on every change and releases deployed by pipeline

Criteria from the AICPA Trust Services Criteria (2017, revised 2022)

Self-assessed, not certified. GovBrain is not FedRAMP certified and has not completed a SOC 2 examination by an independent auditor. We assess our controls against both frameworks ourselves, and we are glad to walk your security team through the mapping.

Ask for a walkthrough

Defense in depth

Four layers between the internet and your records.

Each layer has its own controls, so no single one has to hold on its own.

Layer 1Infrastructure

FedRAMP 20xCNA · CMTSOC 2CC8

  • Application, files and sign-in hosted on AWS in the United States
  • Short-lived deployment credentials, limited to the main branch
  • Least-privilege roles for deployment and background processing
  • Rate limits, request size limits and security headers on the API

Layer 2Identity and access

FedRAMP 20xIAMSOC 2CC6

  • Multi-factor authentication required on every account
  • Passkey sign-in with device verification
  • Minimum 12-character passwords, and no SMS codes
  • Signed tokens verified on every signed-in request

Layer 3Team isolation

FedRAMP 20xIAM · CNASOC 2CC6

  • Every record, file and form is scoped to your team
  • File access is checked against your team before a download link is issued
  • Members join by invitation; owners and admins manage the team
  • Partner upload links are private, expire after the period you set and are stored only as a hash

Layer 4Data protection

FedRAMP 20xSVCSOC 2CC6 · C1

  • TLS encryption for data in transit
  • Encryption at rest for stored records and files
  • Secrets kept out of source code, and every change scanned for leaks across the full history
  • Server-side document rendering with restricted network access

Your dataPursuits, Personnel, projects and past performance

Responsible AI

An assistant that can read, and that is all.

Brian helps your team write and fit documents. It works inside your team’s scope, can read your records but never change them, and every edit it makes in the editor can be undone.

Read your team’s recordsRead-only access

Allowed

Edit the document you have openEvery AI edit can be undone

Undoable

Change your recordsIt cannot write to them

Never

Save on your behalfNothing saves until you do

Never

Look outside your teamLookups always use your team’s scope

Never

Have its requests stored by the AI providerBrian sends them with storage turned off

Off

FAQ

Questions security teams ask.

Something we didn’t cover? Email the team and we’ll get back within a business day.

Is GovBrain FedRAMP certified or SOC 2 audited?

Not at this time. GovBrain is not FedRAMP certified and has not completed a SOC 2 examination. We map our controls to the FedRAMP 20x Class C Key Security Indicators and the SOC 2 Trust Services Criteria, assess ourselves against both, and are glad to walk your security team through that mapping.

Where is GovBrain hosted?

The application, files and sign-in run on Amazon Web Services in the United States, and records are stored in a managed MongoDB Atlas database. Releases are built, scanned and deployed by an automated pipeline that uses short-lived credentials.

Who can see our records?

Only members of your team. Every record, file and form is scoped to your team, members join by invitation, and file access is checked against your team before a download link is issued.

How is sign-in protected?

Multi-factor authentication is required on every account, with an authenticator app or a passkey. SMS codes are not used, passwords must be at least 12 characters, and signed tokens are verified on every signed-in request.

How do partners share their resumes and projects?

Through a private upload link that expires after the period you set, up to 30 days. Partners add their own Personnel and projects without an account, and GovBrain stores only a hash of each link’s secret token.

Can Brian change our data?

No. Brian has read-only access to your records. Its edits apply to the document you have open, nothing saves until you do, and every edit can be undone.

How do you handle vulnerabilities?

Dependencies are updated weekly, automated checks fail on high or critical advisories, every change is scanned for leaked secrets across the code history, and container images are scanned on every release. If you find an issue, report it using the details at the bottom of this page.

Responsible disclosure

Reporting a vulnerability

If you believe you have found a security issue in GovBrain, email hello@govbrain.org with the details. We acknowledge reports promptly and ask that you give us a reasonable time to fix an issue before disclosing it.

Report an issue