System interview

GrantLedger

Organization
Northfield Federal Research Office (fictional agency)
Framework
NIST SP 800-53 Rev. 5.2.0 — Security and Privacy Controls for Information Systems and Organizations
Exported
2026-11-22
Answered
92 of 92 questions
This file holds
Interview only

1. System identification

QuestionAnswer
System nameGrantLedger
Organization nameNorthfield Federal Research Office (fictional agency)
System owner (name and title)Dr. Celia Mbeki, Director of Grants Management
Security officer / ISSO (name and title)Owen Strathmore, Information System Security Officer
Describe the systemGrantLedger is the grants management system of the Northfield Federal Research Office, a fictional federal agency that funds university research. About 300 agency staff use it to review proposals, award grants and track payments; about 4,000 external grantee users submit applications and reports through its public portal.

It handles grantee organization data, PII of principal investigators and financial award data. Applications arrive through the portal and an API from a government-wide grants intake service; award data is sent to the agency financial system nightly.

GrantLedger runs on AWS GovCloud in the agency's landing zone. The authorization boundary includes the portal, the case management application, the API, the PostgreSQL database and the administration tools.
What kinds of information does the system handle?Federal information (non-public); Personally identifiable information (PII); Financial information
FIPS 199 security categorization
ConfidentialityModerate
IntegrityModerate
AvailabilityModerate
Authorization to operateAuthorized (ATO in place)
Authorizing official (name and title)Raymond Akers, Chief Information Officer
Why is the SSP needed?FISMA (federal agency system)
Operational statusOperational

2. Boundary and environment

QuestionAnswer
Where is the system's information stored, processed or transmitted?Cloud IaaS / PaaS; Organization laptops / desktops
Cloud platforms in scopeAWS GovCloud
How many people use the system?More than 1000
Types of usersEmployees; Contractors; Privileged administrators; External partners / customers
Physical locations in scopeAgency headquarters in Washington, DC and two regional offices; servers in AWS GovCloud (US-West)
Do users access the system remotely?Hybrid
Describe the network and system boundaryThree-tier application in a dedicated VPC: public load balancers and a web application firewall, private application subnets and isolated database subnets. Administration is only through the agency's zero-trust access service. The VPC sits inside the agency's AWS landing zone, which provides shared logging and security services.
Connections to external systemsInbound application feed from the government-wide grants intake service (API, ISA in place). Outbound nightly award file to the agency financial system (ISA in place). Login.gov for external user sign-in.
External service providersAWS GovCloud (FedRAMP High). Login.gov for public identity. Development and operations contractor under an agency contract.

3. Identity and access

QuestionAnswer
Identity provider / directoryOkta; Agency staff use PIV through Okta; grantees use Login.gov
Multi-factor authentication coverageAll users, all access
MFA methods in useAuthenticator app; FIDO2 / hardware security key; Smart card / PIV / CAC
How is privileged (admin) access handled?Cloud and database administrators request time-limited elevated roles through the privileged access tool; sessions are recorded. Break-glass accounts are sealed and tested quarterly.
How are accounts requested, approved, reviewed and removed?Staff accounts follow the agency onboarding system with supervisor approval; grantee accounts are self-registered through Login.gov and approved by their organization's signing official. Inactive staff accounts are disabled after 60 days. Privileged accounts are reviewed monthly, others quarterly.
Remote access methodsZero-trust network access (ZTNA)
Wireless access to the systemGuest wireless only, isolated from the system
Mobile device managementMicrosoft Intune
Session lock, logout and lockout settingsStaff sessions time out after 15 minutes idle; lockout after 3 failed attempts for 15 minutes

4. Endpoints and infrastructure

