System interview
Ironbark Program Enclave
- Organization
- Ironbark Defense Systems Corp. (fictional)
- Framework
- NIST SP 800-172 (February 2021) — Enhanced Security Requirements for Protecting Controlled Unclassified Information
- Exported
- 2026-11-22
- Answered
- 81 of 81 questions
- This file holds
- Interview only
1. System identification
| Question | Answer |
|---|---|
| System name | Ironbark Program Enclave |
| Organization name | Ironbark Defense Systems Corp. (fictional) |
| System owner (name and title) | Col. (ret.) Hannah Brandt, Vice President of Programs |
| Security officer / ISSO (name and title) | Devin Achterberg, Chief Information Security Officer |
| Describe the system | Ironbark Defense Systems develops guidance-electronics firmware for a DoD missile program designated critical, which requires CMMC Level 3. The Ironbark Program Enclave is the isolated development environment for that program: build servers, source control, a hardware-in-the-loop test lab and 60 engineering workstations. CUI includes firmware source code, interface control documents and test results. It enters through the DoD program office's secure exchange, is developed and tested inside the enclave, and leaves only as signed firmware releases and reports through the same exchange. The enclave runs in Ironbark's own data center, physically and logically isolated from the corporate network. CMMC Level 2 for this enclave was certified last year. |
| 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; CMMC Level 3 |
| Operational status | Operational |
2. Boundary and environment
| Question | Answer |
|---|---|
| Where is CUI stored, processed or transmitted? | On-premises servers; Company laptops / desktops |
| Cloud platforms in scope | None |
| How many people use the system? | 51-250 |
| Types of users | Employees; Privileged administrators |
| Physical locations in scope | Secure development building and data center in Tucson, Arizona |
| Do users access the system remotely? | No remote access |
| Describe the network and system boundary | The enclave has separate segments for workstations, build and source control, the test lab and management. A dedicated data diode carries logs to the security operations center; nothing else crosses from the enclave. A cross-domain transfer station with manual review is the only path for files in and out. |
| Connections to external systems | DoD program office secure exchange through the reviewed transfer station. One-way log feed to the SOC through a data diode. |
| External service providers | None; all operations are performed by Ironbark staff. |
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? | Privileged access uses a PAM vault with session recording and dual authorization for production build and signing operations. Admin workstations are dedicated and hardened. |
| How are accounts requested, approved, reviewed and removed? | Accounts require program manager and security approval, are disabled after 30 days of inactivity and are reviewed monthly. |
| 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 5 minutes; lockout after 3 failed attempts until an administrator releases it |
4. Endpoints and infrastructure
| Question | Answer |
|---|---|
| Endpoint operating systems | Windows 11; Linux |
| Server platforms | Linux; Virtualization (VMware / Hyper-V) |
| Endpoint protection / EDR | CrowdStrike Falcon |
| Firewalls and boundary protection | The enclave has no internet connection. Internal segments are separated by firewalls with default-deny rules and an allow list per service. |
| Is the CUI environment segmented from the rest of the network? | Yes, a dedicated enclave |
| Encryption at rest | BitLocker; LUKS; Database / application-level encryption |
| Encryption in transit | TLS 1.2 or later; IPsec / SSL VPN |
| Is cryptography protecting CUI FIPS-validated? | Yes, everywhere CUI is protected |
| Email and collaboration platform | No email inside the enclave; program correspondence uses the transfer station |
| Configuration baselines and enforcement | DISA STIGs; Group Policy |
| How are changes to the system requested, reviewed and approved? | A configuration control board approves every change. Automated tools compare every system against its approved baseline nightly and quarantine devices that drift. |
| How is the hardware and software inventory maintained? | An authoritative component repository in the CMDB, populated by automated discovery every 6 hours |
| Patch management tool and timelines | Patches are tested in the lab, then applied within 14 days for critical and 30 days for others |
| Vulnerability scanning tool and frequency | Tenable.sc authenticated scans weekly; annual penetration test by an approved third party |
| Backups | Nightly backups to an isolated immutable backup system; quarterly restore tests |
5. Monitoring and response
| Question | Answer |
|---|---|
| Log collection / SIEM | Splunk |
| Who reviews logs and alerts, and how often? | The 24/7 Ironbark security operations center monitors alerts continuously and runs threat hunts |
| Audit log retention period | 3 years |
| Time synchronization source | Enclave time servers synchronize to GPS receivers |
| Incident response capability | Documented plan and trained team |
| How and how often is incident response tested? | Semi-annual exercises, including a red team exercise each year |
| How are incidents reported externally? | DIBNet within 72 hours; the program office is notified within 24 hours |
| Who performs system maintenance? | Ironbark staff only, on site, with tools kept in the enclave and inspected before use. |
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: no CUI work is permitted outside the secure 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 | On hire, after significant cyber events and annually; includes social engineering, APT and insider threat scenarios with practical exercises |
| Role-based training for administrators and security staff | Role-based training for administrators, developers and SOC analysts annually |
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 and after significant changes or incidents |
| Organization-defined parameters (ODPs) | Using values assigned by the federal agency / DoD |
| Risk assessments | Quarterly threat-informed risk assessment using commercial and DoD-provided threat intelligence |
| Security control assessments | Annual independent assessment; CMMC Level 2 certified, Level 3 assessment by DCMA DIBCAC scheduled |
| Supplier and acquisition security | A supply chain risk management plan covers suppliers of hardware, firmware tools and test equipment; components are bought only from authorized sources and verified on receipt; the plan is reviewed annually. |
| Anything else an assessor should know? | The SOC operates 24/7 and the cyber incident response team can deploy within 24 hours. |
8. Follow-up questions
| Question | Answer |
|---|---|
| How are firmware releases protected from tampering before delivery? | Releases are built on isolated build servers and signed with keys held in an HSM that needs two people to operate; the program office verifies signatures on receipt. |
| Are any specialized assets (test equipment, OT) outside the enhanced requirements? | Hardware-in-the-loop test equipment sits in its own segment and is in scope; nothing is excluded. |