StateRAMP state/local government cloud authorization

version
0.1.0
GitHub stars
436

Install

/plugin install stateramp@grc-engineering-suite

Run it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.

Contents

Discovered from source

Skills 1

StateRAMP Expert

Deep expertise in StateRAMP (State Risk and Authorization Management Program) for cloud service providers serving state and local government agencies.

Expertise Areas

StateRAMP Program Overview

Purpose: Standardized, reusable security authorization framework for state and local government cloud services Authority: State-level (not federal) Based On: FedRAMP framework, adapted for state/local needs Launch: 2015 (evolved from state reciprocity initiatives) Current Status: 15+ participating states, growing adoption

Program Goals:

  • Reduce duplicative state-by-state assessments
  • Lower costs for CSPs and states
  • Standardize security baselines
  • Enable reciprocity across states
  • Accelerate secure cloud adoption

StateRAMP vs FedRAMP Comparison

AspectStateRAMPFedRAMP
AuthorityState/local governmentFederal government
GovernanceStateRAMP Impact CouncilGSA, DHS, DOD (JAB)
Market50 states, territories, localitiesFederal agencies
Cost20-30% lower typically$200K-$1M+
Timeline6-18 months12-24+ months
ReciprocityAcross participating statesAcross federal agencies
ControlsNIST 800-53 (state-tailored)NIST 800-53 Rev 5
Impact LevelsLow, ModerateLow, Moderate, High
AssessmentStateRAMP-recognized 3PAOFedRAMP-authorized 3PAO

Similarities:

  • NIST 800-53 control framework
  • Third-party assessment required
  • Continuous monitoring mandatory
  • Similar documentation (SSP, SAP, SAR, POA&M)
  • Annual assessments
  • Significant change notifications

Key Differences:

  • Scope: States vs. federal agencies
  • Data Types: State data vs. federal CUI/FCI
  • Cost: StateRAMP generally less expensive (smaller scope, faster timelines)
  • Flexibility: States may add requirements, less rigid than FedRAMP
  • Market Size: 50 states + locals vs. federal enterprise
  • Leverage: FedRAMP authorization helps StateRAMP but not reciprocal

StateRAMP Impact Levels

StateRAMP uses FIPS 199 categorization:

Low Impact (~125 controls):

  • Data: Public information, non-sensitive
  • Systems: Public-facing services, informational systems
  • Impact: Limited adverse effect if compromised
  • Examples:
    • Event calendars
    • Public document repositories
    • General constituent communication
    • Non-sensitive form submissions
  • Cost: $50K-$150K assessment + remediation
  • Timeline: 6-12 months

Moderate Impact (~325 controls):

  • Data: CUI, PII, PHI, financial, law enforcement sensitive
  • Systems: Mission-critical, sensitive data processing
  • Impact: Serious adverse effect if compromised
  • Examples:
    • Tax systems
    • Benefits administration (SNAP, Medicaid)
    • HR/Payroll systems
    • Law enforcement case management
    • Licensing with PII
    • Healthcare portals
    • Financial management
  • Cost: $150K-$400K assessment + remediation
  • Timeline: 12-18 months

High Impact:

  • Not currently defined in StateRAMP
  • States with high-impact needs typically use FedRAMP High or custom authorizations
  • May emerge in future StateRAMP versions

NIST 800-53 Control Families

StateRAMP uses NIST SP 800-53 control framework:

18 Control Families:

  1. Access Control (AC) - 25 controls at Moderate

    • Account management (AC-2)
    • Least privilege (AC-6)
    • Remote access (AC-17)
    • Wireless access (AC-18)
    • Access control for mobile devices (AC-19)
  2. Awareness and Training (AT) - 5 controls

    • Security awareness (AT-2)
    • Role-based training (AT-3)
    • Security training records (AT-4)
  3. Audit and Accountability (AU) - 12 controls

    • Audit events (AU-2)
    • Content of audit records (AU-3)
    • Audit storage capacity (AU-4)
    • Response to audit failures (AU-5)
    • Audit review, analysis, reporting (AU-6)
    • Audit reduction and report generation (AU-7)
    • Time stamps (AU-8)
    • Protection of audit information (AU-9)
    • Audit record retention (AU-11)
  4. Security Assessment and Authorization (CA) - 9 controls

    • Security assessments (CA-2)
    • System interconnections (CA-3)
    • Plan of action and milestones (CA-5)
    • Security authorization (CA-6)
    • Continuous monitoring (CA-7)
    • Penetration testing (CA-8)
  5. Configuration Management (CM) - 11 controls

    • Baseline configuration (CM-2)
    • Configuration change control (CM-3)
    • Security impact analysis (CM-4)
    • Access restrictions for change (CM-5)
    • Configuration settings (CM-6)
    • Least functionality (CM-7)
    • Information system component inventory (CM-8)
  6. Contingency Planning (CP) - 10 controls

    • Contingency plan (CP-2)
    • Contingency training (CP-3)
    • Contingency plan testing (CP-4)
    • Information system backup (CP-9)
    • Information system recovery and reconstitution (CP-10)
  7. Identification and Authentication (IA) - 11 controls

    • Identification and authentication (organizational users) (IA-2)
    • Device identification and authentication (IA-3)
    • Identifier management (IA-4)
    • Authenticator management (IA-5)
    • Authenticator feedback (IA-6)
    • Cryptographic module authentication (IA-7)
  8. Incident Response (IR) - 10 controls

    • Incident response training (IR-2)
    • Incident response testing (IR-3)
    • Incident handling (IR-4)
    • Incident monitoring (IR-5)
    • Incident reporting (IR-6)
    • Incident response assistance (IR-7)
    • Incident response plan (IR-8)
  9. Maintenance (MA) - 6 controls

    • System maintenance policy and procedures (MA-1)
    • Controlled maintenance (MA-2)
    • Maintenance tools (MA-3)
    • Nonlocal maintenance (MA-4)
    • Maintenance personnel (MA-5)
    • Timely maintenance (MA-6)
  10. Media Protection (MP) - 8 controls

    • Media protection policy (MP-1)
    • Media access (MP-2)
    • Media marking (MP-3)
    • Media storage (MP-4)
    • Media transport (MP-5)
    • Media sanitization (MP-6)
    • Media use (MP-7)
  11. Physical and Environmental Protection (PE) - 18 controls

    • Physical access authorizations (PE-2)
    • Physical access control (PE-3)
    • Access control for transmission medium (PE-4)
    • Access control for output devices (PE-5)
    • Monitoring physical access (PE-6)
    • Visitor control (PE-8)
    • Delivery and removal (PE-16)
  12. Planning (PL) - 9 controls

    • Security planning policy and procedures (PL-1)
    • System security plan (PL-2)
    • Rules of behavior (PL-4)
    • Privacy impact assessment (PL-8)
  13. Personnel Security (PS) - 8 controls

    • Position categorization (PS-2)
    • Personnel screening (PS-3)
    • Personnel termination (PS-4)
    • Personnel transfer (PS-5)
    • Access agreements (PS-6)
    • Third-party personnel security (PS-7)
  14. Risk Assessment (RA) - 6 controls

    • Risk assessment policy (RA-1)
    • Security categorization (RA-2)
    • Risk assessment (RA-3)
    • Vulnerability scanning (RA-5)
  15. System and Services Acquisition (SA) - 22 controls

    • Acquisition process (SA-2)
    • System development life cycle (SA-3)
    • Acquisitions (SA-4)
    • Information system documentation (SA-5)
    • Developer configuration management (SA-10)
    • Developer security testing (SA-11)
  16. System and Communications Protection (SC) - 45 controls

    • Application partitioning (SC-2)
    • Security function isolation (SC-3)
    • Information in shared resources (SC-4)
    • Denial of service protection (SC-5)
    • Boundary protection (SC-7)
    • Transmission confidentiality and integrity (SC-8)
    • Network disconnect (SC-10)
    • Cryptographic key management (SC-12)
    • Use of cryptography (SC-13)
    • Public access protections (SC-15)
    • Mobile code (SC-18)
    • Secure name/address resolution (SC-20, SC-21)
    • Protection of information at rest (SC-28)
  17. System and Information Integrity (SI) - 17 controls

    • Flaw remediation (SI-2)
    • Malicious code protection (SI-3)
    • Information system monitoring (SI-4)
    • Security alerts and advisories (SI-5)
    • Security functionality verification (SI-6)
    • Software and information integrity (SI-7)
    • Spam protection (SI-8)
    • Information input validation (SI-10)
    • Error handling (SI-11)
  18. Program Management (PM) - 16 controls

    • Information security program plan (PM-1)
    • Senior information security officer (PM-2)
    • Information security resources (PM-3)
    • Plan of action and milestones process (PM-4)
    • Critical infrastructure plan (PM-8)
    • Risk management strategy (PM-9)

Control Responsibility Matrix

CSP Responsibility: Cloud Service Provider implements and manages Customer Responsibility: Government agency implements and manages Shared Responsibility: Both CSP and customer have roles

Common Responsibility Patterns:

CSP-Heavy (SaaS):

  • Most SC (System and Communications Protection)
  • Most PE (Physical and Environmental)
  • Most SI (System and Information Integrity)
  • Infrastructure-level controls

Customer-Heavy:

  • AC-2 (Account Management) - who gets access
  • AT (Awareness and Training) - agency personnel
  • PS (Personnel Security) - agency employees
  • PL (Planning) - agency-specific policies

Shared:

  • IR (Incident Response) - both must coordinate
  • AU (Audit) - CSP collects, customer reviews
  • CA (Assessment) - both assess their components
  • RA (Risk Assessment) - different scopes

Inherited Controls:

  • CSP from infrastructure provider (AWS, Azure, GCP)
  • Customer from CSP
  • Clear documentation of inheritance critical

StateRAMP Authorization Process

Phase 1: Readiness (1-3 months)

  1. Gap Assessment:

    • Evaluate current security posture
    • Identify control deficiencies
    • Estimate remediation effort
    • Determine readiness timeline
  2. Impact Level Selection:

    • FIPS 199 categorization
    • Data sensitivity analysis
    • Confidentiality/Integrity/Availability ratings
    • Low vs. Moderate determination
  3. Scoping:

    • Define authorization boundary
    • Identify system components
    • External connections
    • Data flows

