Care with sensitive research data.
When research comes with additional security or data-handling requirements, I help your team build them into the system and its daily operation. The examples below describe the environments and frameworks I have worked with.
Federal and controlled unclassified information
NIST SP 800-171 across storage, scheduler and identity, with the system security plan and POA&M that go with it. NIST SP 800-53 on federal systems, FISMA responsibility as a named security officer, and CMMC readiness for defense subcontracts. DISA STIG and CIS Benchmark hardening on compute at scale. NIST SP 800-88 media sanitization on decommission. FIPS 140 validated cryptography where it is required, and the exemption argument where a validated module does not exist for the hardware.
Controlled-access research data
The NIH Genomic Data Sharing Policy and the dbGaP security best practices as they actually apply to a shared cluster: where controlled-access data may live, who may reach it, how access is logged, and how it is destroyed at the end of the approved period. NIH Data Management and Sharing plans, data use agreements and honest broker arrangements, IRB-driven access boundaries, and the awkward part — enforcing per-study separation on a filesystem several hundred other users also mount.
Import, export and sanctions
EAR and ECCN classification of HPC hardware, GPUs and the software stack, and ITAR where it applies. Deemed export is the one that catches universities: giving a foreign national an account on a machine holding controlled technology is an export, and shared clusters are built to do exactly that. Technology control plans, restricted party and OFAC screening, Entity List constraints on accelerator procurement, and where the fundamental research exclusion genuinely applies rather than where people wish it did.
Clinical and pharmaceutical
HIPAA Security Rule on estates that are simultaneously research and clinical, GxP and 21 CFR Part 11 for electronic records and signatures, PCI DSS, and GDPR where a collaboration crosses into the EU. Audit evidence that can be produced on demand rather than reconstructed the week before an assessment.
Standards and control frameworks
Systems designed and operated to ISO/IEC 27001 information security controls, ISO/IEC 27017 and 27018 for cloud and personal data in cloud, ISO/IEC 20000 service management practice, and SOC 2 control objectives. Where an organization is pursuing certification, the work is the control implementation and the evidence that survives the audit.
What this looks like on a cluster
Compliance fails on shared HPC in predictable places: a scratch filesystem nobody scoped, an epilog that never deletes, a scheduler prolog that leaks a path, home directories mounted everywhere by default, node images drifting apart, and audit logging that stops at the login node. The useful work is closing those, then proving they are closed — not producing a policy document that describes a system nobody has actually configured.