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
| Question | Answer |
|---|---|
| System name | GrantLedger |
| Organization name | Northfield 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 system | GrantLedger 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 | |
| Confidentiality | Moderate |
| Integrity | Moderate |
| Availability | Moderate |
| Authorization to operate | Authorized (ATO in place) |
| Authorizing official (name and title) | Raymond Akers, Chief Information Officer |
| Why is the SSP needed? | FISMA (federal agency system) |
| Operational status | Operational |
2. Boundary and environment
| Question | Answer |
|---|---|
| Where is the system's information stored, processed or transmitted? | Cloud IaaS / PaaS; Organization laptops / desktops |
| Cloud platforms in scope | AWS GovCloud |
| How many people use the system? | More than 1000 |
| Types of users | Employees; Contractors; Privileged administrators; External partners / customers |
| Physical locations in scope | Agency 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 boundary | Three-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 systems | Inbound 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 providers | AWS GovCloud (FedRAMP High). Login.gov for public identity. Development and operations contractor under an agency contract. |
3. Identity and access
| Question | Answer |
|---|---|
| Identity provider / directory | Okta; Agency staff use PIV through Okta; grantees use Login.gov |
| Multi-factor authentication coverage | All users, all access |
| MFA methods in use | Authenticator 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 methods | Zero-trust network access (ZTNA) |
| Wireless access to the system | Guest wireless only, isolated from the system |
| Mobile device management | Microsoft Intune |
| Session lock, logout and lockout settings | Staff sessions time out after 15 minutes idle; lockout after 3 failed attempts for 15 minutes |
4. Endpoints and infrastructure
| Question | Answer |
|---|---|
| Endpoint operating systems | Windows 11; macOS |
| Server platforms | Linux; Containers / Kubernetes |
| Endpoint protection / EDR | Microsoft Defender for Endpoint |
| Firewalls and boundary protection | AWS 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 rest | Cloud provider encryption; Database / application-level encryption |
| Encryption in transit | TLS 1.2 or later |
| Is the cryptography protecting system information FIPS-validated? | Yes, everywhere it is used |
| Email and collaboration platform | Agency Microsoft 365 GCC; not part of the system |
| Configuration baselines and enforcement | CIS 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 timelines | Container images rebuilt weekly; critical vulnerabilities fixed within 15 days, high within 30 |
| Vulnerability scanning tool and frequency | Weekly authenticated scans; container and code scanning on every build; annual penetration test |
| Backups | Automated database snapshots every 4 hours and daily cross-region backups; restore tested quarterly |
5. Monitoring and response
| Question | Answer |
|---|---|
| Log collection / SIEM | Splunk |
| Who reviews logs and alerts, and how often? | The agency SOC monitors alerts 24x7; the ISSO reviews audit reports weekly |
| Audit log retention period | 1 year online, 3 years archived, per agency policy |
| Time synchronization source | Amazon Time Sync Service |
| Incident response capability | Documented 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 planning | Contingency 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
| Question | Answer |
|---|---|
| Physical access controls | Badge / electronic access control; Visitor log and escort; Cameras |
| Environmental protections for on-premises equipment | None - 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 practices | Removable media prohibited; Media sanitized per NIST SP 800-88; Sensitive paper records shredded |
| Personnel screening before access to the system | Background check; Citizenship / U.S. person verification; Non-disclosure agreement |
| Termination and transfer process | Documented checklist, access removed same day |
| Security awareness training | Annual agency security and privacy awareness training; quarterly phishing exercises |
| Role-based training for administrators and security staff | Annual role-based training for administrators, developers and the ISSO |
7. Policies and governance
| Question | Answer |
|---|---|
| Status of policies, plans and procedures | |
| Access control policy | Documented and approved |
| Awareness and training policy | Documented and approved |
| Audit and accountability policy | Documented and approved |
| Assessment, authorization and monitoring policy | Documented and approved |
| Configuration management policy / plan | Documented and approved |
| Contingency planning policy / contingency plan | Documented and approved |
| Identification and authentication policy | Documented and approved |
| Incident response policy / plan | Documented and approved |
| Maintenance policy | Documented and approved |
| Media protection policy | Documented and approved |
| Physical and environmental protection policy | Documented and approved |
| Planning policy | Documented and approved |
| Information security program plan | Documented and approved |
| Personnel security policy | Documented and approved |
| PII processing and transparency policy | Documented and approved |
| Risk assessment policy | Documented and approved |
| System and services acquisition policy | Documented and approved |
| System and communications protection policy | Documented and approved |
| System and information integrity policy | Documented and approved |
| Supply chain risk management policy / plan | Documented and approved |
| Rules of behavior / acceptable use | Documented and approved |
| Plan of action and milestones (POA&M) process | Documented 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 assessments | Annual risk assessment as part of ongoing authorization |
| Security control assessments | Continuous monitoring with one-third of controls assessed each year by the agency assessment team |
| Supplier and acquisition security | Cloud services must be FedRAMP authorized; software components are tracked in an SBOM and scanned for known vulnerabilities. |
| Privacy | Privacy 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
| Question | Answer |
|---|---|
| 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. |