System interview
Tessellate CaseFlow
- Organization
- Tessellate Cloud, Inc. (fictional)
- 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 | Tessellate CaseFlow |
| Organization name | Tessellate Cloud, Inc. (fictional) |
| System owner (name and title) | Morgan Lindqvist, Vice President of Engineering |
| Security officer / ISSO (name and title) | Adaeze Okonkwo, Director of Compliance (ISSO) |
| Describe the system | Tessellate CaseFlow is a multi-tenant SaaS case management product sold to federal agencies for tracking investigations, FOIA requests and inspections. Tessellate Cloud, Inc. is seeking FedRAMP Rev5 Class C certification through an agency sponsor. Agency users create and manage cases, upload documents and generate reports. Customer data includes federal case records, PII of members of the public and uploaded documents. Each agency tenant's data is separated logically with tenant-specific encryption keys. CaseFlow runs on AWS GovCloud as containerised microservices on Amazon EKS with Amazon RDS for PostgreSQL and Amazon S3 for documents. The boundary includes the production VPCs, the CI/CD pipeline, the administration tools and the corporate identity provider used by Tessellate operators. |
| What kinds of information does the system handle? | Federal information (non-public); Personally identifiable information (PII); Law enforcement or investigative information |
| FIPS 199 security categorization | |
| Confidentiality | Moderate |
| Integrity | Moderate |
| Availability | Moderate |
| Authorization to operate | Authorization in progress |
| Authorizing official (name and title) | Agency sponsor's authorizing official (fictional): Janelle Ortiz, CIO |
| Why is the SSP needed? | FedRAMP authorization |
| Operational status | Operational |
2. Boundary and environment
| Question | Answer |
|---|---|
| Where is the system's information stored, processed or transmitted? | Cloud IaaS / PaaS |
| Cloud platforms in scope | AWS GovCloud |
| How many people use the system? | More than 1000 |
| Types of users | Employees; Privileged administrators; External partners / customers |
| Physical locations in scope | Tessellate offices in Raleigh, NC (no customer data); AWS GovCloud (US-East and US-West) |
| Do users access the system remotely? | Yes, most users work remotely |
| Describe the network and system boundary | Production runs in dedicated VPCs per environment with public load balancers behind AWS WAF, private EKS node groups and isolated data subnets. Operators reach production only through a zero-trust access broker. Separate AWS accounts are used for production, logging, security tooling and CI/CD. |
| Connections to external systems | Customer agency single sign-on (SAML or OIDC) per tenant. Outbound email notifications through Amazon SES. No other external connections. |
| External service providers | AWS GovCloud (FedRAMP High). Okta for operator identity (FedRAMP authorized). 3PAO engaged for the assessment. |
3. Identity and access
| Question | Answer |
|---|---|
| Identity provider / directory | Okta |
| Multi-factor authentication coverage | All users, all access |
| MFA methods in use | FIDO2 / hardware security key; Smart card / PIV / CAC |
| How is privileged (admin) access handled? | Operators have no standing production access; access is granted just in time for up to 2 hours with ticket approval and recorded sessions. |
| How are accounts requested, approved, reviewed and removed? | Operator accounts are provisioned from the HR system and removed within 4 hours of termination. Customer accounts are managed by each agency through its own SSO. Operator access is reviewed monthly. |
| Remote access methods | Zero-trust network access (ZTNA) |
| Wireless access to the system | Guest wireless only, isolated from the system |
| Mobile device management | Mobile devices are not permitted to access the system |
| Session lock, logout and lockout settings | Application sessions time out after 15 minutes idle and 12 hours absolute; operator lockout after 3 failed attempts for 30 minutes |
4. Endpoints and infrastructure
| Question | Answer |
|---|---|
| Endpoint operating systems | macOS |
| Server platforms | Linux; Containers / Kubernetes |
| Endpoint protection / EDR | CrowdStrike Falcon |
| Firewalls and boundary protection | AWS WAF with managed rules, AWS Shield Advanced, security groups with default-deny, and egress only through an inspection firewall with domain allow lists. |
| 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 | Corporate Google Workspace; not part of the system |
| Configuration baselines and enforcement | CIS Benchmarks |
| How are changes to the system requested, reviewed and approved? | All changes are made in code through pull requests with two approvals, automated security tests and a change record. Significant changes are notified to FedRAMP and customers under the significant change rules. |
| How is the hardware and software inventory maintained? | Generated continuously from AWS Config and Kubernetes; machine-readable inventory published monthly |
| Patch management tool and timelines | Images rebuilt daily; critical vulnerabilities fixed within 15 days, high within 30, moderate within 90 |
| Vulnerability scanning tool and frequency | Continuous container and host scanning, weekly authenticated scans, annual 3PAO penetration test |
| Backups | Point-in-time database recovery, daily cross-region snapshots and versioned S3; restores tested monthly |
5. Monitoring and response
| Question | Answer |
|---|---|
| Log collection / SIEM | Elastic |
| Who reviews logs and alerts, and how often? | In-house security team monitors alerts 24x7 with an on-call rotation; weekly audit review |
| Audit log retention period | 1 year online, 3 years archived |
| Time synchronization source | Amazon Time Sync Service |
| Incident response capability | Documented plan and trained team |
| How and how often is incident response tested? | Semi-annual tabletop and an annual functional exercise |
| How are incidents reported externally? | FedRAMP, affected agencies and CISA per FedRAMP incident communications requirements |
| Contingency planning | Contingency plan tested annually. RTO 8 hours, RPO 1 hour. Active-passive failover to a second GovCloud region. |
| Who performs system maintenance? | All maintenance is automated through the pipeline or done through recorded just-in-time sessions; no physical maintenance (cloud). |
6. Physical, media and personnel
| Question | Answer |
|---|---|
| Physical access controls | No company facility (fully remote / cloud); Physical protection inherited from AWS GovCloud |
| Environmental protections for on-premises equipment | None - cloud only; inherited from AWS GovCloud |
| Safeguards at alternate work sites (home offices) | Company-managed laptops with disk encryption, EDR and ZTNA; customer data is never downloaded to laptops |
| Media protection practices | Removable media prohibited; Media sanitized per NIST SP 800-88 |
| 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 | Security and privacy training on hire and annually; monthly phishing simulations |
| Role-based training for administrators and security staff | Annual role-based training for engineers with production access and for the security team |
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 | Draft |
| 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 | Draft |
| 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 and after significant changes |
| Organization-defined parameters (ODPs) | Using values assigned by our agency or FedRAMP |
| Risk assessments | Annual risk assessment, updated with each significant change |
| Security control assessments | Initial 3PAO assessment in progress; continuous monitoring planned under FedRAMP rules |
| Supplier and acquisition security | Third-party services must be FedRAMP authorized; open-source dependencies are tracked in an SBOM, scanned on every build and pinned to verified versions. |
| Privacy | Privacy impact assessment completed; a privacy officer reviews new data fields; customers control PII retention per tenant. |
| Anything else an assessor should know? | Tessellate CaseFlow is a fictional product used as an example. |
8. Follow-up questions
| Question | Answer |
|---|---|
| How are tenant encryption keys managed? | Each tenant has its own AWS KMS customer managed key in a FIPS 140-validated module; key administrators cannot use keys and key users cannot manage them. |
| Which controls are inherited from AWS GovCloud? | Physical and environmental protection, media protection for the underlying hardware and parts of contingency planning are inherited; customer responsibilities are documented for agencies. |