Page 137 of the DSE IT knowledge center, with source-backed guidance and practical next steps.
Production-minded guidance for endpoints, servers, updates, cloud services, administration, and supportable operations.
Platform firmware is needed to boot and operate a system. Procurement and operations should address unauthorized change prevention, detection, supported recovery, and evidence of restoration.
Read the guide
NIST's minimum verification guidance describes multiple complementary techniques. Select, scope, and retain evidence from the techniques that address design, code, dependencies, and running behavior.
Read the checklist
IaaS, PaaS, and SaaS expose different components and administrative boundaries. Trace every important access decision to the identity, policy, service layer, owner, and evidence source that enforce it.
Read the guide
OAuth authorization-code flows need exact redirect URI matching and correctly enforced PKCE. Treat both as testable protocol controls across every client and authorization server.
Read the guide
A CI/CD pipeline carries source through build, test, package, and deployment operations. Protect each transition, identity, dependency, artifact, approval, and evidence record in the path.
Read the playbook
Microservices depend on APIs and shared architectural services. Define how each service authenticates, authorizes, discovers peers, protects traffic, limits load, records events, and fails.
Read the guide
A proxy-based service mesh can centralize important service-to-service functions. Govern its identity, trust, policy, telemetry, availability, bypass paths, and change control as production security infrastructure.
Read the checklist
Block, file, object, virtualized, and cloud storage bring distinct control and recovery paths. Inventory data flows, management planes, identities, isolation, protection, restoration, and encryption as one system.
Read the guide
VM traffic may traverse virtual switches, overlays, host paths, and distributed controls. Design segmentation, redundancy, traffic enforcement, and monitoring against the real path.
Read the checklist
Cryptography depends on keying material that must be created, protected, used, rotated, recovered, archived, revoked, and destroyed according to its purpose and risk.
Read the guide