System interview
Quillfeather Classroom
- Organization
- Quillfeather Learning Co. (fictional)
- Framework
- NIST Cybersecurity Framework 2.0 — The NIST Cybersecurity Framework (CSF) 2.0
- Exported
- 2026-11-22
- Answered
- 84 of 84 questions
- This file holds
- Interview only
1. System identification
| Question | Answer |
|---|---|
| System name | Quillfeather Classroom |
| Organization name | Quillfeather Learning Co. (fictional) |
| System owner (name and title) | Benedikt Aurelio, Chief Executive Officer |
| Security officer / ISSO (name and title) | Shreya Kulkarni, Head of Security |
| Describe the system | Quillfeather Classroom is a SaaS writing-feedback platform used by about 600 K-12 schools. Teachers post assignments, students submit essays, and the platform gives rubric-based feedback and tracks progress. It stores student names, school email addresses, essays and grades, teacher accounts and school billing contacts. Schools sign in through Google or Microsoft single sign-on and sync rosters from their student information systems. The platform runs on Google Cloud (Cloud Run, Cloud SQL for PostgreSQL and Cloud Storage). Quillfeather's 45 staff work remotely. The company is adopting the NIST CSF 2.0 to describe its current security posture to school districts and its cyber insurer. |
| What kinds of information does the system handle? | Personally identifiable information (PII); Financial information; Student education records (essays, grades) |
| Why is this assessment being done? | Customer or partner requirement; Board or executive direction; Cyber insurance |
| Operational status | Operational |
2. Boundary and environment
| Question | Answer |
|---|---|
| Where is the system's information stored, processed or transmitted? | Cloud SaaS (e.g. Microsoft 365); Cloud IaaS / PaaS; Organization laptops / desktops |
| Cloud platforms in scope | Google Workspace; Google Cloud |
| How many people use the system? | More than 1000 |
| Types of users | Employees; Contractors; Privileged administrators; External partners / customers |
| Physical locations in scope | Fully remote company; registered office in Madison, Wisconsin |
| Do users access the system remotely? | Yes, most users work remotely |
| Describe the network and system boundary | Serverless application on Cloud Run behind Google Cloud Armor, with Cloud SQL and Cloud Storage reachable only through private service connections. Separate projects for production, staging and security logging. |
| Connections to external systems | Roster sync with schools' student information systems through a rostering provider; Google and Microsoft single sign-on for schools; Stripe for billing. |
| External service providers | Google Cloud and Google Workspace, Stripe (billing), a rostering integration provider and an outsourced 24x7 managed detection and response provider. |
3. Identity and access
| Question | Answer |
|---|---|
| Identity provider / directory | Google Workspace identity |
| Multi-factor authentication coverage | All users, all access |
| MFA methods in use | Authenticator app; FIDO2 / hardware security key |
| How is privileged (admin) access handled? | Production access is granted just in time through Google Cloud Privileged Access Manager for up to 1 hour; four engineers are eligible. |
| How are accounts requested, approved, reviewed and removed? | Staff accounts are created from the HR system on the start date and suspended at termination. Quarterly access reviews. School accounts are managed by each school through SSO and roster sync. |
| Remote access methods | Direct to cloud services only |
| Wireless access to the system | No wireless |
| Mobile device management | Mobile devices are used but not managed |
| Session lock, logout and lockout settings | Laptops lock after 5 minutes; Workspace sessions re-authenticate every 14 days; production consoles require re-authentication every hour |
4. Endpoints and infrastructure
| Question | Answer |
|---|---|
| Endpoint operating systems | macOS |
| Server platforms | Containers / Kubernetes; Google Cloud Run (serverless containers) |
| Endpoint protection / EDR | SentinelOne |
| Firewalls and boundary protection | Cloud Armor web application firewall and rate limiting; no inbound access to data services from the internet. |
| Is the system segmented from other networks? | Not applicable (cloud only) |
| Encryption at rest | FileVault; Cloud provider encryption |
| Encryption in transit | TLS 1.2 or later |
| Is the cryptography protecting system information FIPS-validated? | No |
| Email and collaboration platform | Google Workspace |
| Configuration baselines and enforcement | CIS Benchmarks; Intune / MDM configuration profiles; Laptops managed with Kandji; cloud configuration checked by Security Command Center |
| How are changes to the system requested, reviewed and approved? | Pull requests with peer review and automated tests; production deploys through CI/CD only. |
| How is the hardware and software inventory maintained? | Laptops in the device management tool; cloud assets in Cloud Asset Inventory |
| Patch management tool and timelines | Laptop updates enforced within 7 days; container base images rebuilt weekly |
| Vulnerability scanning tool and frequency | Dependency and container scanning on every build; annual third-party penetration test |
| Backups | Cloud SQL point-in-time recovery for 7 days and daily exports kept 90 days; restore tested twice a year |
5. Monitoring and response
| Question | Answer |
|---|---|
| Log collection / SIEM | Managed by an MSSP / MDR |
| Who reviews logs and alerts, and how often? | MDR provider monitors 24x7; the security team reviews findings weekly |
| Audit log retention period | 1 year |
| Time synchronization source | Google Cloud and Apple time services |
| Incident response capability | Documented plan, not yet exercised |
| How and how often is incident response tested? | First tabletop exercise scheduled next quarter |
| How are incidents reported externally? | Affected schools within 72 hours and state authorities as required by student data privacy laws |
| Contingency planning | Recovery runbooks for the database and application; recovery time objective 8 hours. No formal business continuity plan yet. |
| Who performs system maintenance? | Engineering team through CI/CD; Google maintains the platform. |
6. Physical, media and personnel
| Question | Answer |
|---|---|
| Physical access controls | No company facility (fully remote / cloud) |
| Safeguards at alternate work sites (home offices) | Company laptops only for work; student data may not be downloaded |
| Media protection practices | Removable media prohibited |
| Personnel screening before access to the system | Background check; Non-disclosure agreement |
| Termination and transfer process | Documented checklist, access removed same day |
| Security awareness training | Annual training on security and student data privacy; quarterly phishing simulations |
| Role-based training for administrators and security staff | Secure coding training for engineers each year |
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 | Draft |
| Identification and authentication policy | Documented and approved |
| Incident response policy / plan | Documented and approved |
| Maintenance policy | Informal practice only |
| Media protection policy | Informal practice only |
| Physical and environmental protection policy | None |
| Planning policy | Documented and approved |
| Information security program plan | Informal practice only |
| Personnel security policy | Documented and approved |
| PII processing and transparency policy | Documented and approved |
| Risk assessment policy | Draft |
| 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 | Informal practice only |
| Rules of behavior / acceptable use | Documented and approved |
| Plan of action and milestones (POA&M) process | Informal practice only |
| How often are policies reviewed and updated? | Annually |
| Risk assessments | First formal risk assessment completed this year by an external consultant |
| Security control assessments | Annual penetration test; SOC 2 Type I completed, Type II audit in progress |
| Supplier and acquisition security | Vendors handling student data sign a data privacy agreement and are reviewed when onboarded; no recurring vendor reviews yet. |
| Anything else an assessor should know? | Quillfeather is building a Target Profile with its board to prioritise improvements, starting with incident response exercises and vendor risk management. |
8. Follow-up questions
| Question | Answer |
|---|---|
| Who on the board oversees cybersecurity risk? | The board's audit committee receives a quarterly security report from the Head of Security and approves the annual security budget. |
| How are school districts told about changes to how student data is used? | Material changes are announced 30 days in advance by email to district contacts and in the data privacy agreement change log. |