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

QuestionAnswer
System nameQuillfeather Classroom
Organization nameQuillfeather 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 systemQuillfeather 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 statusOperational

2. Boundary and environment

QuestionAnswer
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 scopeGoogle Workspace; Google Cloud
How many people use the system?More than 1000
Types of usersEmployees; Contractors; Privileged administrators; External partners / customers
Physical locations in scopeFully remote company; registered office in Madison, Wisconsin
Do users access the system remotely?Yes, most users work remotely
Describe the network and system boundaryServerless 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 systemsRoster sync with schools' student information systems through a rostering provider; Google and Microsoft single sign-on for schools; Stripe for billing.
External service providersGoogle Cloud and Google Workspace, Stripe (billing), a rostering integration provider and an outsourced 24x7 managed detection and response provider.

3. Identity and access

QuestionAnswer
Identity provider / directoryGoogle Workspace identity
Multi-factor authentication coverageAll users, all access
MFA methods in useAuthenticator 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 methodsDirect to cloud services only
Wireless access to the systemNo wireless
Mobile device managementMobile devices are used but not managed
Session lock, logout and lockout settingsLaptops lock after 5 minutes; Workspace sessions re-authenticate every 14 days; production consoles require re-authentication every hour

4. Endpoints and infrastructure

QuestionAnswer
Endpoint operating systemsmacOS
Server platformsContainers / Kubernetes; Google Cloud Run (serverless containers)
Endpoint protection / EDRSentinelOne
Firewalls and boundary protectionCloud 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 restFileVault; Cloud provider encryption
Encryption in transitTLS 1.2 or later
Is the cryptography protecting system information FIPS-validated?No
Email and collaboration platformGoogle Workspace
Configuration baselines and enforcementCIS 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 timelinesLaptop updates enforced within 7 days; container base images rebuilt weekly
Vulnerability scanning tool and frequencyDependency and container scanning on every build; annual third-party penetration test
BackupsCloud SQL point-in-time recovery for 7 days and daily exports kept 90 days; restore tested twice a year

5. Monitoring and response

QuestionAnswer
Log collection / SIEMManaged 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 period1 year
Time synchronization sourceGoogle Cloud and Apple time services
Incident response capabilityDocumented 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 planningRecovery 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

QuestionAnswer
Physical access controlsNo 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 practicesRemovable media prohibited
Personnel screening before access to the systemBackground check; Non-disclosure agreement
Termination and transfer processDocumented checklist, access removed same day
Security awareness trainingAnnual training on security and student data privacy; quarterly phishing simulations
Role-based training for administrators and security staffSecure coding training for engineers each year

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 planDraft
Identification and authentication policyDocumented and approved
Incident response policy / planDocumented and approved
Maintenance policyInformal practice only
Media protection policyInformal practice only
Physical and environmental protection policyNone
Planning policyDocumented and approved
Information security program planInformal practice only
Personnel security policyDocumented and approved
PII processing and transparency policyDocumented and approved
Risk assessment policyDraft
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 / planInformal practice only
Rules of behavior / acceptable useDocumented and approved
Plan of action and milestones (POA&M) processInformal practice only
How often are policies reviewed and updated?Annually
Risk assessmentsFirst formal risk assessment completed this year by an external consultant
Security control assessmentsAnnual penetration test; SOC 2 Type I completed, Type II audit in progress
Supplier and acquisition securityVendors 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

QuestionAnswer
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.