QuestionAnswer
Endpoint operating systemsWindows 11; macOS
Server platformsLinux; Containers / Kubernetes
Endpoint protection / EDRMicrosoft Defender for Endpoint
Firewalls and boundary protectionAWS WAF and Shield in front of the portal; security groups and network ACLs with default-deny; egress through the landing zone's inspection firewall.
Is the system segmented from other networks?Partially (VLANs / firewall rules)
Encryption at restCloud provider encryption; Database / application-level encryption
Encryption in transitTLS 1.2 or later
Is the cryptography protecting system information FIPS-validated?Yes, everywhere it is used
Email and collaboration platformAgency Microsoft 365 GCC; not part of the system
Configuration baselines and enforcementCIS Benchmarks; DISA STIGs
How are changes to the system requested, reviewed and approved?Changes go through the agency change advisory board with a security impact analysis by the ISSO. Releases are deployed by pipeline after automated security tests.
How is the hardware and software inventory maintained?AWS Config and the agency CMDB, reconciled monthly
Patch management tool and timelinesContainer images rebuilt weekly; critical vulnerabilities fixed within 15 days, high within 30
Vulnerability scanning tool and frequencyWeekly authenticated scans; container and code scanning on every build; annual penetration test
BackupsAutomated database snapshots every 4 hours and daily cross-region backups; restore tested quarterly

5. Monitoring and response

QuestionAnswer
Log collection / SIEMSplunk
Who reviews logs and alerts, and how often?The agency SOC monitors alerts 24x7; the ISSO reviews audit reports weekly
Audit log retention period1 year online, 3 years archived, per agency policy
Time synchronization sourceAmazon Time Sync Service
Incident response capabilityDocumented plan and trained team
How and how often is incident response tested?Annual tabletop exercise with the agency SOC
How are incidents reported externally?Agency SOC within 1 hour; CISA per federal incident notification guidelines
Contingency planningContingency plan tested annually. Recovery time objective 24 hours, recovery point objective 4 hours. Warm standby in a second GovCloud region.
Who performs system maintenance?The operations contractor maintains the system through the pipeline and the privileged access tool; there is no physical maintenance (cloud).

6. Physical, media and personnel

QuestionAnswer
Physical access controlsBadge / electronic access control; Visitor log and escort; Cameras
Environmental protections for on-premises equipmentNone - cloud only; provided by AWS GovCloud data centers
Safeguards at alternate work sites (home offices)Agency telework policy: government-furnished equipment only, ZTNA, no printing of PII at home
Media protection practicesRemovable media prohibited; Media sanitized per NIST SP 800-88; Sensitive paper records shredded
Personnel screening before access to the systemBackground check; Citizenship / U.S. person verification; Non-disclosure agreement
Termination and transfer processDocumented checklist, access removed same day
Security awareness trainingAnnual agency security and privacy awareness training; quarterly phishing exercises
Role-based training for administrators and security staffAnnual role-based training for administrators, developers and the ISSO

7. Policies and governance

QuestionAnswer
Status of policies, plans and procedures
Access control policyDocumented and approved
Awareness and training policyDocumented and approved
Audit and accountability policyDocumented and approved
Assessment, authorization and monitoring policyDocumented and approved
Configuration management policy / planDocumented and approved
Contingency planning policy / contingency planDocumented and approved
Identification and authentication policyDocumented and approved
Incident response policy / planDocumented and approved
Maintenance policyDocumented and approved
Media protection policyDocumented and approved
Physical and environmental protection policyDocumented and approved
Planning policyDocumented and approved
Information security program planDocumented and approved
Personnel security policyDocumented and approved
PII processing and transparency policyDocumented and approved
Risk assessment policyDocumented and approved
System and services acquisition policyDocumented and approved
System and communications protection policyDocumented and approved
System and information integrity policyDocumented and approved
Supply chain risk management policy / planDocumented and approved
Rules of behavior / acceptable useDocumented and approved
Plan of action and milestones (POA&M) processDocumented and approved
How often are policies reviewed and updated?Annually by the agency CISO office
Organization-defined parameters (ODPs)Using values assigned by our agency or FedRAMP
Risk assessmentsAnnual risk assessment as part of ongoing authorization
Security control assessmentsContinuous monitoring with one-third of controls assessed each year by the agency assessment team
Supplier and acquisition securityCloud services must be FedRAMP authorized; software components are tracked in an SBOM and scanned for known vulnerabilities.
PrivacyPrivacy impact assessment completed and published; system of records notice in place; the Senior Agency Official for Privacy approves changes to PII collection.
Anything else an assessor should know?GrantLedger is a fictional system used as an example.

8. Follow-up questions

QuestionAnswer
Which controls are inherited from the agency landing zone?Logging infrastructure, the inspection firewall, AWS physical and environmental protection and the agency SOC are inherited; GrantLedger documents them as common controls.
How is PII minimized in reports?Exports to the financial system contain award identifiers and amounts only; PII is masked in non-production environments.