# Cloud Contractors Embed Identity Security

A Security Boulevard article argues that cloud identity and access management should be designed alongside infrastructure rather than treated as a separate layer. It highlights least-privilege access, short-lived workload identities, and federated authentication as ways to reduce persistent access and stored-secret risks, and connects these practices to NIST zero-trust guidance. The article identifies no government solicitation, contract, funding amount, or procurement deadline; its relevance is to contractors shaping cloud modernization and security solutions.

- Contractors developing cloud proposals or architectures can address identity controls as part of the infrastructure design, including least privilege, short-lived workload identities, and federated authentication.
- Procurement teams evaluating cloud security solutions can use these practices as design considerations when assessing how offerings reduce persistent access and stored-secret exposure.
- The article provides a technical trend rather than a specific procurement opportunity; it does not identify a solicitation or mandatory new compliance requirement.

**Jurisdictions:** federal
**Industries:** Information Technology
**Topics:** Cybersecurity, Cloud Services
**Published:** November 12, 2026

### Government Entities
- National Institute of Standards and Technology (NIST)

### Sources
- [Why Cloud Security Breaks When Identity Is Treated as a Separate Layer - Security Boulevard](https://securityboulevard.com/2026/11/why-cloud-security-breaks-when-identity-is-treated-as-a-separate-layer) - Security Boulevard