Phase 2: Implementation (3-9 months)

  1. Control Implementation:

    • Address gap assessment findings
    • Deploy security technologies
    • Develop policies and procedures
    • Configure security settings
  2. Documentation:

    • System Security Plan (SSP)
    • Privacy Impact Assessment (PIA)
    • Contingency Plan
    • Incident Response Plan
    • Configuration Management Plan
    • Rules of Behavior

Phase 3: Assessment (2-3 months)

  1. 3PAO Selection:

    • Choose StateRAMP-recognized assessor
    • Negotiate scope and cost
    • Develop assessment timeline
  2. Security Assessment Plan (SAP):

    • 3PAO develops testing methodology
    • Review and approve scope
    • Finalize schedule
  3. Assessment Execution:

    • Vulnerability scanning
    • Penetration testing
    • Control validation (examine/interview/test)
    • Evidence review
    • Findings documentation
  4. Security Assessment Report (SAR):

    • 3PAO documents results
    • Risk ratings for deficiencies
    • Recommendations

Phase 4: Authorization (1-2 months)

  1. POA&M Development:

    • Document deficiencies
    • Remediation plans
    • Milestone dates
    • Risk acceptance
  2. ATO Package Submission:

    • SSP, SAP, SAR, POA&M
    • Supporting documentation
    • Submit to state authorizing official
  3. State Review:

    • Authorizing official evaluates risk
    • May request clarifications
    • Risk acceptance decision
  4. ATO Issuance:

    • Authorization to Operate granted
    • Typically 3-year validity
    • Conditional on continuous monitoring

Phase 5: Continuous Monitoring (Ongoing)

  1. Monthly Deliverables:

    • POA&M status updates
    • Vulnerability scan results
    • Significant changes
    • Incident reports
  2. Annual Assessment:

    • 3PAO reassessment
    • Updated SAR
    • Control validation
    • POA&M refresh
  3. Significant Changes:

    • 30-day notification required
    • May require supplemental assessment
    • Could trigger re-authorization

Third-Party Assessment Organizations (3PAO)

StateRAMP 3PAO Recognition:

  • StateRAMP maintains list of recognized assessors
  • Must demonstrate competency
  • Similar to FedRAMP 3PAO but state-focused
  • Some FedRAMP 3PAOs also do StateRAMP

3PAO Selection Criteria:

  1. Experience: StateRAMP assessments completed
  2. Expertise: Understanding of state requirements
  3. Cost: $50K-$300K+ depending on scope
  4. Timeline: Availability and schedule
  5. Reputation: References and quality
  6. State Relationships: Known to state authorizing officials

3PAO Deliverables:

  • Security Assessment Plan (SAP)
  • Security Assessment Report (SAR)
  • Penetration test report
  • Vulnerability scan results
  • Risk ratings and recommendations

Participating States

Current Participants (15+ as of 2024):

  • California (CA)
  • Texas (TX)
  • Florida (FL)
  • New York (NY)
  • Illinois (IL)
  • Michigan (MI)
  • Pennsylvania (PA)
  • Ohio (OH)
  • Georgia (GA)
  • North Carolina (NC)
  • Colorado (CO)
  • Arizona (AZ)
  • Maryland (MD)
  • Massachusetts (MA)
  • Washington (WA)

StateRAMP Impact Council:

  • Coordinating body across states
  • Reviews and approves authorizations
  • Maintains program standards
  • Facilitates reciprocity

Reciprocity Model:

  • One StateRAMP ATO accepted by multiple states
  • Individual states may add supplemental requirements
  • Reduces redundant assessments
  • Lowers costs for CSPs and states

State-Specific Requirements

Common Variations:

  1. Data Residency:

    • US-Based: Most common requirement
    • State-Specific: Rare, but some states for certain data
    • No Restriction: Some states if adequate protections
  2. Privacy Laws:

    • California: CCPA (California Consumer Privacy Act)
    • New York: SHIELD Act
    • Colorado: Colorado Privacy Act (CPA)
    • Illinois: BIPA (Biometric Information Privacy Act)
    • Virginia: VCDPA
    • Others emerging
  3. Breach Notification:

    • Timelines: 24 hours to 90 days (varies by state)
    • Thresholds: Number of affected residents
    • Recipients: Attorney General, residents, media
    • State-specific reporting portals
  4. Records Management:

    • Public records laws (all states)
    • Retention requirements (varies)
    • E-discovery obligations
    • Freedom of Information Act (FOIA) equivalents
  5. Sector-Specific:

    • Criminal Justice: CJIS requirements
    • Education: FERPA + state laws
    • Healthcare: HIPAA + state laws
    • Tax: IRS 1075 + state requirements

State Contacts:

  • Each state has designated StateRAMP coordinator
  • Usually within state IT or security office
  • Check StateRAMP website for current contacts

Common Implementation Challenges

Technical Gaps:

  1. Multi-Factor Authentication (IA-2):

    • Not implemented for all users
    • Legacy systems without MFA capability
    • SMS-based MFA (insufficient for Moderate)
    • Phishing-resistant MFA needed
  2. Encryption:

    • At Rest (SC-28): Unencrypted databases, file stores
    • In Transit (SC-8): HTTP instead of HTTPS, weak TLS
    • Key Management (SC-12): Poor key rotation, storage
  3. Logging and Monitoring:

    • Audit Logging (AU family): Insufficient events captured
    • Log Retention (AU-11): Too short or inconsistent
    • Monitoring (SI-4): No SIEM, manual review only
    • Log Protection (AU-9): Logs not tamper-proof
  4. Vulnerability Management (RA-5):

    • Irregular scanning
    • Slow patching (SI-2)
    • No vulnerability tracking
    • Missing compensating controls for unpatchable systems
  5. Incident Response (IR family):

    • No formal IR plan (IR-8)
    • Untested procedures (IR-3)
    • Unclear reporting (IR-6)
    • No forensics capability (IR-4)
  6. Access Control:

    • Account Management (AC-2): No periodic reviews
    • Least Privilege (AC-6): Over-privileged accounts
    • Session Management: No auto-logout
    • Remote Access (AC-17): Weak VPN, no MFA

Documentation Gaps:

  1. System Security Plan (SSP):

    • Generic template text, not customized
    • Missing diagrams or outdated
    • Controls not actually implemented as described
    • No evidence references
  2. Policies and Procedures:

    • Outdated or missing
    • Not followed in practice
    • Inconsistent with actual operations
    • No version control
  3. Contingency Planning (CP family):

    • No contingency plan or untested
    • Backup not validated (CP-9)
    • No disaster recovery
    • Missing RTO/RPO definitions

Organizational Challenges:

  1. Resource Constraints:

    • Limited security staff
    • Budget limitations
    • Competing priorities
  2. Executive Support:

    • Lack of C-suite commitment
    • Insufficient resources allocated
    • Security seen as checkbox, not priority
  3. Change Management:

    • Resistance to new processes
    • "We've always done it this way"
    • User pushback on MFA, security controls
  4. Third-Party Dependencies:

    • Cloud infrastructure provider (AWS, Azure, GCP)
    • SaaS components
    • Unclear inherited controls
    • Vendor coordination challenges

Critical Success Factors

Technical Excellence:

  1. Strong Security Architecture:

    • Defense in depth
    • Network segmentation
    • Encryption everywhere
    • Zero trust principles
  2. Robust Monitoring:

    • SIEM or log aggregation
    • Automated alerting
    • Continuous scanning
    • Threat intelligence
  3. Mature Processes:

    • Configuration management
    • Change control
    • Vulnerability management
    • Incident response

Documentation Quality:

  1. Accurate SSP:

    • Specific, not generic
    • Evidence-based
    • Current diagrams
    • Clear inheritance
  2. Complete Policies:

    • Cover all control families
    • Practical and followed
    • Regularly reviewed
    • Version controlled

Organizational Readiness:

  1. Executive Sponsorship:

    • C-suite commitment
    • Adequate resources
    • Strategic priority
  2. Dedicated Team:

    • Security expertise
    • Compliance knowledge
    • Project management
    • Technical skills
  3. Culture of Security:

    • Security awareness
    • User training
    • Continuous improvement
    • Risk-based decision making

Strategic Planning:

  1. Right-Sized Scope:

    • Not too broad (hard to secure)
    • Not too narrow (limits functionality)
    • Clear boundaries
    • Well-documented
  2. Realistic Timeline:

    • Adequate remediation time
    • Buffer for unexpected issues
    • Phased approach if needed
  3. Multi-State Strategy:

    • Start with one state, expand
    • Understand state variations
    • Build flexibility for state-specific needs
    • Engage state coordinators early

Cost Considerations

Low Impact Authorization:

  • Gap Assessment: $10K-$25K
  • Remediation: $30K-$100K (tools, consulting)
  • Documentation: $15K-$30K
  • 3PAO Assessment: $40K-$80K
  • Ongoing Monitoring: $20K-$40K/year
  • Total Initial: $95K-$235K
  • Annual Maintenance: $40K-$80K

Moderate Impact Authorization:

  • Gap Assessment: $20K-$50K
  • Remediation: $100K-$300K (tools, consulting, development)
  • Documentation: $30K-$60K
  • 3PAO Assessment: $100K-$250K
  • Ongoing Monitoring: $50K-$100K/year
  • Total Initial: $250K-$660K
  • Annual Maintenance: $100K-$200K

Cost Variables:

  • System complexity and size
  • Current security maturity
  • Number of deficiencies
  • Tools/infrastructure needed
  • Internal vs. external resources
  • 3PAO rates and scope
  • Number of states (multi-state complexity)

Cost Savings vs. Per-State:

  • StateRAMP: One authorization, multiple states
  • Per-State: Redundant assessments, $100K+ per state
  • ROI: Positive if serving 2+ states
  • Break-even: Typically at 2-3 states

Timeline Estimates

Low Impact (6-12 months):

  • Readiness: 1-2 months
  • Implementation: 2-4 months
  • Assessment: 1-2 months
  • Authorization: 1-2 months
  • Buffer: 1-2 months

Moderate Impact (12-18 months):

  • Readiness: 2-3 months
  • Implementation: 4-8 months
  • Assessment: 2-3 months
  • Authorization: 1-2 months
  • Buffer: 2-3 months

Accelerated Path (if mature security posture):

  • Low: 4-6 months
  • Moderate: 8-12 months

Factors Causing Delay:

  • Major security gaps requiring development
  • Procurement delays (tools, infrastructure)
  • Resource constraints (limited staff)
  • Organizational resistance
  • 3PAO scheduling conflicts
  • State review backlog

Continuous Monitoring Requirements

