The Definitions Others Build On
ISO/IEC 27017, the CSA guidance, regulator circulars and most cloud contracts use NIST's service and deployment models. Getting the classification right is the first step in every cloud risk assessment.
NIST cloud computing security is a family of publications from the US National Institute of Standards and Technology. SP 800-145 defines cloud computing through five essential characteristics, three service models (SaaS, PaaS, IaaS) and four deployment models. SP 500-292 gives the reference architecture with five actors. SP 800-144 sets out security and privacy guidance for public cloud, SP 800-210 covers access control, and later documents address microservices, service mesh and Zero Trust in cloud-native systems.
NIST's cloud guidance is a set of documents rather than one standard. Select a publication to see what it covers and how XcellHost puts it to work.
The short definition the whole industry quotes: five essential characteristics (on-demand self-service, broad network access, resource pooling, rapid elasticity, measured service), three service models and four deployment models (private, community, public, hybrid).
Names the five actors in any cloud arrangement, Cloud Consumer, Cloud Provider, Cloud Auditor, Cloud Broker and Cloud Carrier, and the activities each performs, giving contracts and risk assessments a shared vocabulary.
Guidance on the security and privacy issues of outsourcing data and applications to public cloud: governance, compliance, trust, architecture, identity, software isolation, data protection, availability and incident response.
A plain explanation of what each service model means for security, performance and reliability, with recommendations on when cloud is and is not the right choice for a given workload.
Published July 2020, it sets out access control guidance for IaaS, PaaS and SaaS, noting that controls for lower service models also apply to higher ones, and covers RBAC, ABAC and policy enforcement in cloud.
Five publications on securing microservices-based applications, using service mesh for authentication and attribute-based access, implementing DevSecOps, and integrating software supply chain security in CI/CD pipelines.
Applies Zero Trust architecture to access control in cloud-native applications running across multi-cloud environments, defining identity-tier and network-tier policies enforced close to each service rather than at a perimeter.
ISO/IEC 27017, the CSA guidance, regulator circulars and most cloud contracts use NIST's service and deployment models. Getting the classification right is the first step in every cloud risk assessment.
The five actors and the service-model split make shared responsibility explicit, so providers, brokers and your own team cannot each assume the other is handling a control.
SEBI's cloud framework and RBI's outsourcing directions discuss IaaS, PaaS and SaaS and deployment models in NIST's terms, so NIST-based classification feeds straight into regulatory filings.
Later publications cover microservices, service mesh, DevSecOps and Zero Trust, giving engineering teams a reference for securing Kubernetes and API-driven systems, not only virtual machines.
NIST publications bind US federal agencies, not Indian organisations. Their influence in India is through vocabulary: regulators, MeitY and contracts describe cloud using NIST's models, so an assessment built on them translates directly into Indian compliance work.
| Aspect | NIST cloud publications | CSA Security Guidance v5 |
|---|---|---|
| Publisher | US government standards body | Industry non-profit (Cloud Security Alliance) |
| Form | Several special publications since 2011 | One document in twelve domains |
| Strength | Definitions, architecture and access control | End-to-end practitioner guidance |
| Assurance link | FedRAMP via SP 800-53 controls | CCM and STAR Registry |
One team for assessment, remediation, 24×7 operations and audit evidence — run from Mumbai by a company certified to ISO/IEC 27001 and ISO/IEC 20000-1.
Talk to our security team →Catalogue cloud services by service and deployment model and name the actors for each.
Weeks 1–2Review each service against SP 800-144 concern areas and access control guidance.
Weeks 3–6Fix identity, isolation, data protection and recovery gaps with a chosen control catalogue.
Months 2–5Monitor cloud and cloud-native workloads continuously and reassess as services change.
OngoingXcellHost is certified to ISO/IEC 27001 and ISO/IEC 20000-1 and has protected Indian businesses since 1999 — so your NIST cloud guidance work is run by a team that lives these controls every day.
Vendor-neutral cloud security architecture and practice
Cloud SecurityCloud-specific security controls and assessment questions
Cloud SecuritySecurity and privacy control catalogue
Core Cybersecurity & RiskZero Trust architecture
Zero TrustCloud security controls for customers and providers
Cloud SecuritySearch the complete master list across 12 domains.
Framework explorer