System interview

Corvid Design Enclave

Organization
Corvid Microelectronics Inc. (fictional)
Framework
NIST SP 800-172 Rev. 3 — 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

QuestionAnswer
System nameCorvid Design Enclave
Organization nameCorvid Microelectronics Inc. (fictional)
System owner (name and title)Aiko Matsuda, Chief Technology Officer
Security officer / ISSO (name and title)Rafael Quintero, Director of Security Engineering
Describe the systemCorvid Microelectronics designs radiation-hardened ASICs for satellites supporting critical national security programs. The Corvid Design Enclave holds chip designs, process design kits and verification results that are CUI and export-controlled.

The enclave is a private cloud of electronic design automation (EDA) servers in Corvid's data center with 80 thin-client workstations. Designs arrive from government customers through a secure exchange, are developed and verified inside the enclave and leave as tape-out packages sent to an accredited foundry over an encrypted dedicated link.

The enclave applies NIST SP 800-172 Rev. 3 enhanced requirements because the programs it supports are high-value targets of advanced persistent threats.
What kinds of CUI does the system handle?Controlled Technical Information (CTI); Export-controlled (ITAR / EAR); Proprietary business information received under contract
Why is the SSP needed?DFARS 252.204-7012; Other federal contract clause; Prime contractor / customer flow-down
Operational statusOperational

2. Boundary and environment

QuestionAnswer
Where is CUI stored, processed or transmitted?On-premises servers
Cloud platforms in scopeNone
How many people use the system?51-250
Types of usersEmployees; Contractors; Privileged administrators
Physical locations in scopeDesign center and data center in Albuquerque, New Mexico
Do users access the system remotely?No remote access
Describe the network and system boundaryThin clients connect to virtual desktops on the EDA cluster. The enclave is split into design, verification, management and transfer zones. Components that fail authentication or configuration checks cannot join the network (802.1X with posture checks).
Connections to external systemsGovernment customer secure exchange (transfer zone, manual review). Encrypted dedicated link to the accredited foundry for tape-out only.
External service providersThe accredited foundry receives tape-out packages. EDA tool vendors provide licences through an on-premises licence server; no vendor access.

3. Identity and access

QuestionAnswer
Identity provider / directoryOn-premises Active Directory
Multi-factor authentication coverageAll users, all access
MFA methods in useFIDO2 / hardware security key; Smart card / PIV / CAC
How is privileged (admin) access handled?Just-in-time privileged access through a PAM platform with dual authorization for tape-out, key management and baseline changes; all privileged sessions are recorded.
How are accounts requested, approved, reviewed and removed?Accounts are approved by the program lead and security, disabled after 21 days of inactivity and reviewed monthly; contractor accounts expire with their contract.
Remote access methodsNone
Wireless access to the systemNo wireless
Mobile device managementMobile devices are not permitted to access CUI
Session lock, logout and lockout settingsVirtual desktops lock after 5 minutes and disconnect after 30; lockout after 3 failed attempts for 60 minutes

4. Endpoints and infrastructure

QuestionAnswer
Endpoint operating systemsLinux
Server platformsLinux; Virtualization (VMware / Hyper-V); Containers / Kubernetes
Endpoint protection / EDRSentinelOne
Firewalls and boundary protectionNo internet access from the enclave. Zone firewalls enforce default-deny. Deception hosts in each zone alert on any contact.
Is the CUI environment segmented from the rest of the network?Yes, a dedicated enclave
Encryption at restLUKS; Database / application-level encryption
Encryption in transitTLS 1.2 or later; IPsec / SSL VPN
Is cryptography protecting CUI FIPS-validated?Yes, everywhere CUI is protected
Email and collaboration platformNo email in the enclave; an internal wiki and ticketing system run inside it
Configuration baselines and enforcementCIS Benchmarks; DISA STIGs
How are changes to the system requested, reviewed and approved?Infrastructure is defined in code; every change is peer reviewed, approved by the change board and deployed by pipeline. Systems are rebuilt from known-good images monthly.
How is the hardware and software inventory maintained?Automated discovery feeds an authoritative inventory every hour; unknown devices are blocked
Patch management tool and timelinesCritical patches within 7 days after lab testing; others within 30 days
Vulnerability scanning tool and frequencyContinuous agent-based scanning plus weekly network scans; penetration testing twice a year
BackupsImmutable backups to an isolated vault every 4 hours; restores tested monthly

5. Monitoring and response

QuestionAnswer
Log collection / SIEMElastic
Who reviews logs and alerts, and how often?Security operations center staffed 24/7; threat hunting weekly and when indicators warrant
Audit log retention period3 years
Time synchronization sourceStratum-1 GPS time servers inside the enclave
Incident response capabilityDocumented plan and trained team
How and how often is incident response tested?Quarterly exercises, including an annual purple team exercise
How are incidents reported externally?Government customers within 24 hours; DIBNet within 72 hours
Who performs system maintenance?Corvid staff only, on site; hardware returned for repair has storage removed and destroyed first.

6. Physical, media and personnel

QuestionAnswer
Physical access controlsBadge / electronic access control; Visitor log and escort; Cameras; Alarm system; Locked server room / rack
Safeguards at alternate work sites (home offices)Not applicable: enclave work happens only in the design center
Media protection practicesRemovable media prohibited; CUI media marked; Media sanitized per NIST SP 800-88; Paper CUI shredded
Personnel screening before access to CUIBackground check; Citizenship / U.S. person verification; Non-disclosure agreement
Termination and transfer processDocumented checklist, access removed same day
Security awareness trainingQuarterly training on APT tactics, social engineering and insider threat with practical exercises
Role-based training for administrators and security staffRole-based training for EDA administrators, SOC analysts and developers twice a 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
Configuration management policy / planDocumented and approved
Identification and authentication policyDocumented and approved
Incident response planDocumented and approved
Maintenance policyDocumented and approved
Media protection policyDocumented and approved
Personnel security policyDocumented and approved
Physical protection policyDocumented and approved
Risk assessment policyDocumented and approved
Security assessment and monitoring policyDocumented and approved
System and communications protection policyDocumented and approved
System and information integrity policyDocumented and approved
Security planning policyDocumented and approved
System and services acquisition policyDocumented and approved
Supply chain risk management planDraft
Rules of behavior / acceptable useDocumented and approved
Plan of action and milestones (POA&M) processDocumented and approved
How often are policies reviewed and updated?Every six months
Organization-defined parameters (ODPs)Defined our own values
Risk assessmentsThreat-informed risk assessment every quarter using commercial threat intelligence and government briefings
Security control assessmentsAnnual independent assessment against NIST SP 800-171 Rev. 3 and SP 800-172 Rev. 3
Supplier and acquisition securityFoundry and EDA vendors are vetted and contractually bound to security requirements; incoming hardware is verified against known-good images. The supply chain plan is being updated for SP 800-172 Rev. 3.
Anything else an assessor should know?Enhanced requirements are applied to the whole enclave; there are no excluded components.

8. Follow-up questions

QuestionAnswer
How is the integrity of the EDA tool binaries verified?Tools are installed only from vendor media whose signatures are verified, and file integrity monitoring compares them with recorded hashes daily.
What diversity or deception measures are in place?Deception hosts and decoy credentials are deployed in every zone; verification servers run a different OS distribution from design servers.