Monthly Deliverables:

  1. POA&M Updates:

    • Status of open items
    • Milestone progress
    • Newly identified deficiencies
    • Closed items with evidence
  2. Vulnerability Scans:

    • Monthly authenticated scans
    • Vulnerability remediation tracking
    • False positive analysis
    • Scan reports
  3. Significant Changes:

    • New connections or services
    • Architecture changes
    • New data types
    • Risk impact analysis
  4. Incident Reports:

    • Security incidents
    • Root cause analysis
    • Corrective actions
    • Lessons learned

Annual Assessment:

  • 3PAO reassessment required
  • Control sampling (subset of controls)
  • Updated SAR
  • Renewed ATO

Triggers for Re-Authorization:

  • Impact level change (Low → Moderate)
  • Major architecture redesign
  • Significant security incidents
  • Failure to maintain continuous monitoring
  • Accumulation of high-risk POA&M items

Comparison to Other Frameworks

StateRAMP + FedRAMP:

  • FedRAMP authorization helpful for StateRAMP
  • Similar controls, documentation, processes
  • FedRAMP more rigorous (especially JAB)
  • Can leverage FedRAMP SSP for StateRAMP
  • Not reciprocal (StateRAMP doesn't satisfy FedRAMP)

StateRAMP + SOC 2:

  • Both commonly required by government customers
  • SOC 2 focuses on trust service criteria
  • StateRAMP is authorization, SOC 2 is attestation
  • Different scopes and purposes
  • Can be complementary

StateRAMP + ISO 27001:

  • ISO 27001 is international standard
  • StateRAMP is US state-specific
  • Some control overlap
  • ISO certification may help StateRAMP readiness
  • Not substitutes for each other

StateRAMP + CJIS:

  • CJIS for criminal justice information
  • Required by FBI for law enforcement data
  • More stringent than StateRAMP Moderate
  • StateRAMP + CJIS may be needed for law enforcement systems
  • Different authorization authorities

Market and Business Considerations

Target Market:

  • SaaS providers to state/local government
  • Cloud infrastructure for state agencies
  • Managed service providers
  • Healthcare (state Medicaid)
  • Education (state universities, K-12)
  • Public safety and law enforcement
  • Social services (benefits, licensing)

Competitive Advantage:

  • Differentiates from competitors
  • Required for many RFPs
  • Demonstrates security maturity
  • Reduces sales friction
  • Enables multi-state expansion

Market Size:

  • 50 states + territories
  • 3,000+ counties
  • 19,000+ municipalities
  • $7+ trillion state/local spending
  • Growing cloud adoption

ROI Considerations:

  • Upfront cost: $95K-$660K
  • Annual maintenance: $40K-$200K
  • Market access: Potentially millions in contracts
  • Sales cycle: Faster with StateRAMP
  • Win rate: Higher for compliant vendors

Capabilities

  • StateRAMP impact level selection (Low vs. Moderate)
  • FIPS 199 security categorization
  • NIST 800-53 control implementation guidance (all families, 325+ controls)
  • System Security Plan (SSP) development and review
  • Security Assessment Plan (SAP) guidance
  • Gap assessment and remediation roadmaps
  • 3PAO selection and management
  • ATO package preparation (SSP, SAP, SAR, POA&M)
  • Continuous monitoring program design
  • State-specific requirement analysis (15+ states)
  • Multi-state authorization strategy
  • Privacy law compliance (CCPA, SHIELD, CPA, BIPA, etc.)
  • Data residency and sovereignty guidance
  • Breach notification procedures (state-by-state)
  • Public records law compliance
  • Control inheritance documentation (CSP/customer/shared)
  • FedRAMP to StateRAMP translation
  • Cost estimation and timeline planning
  • Significant change assessment
  • Annual assessment preparation

Commands 5

StateRAMP Assessment

Evaluates organizational readiness for StateRAMP (State Risk and Authorization Management Program) authorization to provide cloud services to state and local governments.

Arguments

  • $1 - Impact level (required: low, moderate)
  • $2 - Target state (optional: specific state or "multi-state")

StateRAMP Overview

Purpose: Standardized security framework for state and local government cloud services Based On: FedRAMP framework, adapted for state/local needs Benefit: Single authorization accepted by multiple states Participants: 15+ states and growing (CA, TX, FL, NY, IL, etc.)

Impact Levels

StateRAMP Low (~125 controls)

  • Data Type: Low-impact public information
  • Systems: Non-sensitive applications, public-facing services
  • Examples: Event calendars, public forms, general information systems
  • Assessment: Third-party assessor required
  • Timeline: 6-12 months typical
  • Cost: $50K-$150K assessment + remediation

StateRAMP Moderate (~325 controls)

  • Data Type: Controlled Unclassified Information (CUI), PII, sensitive data
  • Systems: Finance, HR, law enforcement, healthcare, licensing
  • Examples: Tax systems, benefits administration, case management
  • Assessment: Third-party assessor required
  • Timeline: 12-18 months typical
  • Cost: $150K-$400K assessment + remediation

StateRAMP vs FedRAMP Differences

Similarities:

  • Based on NIST 800-53 controls
  • Continuous monitoring required
  • Third-party assessment organization (3PAO)
  • Similar documentation (SSP, SAP, SAR, POA&M)

Key Differences:

  1. Scope: State/local government (not federal)
  2. Reciprocity: State-level acceptance (not federal agencies)
  3. Control Set: Tailored for state needs (fewer federal-specific requirements)
  4. Cost: Generally 20-30% lower than FedRAMP
  5. Timeline: Slightly faster (no JAB option, state-sponsored only)
  6. Flexibility: States may add specific requirements

Authorization Process

Phase 1: Preparation (3-6 months)

  1. Determine impact level (Low vs Moderate)
  2. Define system boundaries and data flows
  3. Gap assessment against StateRAMP controls
  4. Remediation planning and implementation
  5. Policy and procedure documentation

Phase 2: Documentation (2-4 months)

  1. System Security Plan (SSP): Comprehensive security documentation
  2. Security Assessment Plan (SAP): Testing methodology
  3. Privacy Impact Assessment (PIA): For PII/sensitive data
  4. Contingency Plan: Business continuity and disaster recovery
  5. Incident Response Plan: Security event handling

Phase 3: Assessment (2-3 months)

  1. Select StateRAMP-recognized 3PAO
  2. Readiness assessment review
  3. On-site security assessment
  4. Penetration testing and vulnerability scanning
  5. Control validation and evidence review

Phase 4: Authorization (1-2 months)

  1. Security Assessment Report (SAR) delivery
  2. Plan of Action & Milestones (POA&M) for deficiencies
  3. State authorization official review
  4. Authorization to Operate (ATO) issuance
  5. Continuous monitoring activation

Assessment Output

  1. Readiness Score: Overall compliance percentage by impact level

  2. Control Family Gaps: Which NIST 800-53 families need work

    • Access Control (AC)
    • Awareness and Training (AT)
    • Audit and Accountability (AU)
    • Security Assessment and Authorization (CA)
    • Configuration Management (CM)
    • Contingency Planning (CP)
    • Identification and Authentication (IA)
    • Incident Response (IR)
    • Maintenance (MA)
    • Media Protection (MP)
    • Physical and Environmental Protection (PE)
    • Planning (PL)
    • Personnel Security (PS)
    • Risk Assessment (RA)
    • System and Communications Protection (SC)
    • System and Information Integrity (SI)
  3. State-Specific Requirements: Variations by target state(s)

  4. Documentation Readiness: SSP, SAP, POA&M completion status

  5. Technical Gaps: Security controls requiring implementation

  6. Timeline Projection: Estimated time to ATO

  7. Cost Estimate: Assessment, remediation, and ongoing monitoring

  8. 3PAO Recommendations: Qualified assessor organizations

Common Implementation Gaps

  1. Multi-Factor Authentication (IA-2):

    • Not implemented for all users
    • Legacy systems without MFA support
    • Inconsistent enforcement
  2. Encryption (SC-8, SC-13, SC-28):

    • Data at rest not encrypted
    • Transit encryption gaps
    • Weak cryptographic algorithms
  3. Continuous Monitoring (CA-7, SI-4):

    • Manual processes instead of automated
    • Insufficient log aggregation
    • No SIEM or security monitoring platform
  4. Incident Response (IR family):

    • No formal IR plan
    • Untested procedures
    • Unclear escalation paths
  5. Vulnerability Management (RA-5):

    • Irregular scanning
    • Slow patching processes
    • No vulnerability remediation tracking
  6. Access Control (AC-2, AC-6):

    • Excessive privileged accounts
    • No periodic access reviews
    • Lack of least privilege implementation

Multi-State Considerations

StateRAMP Impact Council:

  • Coordinates across participating states
  • Reviews and approves authorizations
  • Maintains reciprocity agreements

State Acceptance:

  • Individual states may accept StateRAMP ATO
  • Some states require supplemental reviews
  • State-specific addendums possible

Continuous Monitoring:

  • Monthly deliverables to states
  • Annual assessment required
  • Significant change notifications within 30 days

Examples

# Full Low impact assessment
/stateramp:assess low

# Moderate impact for California
/stateramp:assess moderate CA

# Multi-state Moderate assessment
/stateramp:assess moderate multi-state

Next Steps

After assessment:

  1. Use /stateramp:impact-select to validate impact level choice
  2. Use /stateramp:documentation for ATO package guidance
  3. Use /stateramp:state-specific to understand state variations
  4. Engage stateramp-expert skill for detailed implementation guidance

StateRAMP Documentation Guidance

Provides comprehensive guidance on creating StateRAMP Authorization to Operate (ATO) package documentation.

Arguments

  • $1 - Document type (optional: ssp, sap, sar, poam, all)
  • $2 - Impact level (optional: low, moderate)

Required ATO Package Documents

StateRAMP requires four core documents for authorization:

  1. SSP - System Security Plan
  2. SAP - Security Assessment Plan
  3. SAR - Security Assessment Report
  4. POA&M - Plan of Action & Milestones

Plus supporting documents:

  • Privacy Impact Assessment (PIA)
  • Contingency Plan (CP)
  • Incident Response Plan (IRP)
  • Configuration Management Plan
  • Rules of Behavior
  • Control Implementation Summary (CIS)
  • Inventory Workbook

System Security Plan (SSP)

Purpose

Comprehensive description of the system, security controls, and implementation details.

Required Sections

1. Information System Name/Title

  • Official system name
  • Unique identifier
  • Version/release

2. System Categorization

  • FIPS 199 impact level (Low/Moderate)
  • Confidentiality/Integrity/Availability ratings
  • Justification for categorization

3. Information System Owner

  • Cloud Service Provider (CSP) organization
  • Responsible officials
  • Contact information

4. Authorizing Official

  • State agency sponsor
  • Authorization decision authority

5. System Description

  • Purpose and functionality
  • User base and access methods
  • System architecture
  • Technology stack
  • Deployment model (SaaS, PaaS, IaaS)

6. System Environment

  • Architecture Diagrams:
    • Network topology
    • Authorization boundary
    • Data flows
    • External connections
  • Infrastructure:
    • Data centers and locations
    • Cloud service layers
    • Virtualization details
    • Hardware specifications

7. Security Control Implementation

  • For each NIST 800-53 control:
    • Control baseline (Low: ~125, Moderate: ~325)
    • Implementation status (Implemented/Partially Implemented/Not Implemented)
    • Responsibility (CSP/Customer/Shared)
    • Implementation description (HOW control is met)
    • Evidence artifacts

8. Attachments

  • System architecture diagrams
  • Network diagrams
  • Data flow diagrams
  • Authorization boundary diagram
  • User guides
  • Standard Operating Procedures (SOPs)
  • Policies and procedures

SSP Best Practices

Be Specific:

  • ❌ "We use encryption"
  • ✅ "AES-256 encryption for data at rest, TLS 1.2+ for data in transit"

Show Evidence:

  • Reference specific configurations
  • Name security tools and technologies
  • Provide version numbers
  • Include responsible parties

Use Control Inheritance:

  • Clearly mark inherited controls (from cloud provider)
  • Document shared responsibilities
  • Attach provider SSP/compliance docs

Common SSP Mistakes:

  1. Generic copy/paste from templates
  2. No evidence of actual implementation
  3. Vague statements without technical details
  4. Missing diagrams or outdated diagrams
  5. Inconsistent control numbering
  6. Not addressing all control enhancements

SSP Page Count

  • Low: 150-300 pages typical
  • Moderate: 300-600+ pages typical

Security Assessment Plan (SAP)

Purpose

Defines how the 3PAO will assess security controls during the authorization process.

Required Sections

1. Assessment Methodology

  • Testing approach
  • Tools to be used
  • Sampling methodology

2. Scope

  • Controls to be assessed
  • Systems and components in scope
  • Boundaries and limitations

3. Assessment Procedures

  • For each control:
    • Test objectives
    • Examine: Documentation review
    • Interview: Personnel to interview
    • Test: Technical validation methods

4. Rules of Engagement

  • Assessment schedule
  • Access requirements
  • Points of contact
  • Escalation procedures

5. Penetration Testing

  • Scope and rules of engagement
  • Testing methodology
  • Authorized tools
  • Reporting requirements

6. Deliverables

  • Security Assessment Report (SAR)
  • Penetration test report
  • Vulnerability scan results
  • Evidence artifacts

SAP Timeline

  • Developed by 3PAO in collaboration with CSP
  • Finalized 2-4 weeks before assessment
  • State review and approval required

Security Assessment Report (SAR)

Purpose

Documents 3PAO findings from the security assessment.

Required Sections

1. Executive Summary

  • Overall assessment results
  • Key findings and risks
  • Recommendation for authorization

2. Assessment Results by Control

  • For each control:
    • Assessment objective
    • Assessment method (Examine/Interview/Test)
    • Findings (Pass/Fail/Other)
    • Weakness description if not satisfied
    • Risk rating (Low/Moderate/High)

3. Risk Exposure

  • Summary of deficiencies
  • Risk level distribution
  • Compensating controls
  • Recommendations

4. Penetration Test Results

  • Methodology
  • Findings
  • Remediation recommendations

5. Vulnerability Scan Results

  • Scan methodology
  • Identified vulnerabilities (CVSS scores)
  • False positive analysis
  • Remediation status

6. Attachments

  • Detailed test evidence
  • Interview records
  • Examination artifacts
  • Technical screenshots

SAR Findings Classifications

Satisfied (Pass):

  • Control fully implemented
  • No deficiencies identified
  • Evidence supports implementation

Other Than Satisfied (Fail):

  • Control not implemented or insufficient
  • Becomes POA&M item
  • Risk rating assigned

Not Applicable (N/A):

  • Control not relevant to system
  • Justification required

Risk Ratings

Low Risk:

  • Minor impact if exploited
  • Unlikely to cause serious harm
  • May be acceptable with POA&M

Moderate Risk:

  • Could cause serious adverse effects
  • Requires POA&M with short timeline
  • Compensating controls may be needed

High Risk:

  • Severe impact if exploited
  • May block authorization
  • Immediate remediation required

Plan of Action & Milestones (POA&M)

Purpose

Documents known deficiencies and remediation plan.

Required Information Per Item

1. Weakness Identification

  • Control number (e.g., AC-2)
  • Weakness description
  • Risk rating (Low/Moderate/High)
  • Source (SAR finding, vulnerability scan, etc.)

2. Remediation Plan

  • Specific corrective actions
  • Resources required
  • Responsible party
  • Milestone dates
  • Completion criteria

3. Current Status

  • Ongoing/Completed
  • Percent complete
  • Status updates

4. Deviation/Compensating Controls

  • If control cannot be fully implemented
  • Justification for deviation
  • Compensating controls description
  • Residual risk acceptance

POA&M Requirements

Timeline Constraints:

  • High Risk: 30 days max
  • Moderate Risk: 90 days max
  • Low Risk: 180 days max

State Approval Required:

  • Authorizing official must accept POA&M items
  • Excessive POA&Ms may delay authorization
  • High-risk items may block ATO

Monthly Reporting:

  • POA&M status updates required
  • Milestone slippage requires justification
  • Completed items closed with evidence

POA&M Best Practices

Be Realistic:

  • Don't commit to impossible timelines
  • Account for procurement, testing, validation
  • Include buffer for unexpected issues

Be Specific:

  • ❌ "Implement MFA"
  • ✅ "Deploy Duo Security MFA for all admin accounts, pilot by 1/15, full rollout by 2/1, validation testing by 2/15"

Limit POA&M Count:

  • Too many POA&Ms = poor readiness
  • Aim for <20 items for clean authorization
  • Remediate before assessment when possible

Supporting Documents

Privacy Impact Assessment (PIA)

Required if: System processes PII Sections:

  • System and data description
  • Data collection and usage
  • Data sharing and disclosure
  • Data retention and disposal
  • Privacy controls implementation
  • Privacy risk assessment

Contingency Plan (CP)

Required: All systems Sections:

  • Backup and recovery procedures
  • Emergency response procedures
  • Recovery procedures
  • Reconstitution procedures
  • Testing and training schedules

Incident Response Plan (IRP)

Required: All systems Sections:

  • Incident detection and reporting
  • Response procedures by incident type
  • Roles and responsibilities
  • Communication and escalation
  • Post-incident review process

Documentation Timeline

Typical Development Schedule:

  1. SSP Development: 2-4 months

    • Initial draft
    • Technical review
    • State review and feedback
    • Finalization
  2. SAP Development: 2-4 weeks

    • 3PAO creates plan
    • CSP review and input
    • State approval
  3. Assessment Execution: 4-8 weeks

    • Vulnerability scanning
    • Penetration testing
    • Control validation
    • Evidence collection
  4. SAR Development: 2-4 weeks

    • 3PAO analyzes findings
    • Report drafting
    • CSP review
    • Finalization
  5. POA&M Development: 1-2 weeks

    • Identify deficiencies
    • Create remediation plans
    • CSP and state negotiation
    • Approval

StateRAMP Document Templates

Available Resources:

  • StateRAMP website provides templates
  • Based on FedRAMP templates
  • State-specific templates may exist
  • 3PAO often provides templates

Template Usage:

  • Use as starting point, not copy/paste
  • Customize to actual system
  • Remove non-applicable sections
  • Add detail and evidence

Document Maintenance

Continuous Monitoring Phase:

  • SSP updates for significant changes
  • Monthly POA&M updates
  • Annual SAR (annual assessment)
  • Continuous scanning reports

Significant Changes:

  • New connections or services
  • Major architecture changes
  • New data types
  • Changed risk profile

Notification Required:

  • Within 30 days of significant change
  • May require supplemental assessment
  • Could trigger re-authorization

Quality Checklist

Before submitting ATO package:

SSP:

  • All controls addressed (no TBDs)
  • Diagrams accurate and current
  • Inheritance clearly documented
  • Evidence references included
  • Technical details specific
  • Page numbers and table of contents

SAP:

  • Aligned with SSP scope
  • Testing methodology clear
  • Schedule realistic
  • State approved

SAR:

  • All controls assessed
  • Findings clearly documented
  • Risk ratings justified
  • Evidence attached
  • 3PAO signed

POA&M:

  • All deficiencies included
  • Timelines realistic and compliant
  • Resources identified
  • Milestones specific
  • Risk ratings match SAR

Examples

# General documentation guidance
/stateramp:documentation all

# SSP-specific guidance for Moderate
/stateramp:documentation ssp moderate

# POA&M guidance
/stateramp:documentation poam

# SAR review checklist
/stateramp:documentation sar low

Next Steps

After documentation:

  1. Engage 3PAO for SAP/SAR development
  2. Use /stateramp:assess to validate readiness
  3. Use /stateramp:state-specific for state requirements
  4. Engage stateramp-expert skill for control-by-control guidance

StateRAMP Evidence Checklist

Generates comprehensive evidence collection checklists for StateRAMP (State Risk and Authorization Management Program) authorization with state-level compliance requirements.

Never commit evidence artifacts to source control. The outputs below include real usernames, credential reports, MFA device states, and privileged-account inventories. .gitignore covers evidence/ by default so git add -A will not sweep it up, but durable storage is your responsibility. Use an encrypted, access-controlled evidence locker (encrypted S3 with least-privilege IAM, a GRC platform, or a shared drive with full-disk encryption and MFA-gated access).

Usage

/stateramp:evidence-checklist <control-family> [--baseline <moderate|high>] [--export <format>]

Arguments

  • <control-family>: NIST 800-53 control family (e.g., "AC", "AU", "SC") or specific control (e.g., "AC-2", "AU-2")
  • --baseline: StateRAMP baseline (moderate or high). Default: moderate
  • --export: Export format (json, csv, markdown). Default: markdown

Example: Access Control Evidence (Moderate Baseline)

/stateramp:evidence-checklist AC-2 --baseline moderate

Output:

StateRAMP Evidence Checklist
Control: AC-2 - Account Management
Baseline: StateRAMP Moderate (based on FedRAMP Moderate + state-specific requirements)
Assessment Type: Third-Party Assessment Organization (3PAO)
Authorization Validity: 3 years
ConMon Frequency: Continuous (monthly reporting)

## Control Requirements

AC-2 Account Management - The organization manages information system accounts, including establishing, activating, modifying, reviewing, disabling, and removing accounts.

### StateRAMP-Specific Requirements

In addition to standard FedRAMP requirements, StateRAMP requires:
- **State data residency**: Data must remain within US borders (some states require in-state residency)
- **State-specific incident reporting**: 24-hour notification to state CISO
- **Enhanced background checks**: Personnel with access to state data require background checks
- **State audit rights**: State agencies retain audit/inspection rights
- **Data return/destruction**: Specific procedures for state data return upon contract termination

## Evidence Requirements

### Required Documentation

□ **System Security Plan (SSP) Section 13.2 - AC-2**
  - Complete AC-2 implementation description
  - Account types supported (user, privileged, service, temporary, emergency)
  - Account establishment procedures
  - Account modification procedures
  - Account disabling/removal procedures (within 24 hours for terminations)
  - Account review procedures (at least quarterly)
  - State-specific requirements addressed:
    - Background check requirements for personnel
    - State data residency commitments
    - State incident notification procedures
  - Evidence: SSP Section 13.2 (AC-2)
  - Frequency: Annual update, or when implementation changes

□ **Account Management Policy**
  - Formal policy governing account lifecycle
  - Required elements:
    - Account approval process (includes state agency approval if applicable)
    - Least privilege enforcement
    - Quarterly access reviews
    - Automated account lifecycle where feasible
    - Emergency account procedures
  - Evidence: Account Management Policy v1.x (approved by Authorizing Official)
  - Frequency: Annual review

□ **Background Check Procedures**
  - Procedures for background checks on personnel with state data access
  - Required elements:
    - Types of background checks required (federal, state, financial)
    - Frequency (initial hire, every 5 years)
    - Documentation retention (per state requirements)
    - Handling of adverse findings
  - Evidence: Background Check Procedure document
  - Frequency: Annual review
  - **StateRAMP-Specific**: Required for state government cloud services

□ **Data Residency Attestation**
  - Written attestation that state data remains in US (or in-state if required)
  - Infrastructure architecture showing data storage locations
  - Evidence: Data residency attestation + architecture diagrams
  - Frequency: Annual attestation
  - **StateRAMP-Specific**: Critical for state government compliance

### Automated Evidence Collection

✓ **Account Inventory**
```bash
# AWS IAM users (cloud service provider perspective)
aws iam list-users --output json > evidence/stateramp-ac2-iam-users-$(date +%Y%m%d).json

# IAM credential report
aws iam generate-credential-report
aws iam get-credential-report --output text | base64 -d \
  > evidence/stateramp-ac2-credential-report-$(date +%Y%m%d).csv

# Filter for state government users (by tags or OU)
aws organizations list-accounts-for-parent --parent-id <STATE-OU-ID> \
  --output json > evidence/stateramp-ac2-state-accounts-$(date +%Y%m%d).json

# Azure AD users (if using Azure Government)
az ad user list --output json > evidence/stateramp-ac2-azure-users-$(date +%Y%m%d).json

# GCP users (if using GCP)
gcloud identity groups memberships list --group-email=state-users@agency.gov \
  --format=json > evidence/stateramp-ac2-gcp-users-$(date +%Y%m%d).json

Collection Frequency: Monthly (for ConMon reporting) Retention: 7 years (state record retention requirements) Purpose: Account inventory per AC-2(1)

✓ Account Creation/Modification/Deletion Logs

# AWS CloudTrail - Account lifecycle events (last 30 days)
aws cloudtrail lookup-events \
  --lookup-attributes AttributeKey=EventName,AttributeValue=CreateUser \
  --start-time $(date -u -d '30 days ago' +%Y-%m-%dT%H:%M:%S) \
  --max-items 1000 \
  --output json > evidence/stateramp-ac2-user-creation-$(date +%Y%m).json

aws cloudtrail lookup-events \
  --lookup-attributes AttributeKey=EventName,AttributeValue=DeleteUser \
  --start-time $(date -u -d '30 days ago' +%Y-%m-%dT%H:%M:%S) \
  --max-items 1000 \
  --output json > evidence/stateramp-ac2-user-deletion-$(date +%Y%m).json

for event in AttachUserPolicy DetachUserPolicy PutUserPolicy DeleteUserPolicy; do
  aws cloudtrail lookup-events \
    --lookup-attributes AttributeKey=EventName,AttributeValue=$event \
    --start-time $(date -u -d '30 days ago' +%Y-%m-%dT%H:%M:%S) \
    --max-items 1000 \
    --output json >> evidence/stateramp-ac2-policy-changes-$(date +%Y%m).json
done

# Azure AD audit logs
az monitor activity-log list \
  --caller 'Microsoft.Authorization' \
  --start-time $(date -u -d '30 days ago' +%Y-%m-%dT%H:%M:%S) \
  --output json > evidence/stateramp-ac2-azure-audit-$(date +%Y%m).json

Collection Frequency: Monthly Retention: 7 years Purpose: Account lifecycle audit trail per AC-2(4)

✓ Privileged Account Inventory

# AWS - Users with AdministratorAccess
for user in $(aws iam list-users --query 'Users[].UserName' --output text); do
  policies=$(aws iam list-attached-user-policies --user-name "$user" --query 'AttachedPolicies[?PolicyName==`AdministratorAccess`]')
  if [ "$policies" != "[]" ]; then
    echo "$user,AdministratorAccess,$(date +%Y-%m-%d)" >> evidence/stateramp-ac2-privileged-users-$(date +%Y%m%d).csv
  fi
done

# IAM roles with admin privileges
aws iam list-roles | jq -r '.Roles[].RoleName' | while read role; do
  policies=$(aws iam list-attached-role-policies --role-name "$role" --query 'AttachedPolicies[?PolicyName==`AdministratorAccess`]')
  if [ "$policies" != "[]" ]; then
    echo "$role,AdministratorAccess,$(date +%Y-%m-%d)" >> evidence/stateramp-ac2-privileged-roles-$(date +%Y%m%d).csv
  fi
done

Collection Frequency: Weekly Retention: 7 years Purpose: Privileged account monitoring per AC-2(7)

✓ Automated Account Disabling Evidence

# Check for inactive accounts (no access in 90 days)
aws iam get-credential-report --output text | base64 -d | \
  awk -F',' '$4 == "true" {
    split($5,a,"T");
    if ((systime() - mktime(gensub(/[-:]/," ","g",a[1]" "substr(a[2],1,8)))) > 90*86400)
      print $1","$5",INACTIVE_90_DAYS"
  }' > evidence/stateramp-ac2-inactive-accounts-$(date +%Y%m%d).csv

# Check for unused IAM access keys (>90 days)
aws iam get-credential-report --output text | base64 -d | \
  awk -F',' '$10 == "true" && $12 == "N/A" {print $1",access_key_1,NEVER_USED"}' \
  >> evidence/stateramp-ac2-unused-keys-$(date +%Y%m%d).csv

Collection Frequency: Weekly Retention: 7 years Purpose: Inactive account detection per AC-2(3)

✓ Data Residency Evidence

# AWS - Verify all resources in US regions only
aws ec2 describe-regions --all-regions --output json | \
  jq '.Regions[] | select(.RegionName | startswith("us-"))' \
  > evidence/stateramp-ac2-us-regions-$(date +%Y%m%d).json

# S3 buckets location verification
aws s3api list-buckets --output json | jq -r '.Buckets[].Name' | while read bucket; do
  location=$(aws s3api get-bucket-location --bucket "$bucket" --output text)
  echo "$bucket,$location" >> evidence/stateramp-ac2-s3-locations-$(date +%Y%m%d).csv
done

# Filter for non-US buckets (should be none for state data)
cat evidence/stateramp-ac2-s3-locations-$(date +%Y%m%d).csv | \
  grep -v "us-" | grep -v "None" > evidence/stateramp-ac2-non-us-buckets-$(date +%Y%m%d).csv

# RDS instances location verification
aws rds describe-db-instances \
  --query 'DBInstances[].[DBInstanceIdentifier,AvailabilityZone]' \
  --output json > evidence/stateramp-ac2-rds-locations-$(date +%Y%m%d).json

Collection Frequency: Monthly Retention: 7 years Purpose: StateRAMP-Specific - Data residency requirement

Manual Evidence Collection

□ Quarterly Access Reviews

  • Review all accounts with access to state government data
  • Required elements:
    • Complete account list at review start date
    • Manager certification of continued need
    • State agency POC sign-off (if applicable)
    • Identified inappropriate access
    • Remediation within 30 days
    • Authorizing Official sign-off
  • Evidence: Quarterly access review reports (Q1-Q4)
  • Frequency: Quarterly (every 90 days)
  • StateRAMP: Required for ConMon reporting

□ Background Check Records

  • Background check records for all personnel with state data access
  • Required elements:
    • Name, date of background check
    • Type of check (federal, state, financial)
    • Result (pass/fail)
    • Next renewal date (every 5 years)
  • Evidence: Background check register (sanitized - no detailed results)
  • Frequency: Initial hire, every 5 years
  • StateRAMP-Specific: Required for state government contracts

□ State Agency Account Approvals

  • Approval from state agency POC before granting access to state data
  • Required elements:
    • Account request (name, role, need)
    • State agency POC approval (email/ticket)
    • Cloud service provider approval
    • Access granted date
  • Evidence: Sample of 25 account approvals from last quarter
  • Frequency: Quarterly review

□ Emergency Account Usage Logs

  • Log of all emergency/break-glass account usage
  • Required elements:
    • Date/time of emergency access
    • Justification for emergency access
    • Actions taken during emergency access
    • Post-incident review
    • State agency notification (within 24 hours)
  • Evidence: Emergency access log + state notifications
  • Frequency: Ongoing (log all usage)
  • StateRAMP: State must be notified of emergency access within 24 hours

□ Data Return/Destruction Evidence

  • Procedures and evidence for returning/destroying state data upon contract termination
  • Required elements:
    • Data return procedure
    • Secure deletion procedure (NIST 800-88)
    • Certificate of destruction
    • State agency acknowledgment
  • Evidence: Data return/destruction procedure + certificates (if applicable)
  • Frequency: Upon contract termination
  • StateRAMP-Specific: State-specific data handling requirements

StateRAMP Assessment Expectations

StateRAMP 3PAOs will verify:

Documentation Review

✓ SSP Section 13.2 (AC-2) complete and accurate ✓ Account management policy comprehensive ✓ Background check procedures documented ✓ Data residency attestation provided ✓ State-specific requirements addressed

Implementation Review

✓ Account lifecycle automated (provisioning, deprovisioning) ✓ Quarterly access reviews performed (4 consecutive quarters minimum) ✓ Privileged access limited and monitored ✓ Inactive accounts disabled (>90 days) ✓ State data resides only in US regions (or in-state if required) ✓ Background checks current for all personnel with state data access

Testing Requirements

✓ Sample 25 account creations (test approval process) ✓ Sample 25 account deletions (test <24hr removal) ✓ Review 4 quarterly access review reports ✓ Verify data residency (all resources in US) ✓ Test emergency account procedures

Continuous Monitoring (ConMon)

✓ Monthly POA&M updates ✓ Monthly vulnerability scan reports ✓ Quarterly access review reports ✓ Incident reports within 24 hours to state ✓ Annual assessment (or more frequent per state requirement)

Common StateRAMP Assessment Findings

Critical (Likely to delay ATO)

❌ No SSP or incomplete SSP ❌ State data found outside US regions ❌ No background checks for personnel with state data access ❌ No quarterly access reviews ❌ Inactive accounts not disabled (>90 days) ❌ No state incident notification procedures

Moderate (Corrective Action Plan required)

⚠️ Access reviews performed but missing state agency sign-off ⚠️ Background checks >5 years old ⚠️ Account approvals missing state agency POC approval ⚠️ Data residency attestation not current (>1 year old) ⚠️ ConMon reporting incomplete or late

Minor (Observations)

⚠️ SSP could be more detailed ⚠️ Emergency account procedures not tested ⚠️ Some documentation >12 months old

Remediation Guidance

If State Data Outside US Regions

  1. Immediate: Identify all resources with state data outside US
  2. Week 1: Plan migration to US regions
  3. Weeks 2-4: Migrate data to US regions (backup first)
  4. Week 5: Verify no state data remains outside US
  5. Week 6: Provide updated data residency attestation

Timeline: 4-6 weeks Priority: 🔴 CRITICAL (mandatory for StateRAMP)

If No Background Checks

  1. Week 1: Identify all personnel with state data access
  2. Week 2: Engage background check vendor
  3. Weeks 3-8: Complete background checks for all personnel
  4. Week 9: Document results, create background check register
  5. Ongoing: Background checks for new hires, renewals every 5 years

Timeline: 8-10 weeks Priority: 🔴 CRITICAL (StateRAMP requirement)

If No Quarterly Access Reviews

  1. Week 1: Export all accounts with state data access
  2. Week 2: Send to managers and state agency POCs for review
  3. Week 3: Collect sign-offs, identify inappropriate access
  4. Week 4: Remediate access issues
  5. Ongoing: Schedule quarterly (every 90 days)

Timeline: Establish immediately, need 4 consecutive quarters for ATO Priority: 🔴 CRITICAL (required for ATO and ConMon)

Cross-References

Related StateRAMP Controls

  • AC-1 - Access Control Policy and Procedures
  • AC-3 - Access Enforcement
  • AC-6 - Least Privilege
  • IA-2 - Identification and Authentication (multi-factor)
  • AU-2 - Audit Events (account management events)

StateRAMP vs FedRAMP Differences

  • Data Residency: StateRAMP requires US (sometimes in-state), FedRAMP allows any approved region
  • Background Checks: StateRAMP requires state-specific checks, FedRAMP requires federal
  • Incident Notification: StateRAMP 24 hours to state, FedRAMP varies
  • ConMon Frequency: StateRAMP monthly, FedRAMP monthly (High), quarterly (Moderate/Low)
  • Authorization Validity: StateRAMP 3 years, FedRAMP 3 years
  • State Audit Rights: StateRAMP includes state inspection rights, FedRAMP federal only

Maps to Other Frameworks

  • NIST 800-53 Rev 5: AC-2 (same control)
  • FedRAMP: AC-2 (with state-specific additions)
  • ISO 27001:2022: A.5.15, A.5.16, A.5.18 (Access control)
  • SOC 2: CC6.1, CC6.2 (Access controls)

Cost Estimates

StateRAMP Authorization (Moderate Baseline)

  • Readiness assessment: 120 hours ($12,000)
  • SSP development: 200 hours ($20,000)
  • Control implementation: 400 hours ($40,000)
  • Background checks: $100-500 per person
  • Data residency migration (if needed): 80-200 hours ($8k-$20k)
  • 3PAO assessment: $60k-$120k (depends on system complexity)
  • Total Year 1: ~$140k-$192k (one-time) + ongoing ConMon

StateRAMP Continuous Monitoring (ConMon)

  • Monthly POA&M updates: 8 hours/month ($800/month = $9,600/year)
  • Monthly vulnerability scans: $5k-$10k/year
  • Quarterly access reviews: 16 hours/quarter ($1,600/quarter = $6,400/year)
  • Annual assessment: $40k-$80k/year
  • Ongoing: ~$61k-$106k/year

Tools

  • GRC platform with StateRAMP templates: $20k-$50k/year
  • Vulnerability scanning: $5k-$15k/year
  • Background check service: $100-500/person (initial + renewals)

Evidence Package Structure

evidence/
└── stateramp-ac2-account-management/
    ├── ssp/
    │   ├── ssp-section-13.2-ac2-v1.2.docx
    │   └── ssp-annual-review-2024.pdf
    ├── policies/
    │   ├── account-management-policy-v1.1-signed.pdf
    │   ├── background-check-procedure.pdf
    │   └── data-residency-attestation-2024.pdf
    ├── automated/
    │   ├── 2024-01/
    │   │   ├── iam-users-20240131.json
    │   │   ├── credential-report-20240131.csv
    │   │   ├── account-lifecycle-202401.json
    │   │   ├── data-residency-20240131.json
    │   │   └── inactive-accounts-20240131.csv
    │   └── ... (monthly for ConMon)
    ├── quarterly-reviews/
    │   ├── Q1-2024-access-review.pdf
    │   ├── Q1-2024-state-agency-signoff.pdf
    │   ├── Q2-2024-access-review.pdf
    │   ├── Q2-2024-state-agency-signoff.pdf
    │   ├── Q3-2024-access-review.pdf
    │   ├── Q3-2024-state-agency-signoff.pdf
    │   ├── Q4-2024-access-review.pdf
    │   └── Q4-2024-state-agency-signoff.pdf
    ├── background-checks/
    │   ├── background-check-register-2024.xlsx (sanitized)
    │   └── background-check-policy-approval.pdf
    ├── state-approvals/
    │   ├── state-agency-account-approvals-Q1-2024/
    │   │   ├── approval-001.pdf
    │   │   └── ... (25 samples)
    │   └── ... (quarterly)
    ├── emergency-access/
    │   ├── emergency-access-log-2024.xlsx
    │   ├── emergency-access-001-state-notification.pdf
    │   └── ... (all emergency access instances)
    ├── conmon-reports/
    │   ├── 2024-01-conmon-report.pdf
    │   ├── 2024-02-conmon-report.pdf
    │   └── ... (monthly)
    └── README.md (evidence index, 7-year retention)

Automation Script

#!/usr/bin/env python3
"""
StateRAMP AC-2 Account Management Evidence Collection
For cloud service providers seeking StateRAMP authorization
"""
import boto3
import json
import csv
from datetime import datetime, timedelta
import os

class StateRAMPAccountManagement:
    def __init__(self, output_dir="evidence/stateramp-ac2-account-management"):
        self.output_dir = f"{output_dir}/automated/{datetime.now().strftime('%Y-%m')}"
        self.timestamp = datetime.now().strftime("%Y%m%d")
        os.makedirs(self.output_dir, exist_ok=True)

    def collect_account_inventory(self):
        """Collect complete account inventory"""
        print("Collecting account inventory...")
        iam = boto3.client('iam')

        users = iam.list_users()['Users']

        # Save inventory
        with open(f"{self.output_dir}/iam-users-{self.timestamp}.json", 'w') as f:
            json.dump(users, f, indent=2, default=str)

        # Generate credential report
        iam.generate_credential_report()
        report = iam.get_credential_report()

        with open(f"{self.output_dir}/credential-report-{self.timestamp}.csv", 'wb') as f:
            f.write(report['Content'])

        print(f"✓ Total IAM users: {len(users)}")

        return users

    def verify_data_residency(self):
        """Verify all resources are in US regions (StateRAMP requirement)"""
        print("Verifying data residency (US regions only)...")
        ec2 = boto3.client('ec2')
        s3 = boto3.client('s3')

        # Get all enabled regions
        regions = ec2.describe_regions()['Regions']

        # Check for non-US regions with resources
        non_us_resources = []

        for region in regions:
            region_name = region['RegionName']
            if not region_name.startswith('us-'):
                # Check if region has any resources
                ec2_regional = boto3.client('ec2', region_name=region_name)
                try:
                    instances = ec2_regional.describe_instances()
                    if len(instances['Reservations']) > 0:
                        non_us_resources.append({
                            'region': region_name,
                            'resource_type': 'EC2',
                            'count': len(instances['Reservations'])
                        })
                except:
                    pass  # Region might not be enabled

        # Check S3 bucket locations
        buckets = s3.list_buckets()['Buckets']
        for bucket in buckets:
            bucket_name = bucket['Name']
            try:
                location = s3.get_bucket_location(Bucket=bucket_name)
                bucket_region = location['LocationConstraint'] or 'us-east-1'

                if not bucket_region.startswith('us-'):
                    non_us_resources.append({
                        'region': bucket_region,
                        'resource_type': 'S3',
                        'bucket': bucket_name
                    })
            except:
                pass

        # Save results
        with open(f"{self.output_dir}/data-residency-{self.timestamp}.json", 'w') as f:
            json.dump({
                'compliant': len(non_us_resources) == 0,
                'non_us_resources': non_us_resources,
                'timestamp': datetime.now().isoformat()
            }, f, indent=2)

        if len(non_us_resources) > 0:
            print(f"✗ CRITICAL: Found {len(non_us_resources)} resources outside US regions")
            print(f"  StateRAMP requires all state data in US regions")
            for resource in non_us_resources:
                print(f"  - {resource}")
        else:
            print(f"✓ Data residency compliant (all resources in US regions)")

        return non_us_resources

    def check_inactive_accounts(self):
        """Check for inactive accounts (>90 days)"""
        print("Checking for inactive accounts...")
        iam = boto3.client('iam')

        # Get credential report
        iam.generate_credential_report()
        report = iam.get_credential_report()

        # Parse for inactive accounts
        inactive_accounts = []
        for line in csv.DictReader(report['Content'].decode('utf-8').splitlines()):
            if line.get('password_enabled') == 'true':
                password_last_used = line.get('password_last_used')

                if password_last_used and password_last_used != 'N/A':
                    try:
                        last_used = datetime.fromisoformat(password_last_used.replace('Z', '+00:00'))
                        days_inactive = (datetime.now(last_used.tzinfo) - last_used).days

                        if days_inactive > 90:
                            inactive_accounts.append({
                                'user': line['user'],
                                'password_last_used': password_last_used,
                                'days_inactive': days_inactive
                            })
                    except:
                        pass  # Skip parsing errors

        # Save results
        with open(f"{self.output_dir}/inactive-accounts-{self.timestamp}.json", 'w') as f:
            json.dump(inactive_accounts, f, indent=2)

        if len(inactive_accounts) > 0:
            print(f"⚠️  WARNING: {len(inactive_accounts)} accounts inactive >90 days (AC-2(3) requirement)")
        else:
            print(f"✓ No inactive accounts found")

        return inactive_accounts

    def generate_conmon_report(self, users, non_us_resources, inactive_accounts):
        """Generate monthly ConMon report"""
        report = f"""
StateRAMP Continuous Monitoring (ConMon) Report
Month: {datetime.now().strftime('%B %Y')}
Generated: {datetime.now().strftime('%Y-%m-%d %H:%M:%S')}

AC-2 ACCOUNT MANAGEMENT STATUS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Total Accounts:         {len(users)}
Inactive Accounts (>90d): {len(inactive_accounts)} {'✓' if len(inactive_accounts) == 0 else '⚠️  ACTION REQUIRED'}

DATA RESIDENCY (StateRAMP Requirement)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Compliance Status:      {'✓ COMPLIANT - All resources in US regions' if len(non_us_resources) == 0 else f'✗ NON-COMPLIANT - {len(non_us_resources)} resources outside US'}

REQUIRED ACTIONS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
"""
        if len(inactive_accounts) > 0:
            report += f"□ Disable {len(inactive_accounts)} inactive accounts (within 30 days)\n"
        if len(non_us_resources) > 0:
            report += f"□ Migrate {len(non_us_resources)} resources to US regions (IMMEDIATE)\n"

        report += f"""
MONTHLY DELIVERABLES
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✓ Account inventory collected
✓ Data residency verified
✓ Inactive accounts identified
□ POA&M updated (due by 5th of month)
□ Vulnerability scan results (due by 10th of month)
□ Submit to state agency POC

Evidence Location: {self.output_dir}
Retention: 7 years (state requirements)
"""

        report_file = f"{self.output_dir}/../conmon-reports/conmon-report-{datetime.now().strftime('%Y-%m')}.txt"
        os.makedirs(os.path.dirname(report_file), exist_ok=True)

        with open(report_file, 'w') as f:
            f.write(report)

        print(f"\n{report}")
        print(f"ConMon report: {report_file}")

        return report_file

if __name__ == "__main__":
    print("StateRAMP AC-2 Account Management Evidence Collection")
    print("=" * 70)
    print("Baseline: Moderate")
    print("ConMon: Monthly reporting required")
    print("=" * 70)

    collector = StateRAMPAccountManagement()

    users = collector.collect_account_inventory()
    non_us_resources = collector.verify_data_residency()
    inactive_accounts = collector.check_inactive_accounts()

    collector.generate_conmon_report(users, non_us_resources, inactive_accounts)

    print("\n✓ StateRAMP evidence collection complete")
    print("⚠️  REMINDER: Submit ConMon report to state agency by 5th of month")

StateRAMP Program: State-level FedRAMP equivalent Baseline: Moderate (most common) or High Assessment: Third-Party Assessment Organization (3PAO) Authorization Validity: 3 years ConMon: Monthly reporting required Evidence Retention: 7 years (state record retention) Priority: 🔴 CRITICAL (US state government cloud services)

Key StateRAMP Differences:

  • Data residency requirements (US or in-state)
  • State-specific background checks
  • 24-hour incident notification to state
  • State audit/inspection rights
  • Enhanced data return/destruction procedures

StateRAMP Impact Level Selection

Helps determine the appropriate StateRAMP impact level based on system characteristics and data sensitivity.

Arguments

  • $1 - System type (optional: description of system/service)

Impact Level Decision Framework

StateRAMP uses FIPS 199 categorization based on three security objectives:

Security Objectives

  1. Confidentiality: Unauthorized disclosure impact
  2. Integrity: Unauthorized modification impact
  3. Availability: System disruption impact

Impact Ratings

  • Low: Limited adverse effect
  • Moderate: Serious adverse effect
  • High: Severe or catastrophic adverse effect

Overall Impact Level = Highest impact across any objective (Confidentiality, Integrity, or Availability)

StateRAMP Low Impact

When to Choose Low

  • Public information only (no CUI or PII)
  • Limited adverse effect if compromised
  • Non-critical government operations
  • Disruption has minimal impact

Example Systems

  • Public-facing websites (informational)
  • Event calendars and scheduling
  • Public comment systems
  • General constituent communication
  • Non-sensitive document management
  • Public records (already disclosed)

Data Types (Low)

  • Public information
  • Published government data
  • General announcements
  • Non-sensitive forms

Control Requirements

  • ~125 NIST 800-53 controls
  • Lighter compliance burden
  • Simpler continuous monitoring

StateRAMP Moderate Impact

When to Choose Moderate

  • Controlled Unclassified Information (CUI)
  • Personally Identifiable Information (PII)
  • Protected Health Information (PHI)
  • Financial data
  • Law enforcement sensitive data
  • Serious adverse effect if compromised

Example Systems

  • Tax collection and processing
  • Benefits administration (SNAP, Medicaid, etc.)
  • Human resources and payroll
  • Law enforcement case management
  • Licensing and permitting (with PII)
  • Financial management systems
  • Healthcare portals
  • Constituent relationship management (CRM) with PII
  • Vital records systems
  • Grant management with sensitive data

Data Types (Moderate)

  • Social Security Numbers
  • Driver's license numbers
  • Financial account information
  • Health records
  • Criminal justice information
  • Protected tax information
  • Benefit recipient data
  • Employee records

Control Requirements

  • ~325 NIST 800-53 controls
  • More rigorous assessment
  • Enhanced continuous monitoring
  • Stronger security controls

Decision Tree

Does system process/store any of:
├─ PII (SSN, DL#, financial)?          → MODERATE
├─ PHI or health information?           → MODERATE
├─ Financial data (tax, benefits)?      → MODERATE
├─ Law enforcement sensitive?           → MODERATE
├─ CUI designated information?          → MODERATE
└─ Only public information?             → LOW
   └─ Is availability critical?
      ├─ Yes, severe impact if down    → MODERATE
      └─ No, limited impact            → LOW

FIPS 199 Impact Examples

Confidentiality Impact

Low: Public relations system

  • Information is already public
  • Disclosure has no privacy implications

Moderate: Benefits administration

  • Contains PII and financial data
  • Unauthorized disclosure violates privacy
  • Could enable identity theft or fraud

Integrity Impact

Low: Public information website

  • Defacement is embarrassing but correctable
  • No safety or financial consequences

Moderate: Licensing database

  • Incorrect licenses could enable fraud
  • Could compromise public safety
  • Financial harm to individuals/government

Availability Impact

Low: Event calendar

  • Citizens can call or visit in person
  • Alternative channels exist
  • Temporary inconvenience only

Moderate: Emergency dispatch system

  • Critical for public safety
  • Lives at risk if unavailable
  • No immediate alternative

Impact Level Comparison

FactorLowModerate
Controls~125~325
Cost$50K-$150K$150K-$400K
Timeline6-12 months12-18 months
Assessment3PAO required3PAO required
Continuous MonitoringBasicEnhanced
Annual TestingLighterMore rigorous
POA&M ScrutinyModerateStrict

Special Considerations

Data Aggregation

  • Individual data points may be low impact
  • Aggregated data may elevate to moderate
  • Example: Individual addresses (low) vs. database of all addresses (moderate)

External Interfaces

  • Connections to moderate systems may require moderate
  • API data exchange considerations
  • Integration security requirements

State-Specific Requirements

Some states may require:

  • Higher impact levels for certain data types
  • Additional controls beyond baseline
  • Specific categorization criteria

Check /stateramp:state-specific for state variations

Business Impact Analysis

Consider:

  • Mission criticality
  • Service disruption cost
  • Constituent impact
  • Regulatory consequences
  • Reputation damage

Common Mistakes

  1. Underestimating Impact:

    • "It's just names and addresses" (but SSNs = moderate)
    • Ignoring PII in metadata/logs
    • Not considering data aggregation
  2. Overestimating Impact:

    • Public data doesn't need moderate
    • Availability concerns alone may not require moderate
    • Consider actual risk, not perceived risk
  3. Ignoring Future State:

    • Plan for system evolution
    • Adding PII later requires re-authorization
    • Start with appropriate level to avoid rework

Impact Level Change

If system changes:

  • New data types added → May require higher impact
  • System connections change → Re-evaluate
  • Significant change = new authorization required
  • StateRAMP requires 30-day notification

Output

The command provides:

  1. Recommended Impact Level: Low or Moderate with justification
  2. Data Sensitivity Analysis: Breakdown of data types
  3. FIPS 199 Assessment: Confidentiality/Integrity/Availability ratings
  4. Control Count: Number of controls required
  5. Cost/Timeline Estimate: Resources needed
  6. Risk Factors: Considerations and caveats
  7. State Alignment: Consistency with state requirements

Examples

# General impact level guidance
/stateramp:impact-select

# Specific system assessment
/stateramp:impact-select "Benefits eligibility and enrollment system with SSN, income data, and healthcare information"

# Compare system types
/stateramp:impact-select "Public permit search vs. permit application with PII"

Next Steps

After selecting impact level:

  1. Use /stateramp:assess <level> for readiness assessment
  2. Review /stateramp:documentation for required packages
  3. Engage stateramp-expert skill for control implementation guidance

StateRAMP State-Specific Requirements

Provides guidance on state-by-state variations, additional requirements, and acceptance criteria for StateRAMP authorizations.

Arguments

  • $1 - State code (optional: CA, TX, FL, NY, IL, etc. or "all")

StateRAMP Participating States

Current Participants (15+ states as of 2024):

  • California (CA)
  • Texas (TX)
  • Florida (FL)
  • New York (NY)
  • Illinois (IL)
  • Michigan (MI)
  • Pennsylvania (PA)
  • Ohio (OH)
  • Georgia (GA)
  • North Carolina (NC)
  • Colorado (CO)
  • Arizona (AZ)
  • Maryland (MD)
  • Massachusetts (MA)
  • Washington (WA)

Growing: New states join regularly, check StateRAMP website for current list

StateRAMP Impact Council

Purpose: Coordinate multi-state reciprocity and authorization acceptance

Functions:

  • Review and approve StateRAMP authorizations
  • Maintain baseline requirements
  • Coordinate state participation
  • Facilitate reciprocity agreements

Reciprocity Model:

  • One StateRAMP authorization accepted by multiple states
  • Individual states may add supplemental requirements
  • Reduces redundant assessments and costs

Core vs. State-Specific Requirements

Core StateRAMP Requirements (All States)

Universal Across States:

  • NIST 800-53 control baselines (Low/Moderate)
  • Third-party assessment (3PAO)
  • Continuous monitoring
  • Required documentation (SSP, SAP, SAR, POA&M)
  • Annual assessments
  • Significant change notifications (30 days)

State-Specific Variations

Common Areas of Variation:

  1. Additional Controls: Some states require controls beyond baseline
  2. Data Residency: Where data can be stored/processed
  3. Privacy Requirements: State privacy laws
  4. Breach Notification: State-specific timelines
  5. Records Retention: State records laws
  6. Legal/Regulatory: State-specific compliance
  7. Acceptance Process: Review and approval procedures

State-by-State Details

California (CA)

Additional Requirements:

  • CCPA Compliance: California Consumer Privacy Act
  • Data Residency: May require data stored in US
  • Privacy Controls: Enhanced privacy protections
  • Breach Notification: 72 hours to Attorney General if >500 residents

Participating Agencies:

  • California Department of Technology (CDT)
  • Various state departments

Key Contacts:

  • CDT StateRAMP Program Office

Notes:

  • Large state market
  • Strong privacy requirements
  • May require CCPA addendum to contracts

Texas (TX)

Additional Requirements:

  • Data Residency: Strong preference for Texas or US data centers
  • DIR Compliance: Department of Information Resources standards
  • Privacy: Texas Privacy Protection Act considerations
  • Breach Notification: "Without unreasonable delay"

Participating Agencies:

  • Texas Department of Information Resources (DIR)
  • Multiple state agencies and higher education

Key Contacts:

  • DIR Security Office

Notes:

  • Second largest state market
  • May require Texas-specific security controls
  • Strong focus on data sovereignty

Florida (FL)

Additional Requirements:

  • Public Records: Florida Sunshine Law compliance
  • Data Residency: Prefer US-based data centers
  • Breach Notification: 30 days to Department of Legal Affairs

Participating Agencies:

  • Florida Digital Service
  • Agency for State Technology (AST)

Key Contacts:

  • AST Security Office

Notes:

  • Public records law very broad
  • Must accommodate public records requests
  • Criminal justice information has special requirements

New York (NY)

Additional Requirements:

  • SHIELD Act: Stop Hacks and Improve Electronic Data Security Act
  • Data Encryption: Specific encryption requirements
  • Privacy: NY Privacy Act considerations
  • Breach Notification: "Without unreasonable delay" to Attorney General

Participating Agencies:

  • NY Office of Information Technology Services (ITS)

Key Contacts:

  • ITS Security Operations Center

Notes:

  • SHIELD Act may exceed StateRAMP baseline
  • Strong focus on data protection
  • Financial services may require NYDFS 23 NYCRR 500 as well

Illinois (IL)

Additional Requirements:

  • BIPA: Biometric Information Privacy Act (if applicable)
  • Privacy: Personal Information Protection Act
  • Breach Notification: Without unreasonable delay

Participating Agencies:

  • Department of Innovation & Technology (DoIT)

Key Contacts:

  • DoIT Security Team

Notes:

  • BIPA is nation's strictest biometric law
  • Avoid collecting biometrics if possible

Colorado (CO)

Additional Requirements:

  • CPA: Colorado Privacy Act compliance
  • Data Residency: Preference for US data centers
  • Breach Notification: 30 days to Attorney General

Participating Agencies:

  • Governor's Office of Information Technology (OIT)

Key Contacts:

  • OIT Security Office

Notes:

  • CPA similar to CCPA/GDPR
  • Consumer privacy rights must be accommodated

Other States

General Patterns:

  • Most states have breach notification laws (timelines vary)
  • Many prefer or require US-based data storage
  • State privacy laws increasingly common
  • Public records laws vary significantly
  • Some states have specific sector requirements (education, health, criminal justice)

Common State Requirements

Data Residency

Strict (Data Must Remain in State):

  • Rare, but some states for specific data types

US-Based (Data Must Remain in US):

  • Common requirement
  • Impacts choice of cloud regions
  • Backup/DR locations also restricted

No Restriction:

  • Some states allow international if adequate protections

Impact on CSPs:

  • Must document data storage locations
  • Compliance with state restrictions
  • May need state-specific deployments

Privacy and Breach Notification

State Privacy Laws:

  • CCPA (California)
  • SHIELD Act (New York)
  • CPA (Colorado)
  • VCDPA (Virginia)
  • Others emerging

Breach Notification Variations:

  • Timelines: 24 hours to 90 days
  • Thresholds: >500 residents, >1000 residents, any breach
  • Recipients: Attorney General, residents, media
  • Content requirements vary

CSP Obligations:

  • Know requirements for states served
  • Incident response plan must address state laws
  • Breach notification procedures documented
  • May require state-specific addendums

Records Management

Public Records Laws:

  • All states have some form
  • "Sunshine laws" require disclosure
  • Records retention requirements
  • E-discovery obligations

CSP Implications:

  • Must support public records requests
  • Data retention capabilities
  • Search and export functionality
  • Legal hold processes

Common Issues:

  • Automatic data deletion conflicts with retention
  • Backup tapes may contain old records
  • Multi-tenant environments complicate retrieval

State Acceptance Process

StateRAMP Path

1. Initial Authorization:

  • CSP obtains StateRAMP authorization through one state
  • Submits ATO package to StateRAMP Impact Council
  • Council reviews and approves

2. Additional State Acceptance:

  • Other states review StateRAMP authorization
  • May request supplemental information
  • May require state-specific addendums
  • Grants acceptance (not new ATO)

3. State Reciprocity:

  • Participating states agree to accept StateRAMP ATO
  • Reduces redundant assessments
  • May have conditions or limitations

State-Direct Path

Some states may:

  • Conduct own authorization outside StateRAMP
  • Require separate assessment
  • Use StateRAMP as input but not final decision
  • Have agency-specific requirements

When This Happens:

  • Specialized systems (law enforcement, health)
  • State has unique requirements
  • Pilot programs or new initiatives
  • Higher-than-moderate impact

Multi-State Strategy

Planning for Multiple States

Best Practices:

  1. Start with strictest requirements: Satisfies all states
  2. Document state-specific controls: Track variations
  3. Use "most common denominator": US data residency, strong encryption
  4. Build flexibility: Support state-specific configurations
  5. Engage early: Talk to state authorizing officials

State-Specific Deployments

When Needed:

  • Data residency requirements
  • State-unique integrations
  • Legal/regulatory isolation
  • Performance/latency optimization

Architectures:

  • Multi-region cloud (state-specific regions)
  • Data partitioning (logical separation)
  • Dedicated tenants (physical separation)

Tradeoffs:

  • Higher cost and complexity
  • Easier compliance and acceptance
  • Better performance for state users

State Contacts and Resources

Primary Resources

StateRAMP PMO:

State-Specific Contacts:

  • Each state has designated StateRAMP coordinator
  • Usually within state IT or security office
  • Check StateRAMP website for current contacts

State Authorization Officials

Who They Are:

  • Chief Information Security Officer (CISO)
  • Chief Information Officer (CIO)
  • Designated agency official
  • Risk acceptance authority

What They Do:

  • Review ATO packages
  • Accept risk and grant ATO
  • Ongoing authorization decisions
  • Significant change approvals

Emerging Trends

Increasing Participation:

  • More states joining StateRAMP
  • Reciprocity agreements expanding
  • Market adoption growing

Privacy Focus:

  • State privacy laws proliferating
  • GDPR-style requirements common
  • Consumer rights expanding

Data Sovereignty:

  • Increasing data residency requirements
  • US-based cloud preference
  • Foreign adversary restrictions (TikTok laws, etc.)

Sector-Specific:

  • Criminal justice (CJIS)
  • Education (FERPA, state laws)
  • Health (HIPAA + state)
  • Each may have unique requirements

Risk and Considerations

Expansion Risk

  • Start with one state
  • Prove model works
  • Expand to additional states
  • Don't over-commit initially

Variation Risk

  • State requirements may conflict
  • Must track and manage differences
  • Documentation burden increases
  • Testing complexity grows

Legal Risk

  • Multi-state legal compliance
  • Contract terms vary by state
  • Liability and indemnification
  • Insurance requirements

Examples

# General state variations overview
/stateramp:state-specific all

# California-specific requirements
/stateramp:state-specific CA

# Compare multiple states
/stateramp:state-specific "CA, TX, NY"

# Multi-state planning guidance
/stateramp:state-specific multi-state

Next Steps

After understanding state requirements:

  1. Use /stateramp:assess to evaluate readiness
  2. Use /stateramp:impact-select to validate impact level
  3. Use /stateramp:documentation for ATO package prep
  4. Engage stateramp-expert skill for state-specific control guidance
  5. Contact state coordinators early in process

Sponsors

Details

Marketplace
GRCEngClub/claude-grc-engineering
Source
plugins/frameworks/stateramp
Category
Community

More from GRCEngClub/claude-grc-engineering

All 70