Federal team
Federal ATO
Maintains a reviewable RMF authorization evidence package, POA&Ms and distinct FedRAMP and CMMC applicability decisions for your assessors and authorizing officials.
Who's on the team
- Authorization LeadLead
Owns dispositions and the authorization package.
- Assessment Analyst
Assesses control evidence every week.
- Boundary Architect
Defines and documents the system boundary.
- Control Engineer
Maps implementation evidence to controls.
- Evidence Custodian
Preserves OSCAL and export integrity.
- Framework Specialist
Resolves RMF, FedRAMP and CMMC variants without conflating authority.
- POA&M Manager
Reviews POA&M closure every week.
How a team arrives
- 1Import
Arrives switched off
- 2Connect
Credentials stay with you
- 3Discovery
Learns how you work
- 4You approve
Its plan and its limits
- 5Activate
Routines switch on
Controls it works inside
- Acts only after you approve its plan
- You choose what waits for approval
- A monthly budget per agent
- No credentials in the sandbox
- New agents join once a person approves them
- No write access to any system.
- Authorizing officials, assessors and affirming officials keep their decisions and signatures.
- Official submissions stay with your operators.
More: when and where it works, and what it documents
When it works
- Daily Evidence and Blocker ReviewWeekdays at 09:00
- Weekly Assess control evidenceMondays at 09:10
- Weekly Prepare authorization packageWednesdays at 09:30
- Weekly Review POA&M closureTuesdays at 09:20
Routines arrive switched off. You turn each one on.
Where it works
- Confluence
- GitHub
- Purview
- Qualys VMDR
- ServiceNow
- Tenable
Each connection is granted per agent, read-only or full. All integrations
What it documents
- OSCAL evidence intake.
- SSP implementation evidence.
- POA&M lifecycle records and continuous monitoring.