System interview
Halvorsen CUI Enclave
- Organization
- Halvorsen Signal Labs Inc. (fictional)
- Framework
- NIST SP 800-171 Rev. 3 — Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations
- Exported
- 2026-11-22
- Answered
- 81 of 81 questions
- This file holds
- Interview only
1. System identification
| Question | Answer |
|---|---|
| System name | Halvorsen CUI Enclave |
| Organization name | Halvorsen Signal Labs Inc. (fictional) |
| System owner (name and title) | Erik Halvorsen, Chief Executive Officer |
| Security officer / ISSO (name and title) | Tamsin Reyes, Information System Security Officer |
| Describe the system | Halvorsen Signal Labs designs RF antennas and test fixtures for Navy shipboard communications under DoD subcontracts. The Halvorsen CUI Enclave holds antenna designs, test data and program correspondence marked CUI. The enclave has two parts: an on-premises cluster of Windows servers in a locked server room that hosts the simulation and file servers, and 22 Windows engineering workstations that connect only to that cluster. Program staff exchange CUI with the Navy prime through Microsoft 365 GCC High email. CUI enters by encrypted email and the prime's file exchange, is processed on the simulation servers, and leaves as reports and design packages by the same routes. The enclave is separated from the corporate network by a dedicated firewall. |
| What kinds of CUI does the system handle? | Controlled Technical Information (CTI); Export-controlled (ITAR / EAR) |
| Why is the SSP needed? | DFARS 252.204-7012; CMMC Level 2 |
| Operational status | Operational |
2. Boundary and environment
| Question | Answer |
|---|---|
| Where is CUI stored, processed or transmitted? | Cloud SaaS (e.g. Microsoft 365); On-premises servers; Company laptops / desktops |
| Cloud platforms in scope | Microsoft 365 GCC High |
| How many people use the system? | 11-50 |
| Types of users | Employees; Privileged administrators |
| Physical locations in scope | Engineering building in Huntsville, Alabama |
| Do users access the system remotely? | No remote access |
| Describe the network and system boundary | The enclave is a separate network segment behind its own firewall. Workstations and servers sit on two VLANs inside it. Internet access from the enclave is limited to GCC High and update services through a proxy. The corporate network cannot reach the enclave. |
| Connections to external systems | The Navy prime's secure file exchange (outbound HTTPS from one transfer workstation). Microsoft 365 GCC High for email. |
| External service providers | Microsoft (GCC High). No managed IT provider. |
3. Identity and access
| Question | Answer |
|---|---|
| Identity provider / directory | On-premises Active Directory |
| Multi-factor authentication coverage | All users, all access |
| MFA methods in use | Smart card / PIV / CAC |
| How is privileged (admin) access handled? | Two administrators use separate admin accounts with smart cards from a dedicated admin workstation. Domain Admin membership is empty except during approved maintenance. |
| How are accounts requested, approved, reviewed and removed? | Requests are approved by the program manager and the ISSO on a signed form. Accounts inactive for 30 days are disabled by a scheduled script. Accounts are reviewed every quarter. |
| Remote access methods | None |
| Wireless access to the system | No wireless |
| Mobile device management | Mobile devices are not permitted to access CUI |
| Session lock, logout and lockout settings | Screen lock after 10 minutes; sessions end after 12 hours; lockout after 3 failed smart card PIN attempts |
4. Endpoints and infrastructure
| Question | Answer |
|---|---|
| Endpoint operating systems | Windows 11 |
| Server platforms | Windows Server; Virtualization (VMware / Hyper-V) |
| Endpoint protection / EDR | Microsoft Defender for Endpoint |
| Firewalls and boundary protection | Dedicated enclave firewall with default-deny in both directions and an authenticating web proxy for the few allowed internet destinations. |
| Is the CUI environment segmented from the rest of the network? | Yes, a dedicated enclave |
| Encryption at rest | BitLocker; Database / application-level encryption |
| Encryption in transit | TLS 1.2 or later; Encrypted email (S/MIME, OME or similar) |
| Is cryptography protecting CUI FIPS-validated? | Yes, everywhere CUI is protected |
| Email and collaboration platform | Exchange Online in GCC High with S/MIME |
| Configuration baselines and enforcement | DISA STIGs; Group Policy |
| How are changes to the system requested, reviewed and approved? | A change control board of the ISSO, the lead engineer and an administrator meets every two weeks. Every change has a security impact analysis. |
| How is the hardware and software inventory maintained? | Hardware and software inventory in a SharePoint list, reconciled quarterly against Active Directory and a network scan |
| Patch management tool and timelines | WSUS: critical patches within 14 days, all others within 30 days |
| Vulnerability scanning tool and frequency | Tenable Nessus authenticated scans monthly |
| Backups | Nightly Veeam backups to an encrypted appliance, weekly encrypted tapes stored off site; restores tested quarterly |
5. Monitoring and response
| Question | Answer |
|---|---|
| Log collection / SIEM | Wazuh |
| Who reviews logs and alerts, and how often? | The ISSO reviews Wazuh alerts daily and audit reports weekly |
| Audit log retention period | 1 year online, 3 years archived |
| Time synchronization source | Domain controllers synchronize to a GPS time server in the server room |
| Incident response capability | Documented plan and trained team |
| How and how often is incident response tested? | Annual tabletop and a semi-annual phishing response drill |
| How are incidents reported externally? | DIBNet within 72 hours; the Navy prime and contracting officer are notified |
| Who performs system maintenance? | Administrators perform maintenance on site. Vendor engineers are escorted and use enclave-owned tools only. |
6. Physical, media and personnel
| Question | Answer |
|---|---|
| Physical access controls | Badge / electronic access control; Visitor log and escort; Cameras; Alarm system; Locked server room / rack |
| Safeguards at alternate work sites (home offices) | Not applicable: CUI work happens only in the engineering building |
| Media protection practices | Removable media restricted to encrypted company devices; CUI media marked; Media sanitized per NIST SP 800-88; Paper CUI shredded; Media in transit tracked and encrypted |
| Personnel screening before access to CUI | Background check; Citizenship / U.S. person verification; Non-disclosure agreement |
| Termination and transfer process | Documented checklist, access removed same day |
| Security awareness training | Annual training covering CUI marking and handling, insider threat and social engineering |
| Role-based training for administrators and security staff | Administrators hold Security+ and complete annual STIG training |
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 |
| Configuration management policy / plan | Documented and approved |
| Identification and authentication policy | Documented and approved |
| Incident response plan | Documented and approved |
| Maintenance policy | Documented and approved |
| Media protection policy | Documented and approved |
| Personnel security policy | Documented and approved |
| Physical protection policy | Documented and approved |
| Risk assessment policy | Documented and approved |
| Security assessment and monitoring policy | Documented and approved |
| System and communications protection policy | Documented and approved |
| System and information integrity policy | Documented and approved |
| Security planning policy | Documented and approved |
| System and services acquisition policy | Documented and approved |
| Supply chain risk management 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 |
| Organization-defined parameters (ODPs) | Using values assigned by the federal agency / DoD |
| Risk assessments | Annual risk assessment by the ISSO; updated after significant changes |
| Security control assessments | Annual self-assessment; third-party assessment completed last year |
| Supplier and acquisition security | Equipment is bought from authorized resellers and inspected on receipt. Software comes only from vendor sites and is checked against published hashes. |
| Anything else an assessor should know? | Organization-defined parameters follow the DoD values for NIST SP 800-171 Rev. 3 published in April 2025. |
8. Follow-up questions
| Question | Answer |
|---|---|
| How does the transfer workstation keep CUI from leaving through the internet connection? | Only the prime's file exchange is reachable from it, through the proxy, and every transfer is logged and reviewed weekly by the ISSO. |
| Who holds the smart card issuance role? | The ISSO issues smart cards after identity proofing in person; the CEO approves issuance for administrators. |