Study guide

3.5 Secure Provisioning, Inventory, and Asset Management

CISSP Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: CISSP Orientation, CAT, and Official Source Control

1.1 Credential Scope, CISSP Mindset, and Search Language 1.2 Exam Outline Effective Date and Eight-Domain Map 1.3 CAT Format, 100-150 Items, and Forward-Only Rules 1.4 Passing Grade, Results, Feedback, and Retake Policy 1.5 Experience, Endorsement, and Associate of ISC2 Path 1.6 Pricing, AMF, CPE, and Maintenance Overview

2 Chapter 2: Security and Risk Management

2.1 Professional Ethics, CIA, and Security Governance 2.2 Policies, Standards, Procedures, Guidelines, and Control Ownership 2.3 Legal, Regulatory, Privacy, and Investigation Context 2.4 Risk Identification, Analysis, Treatment, and Reporting 2.5 Business Continuity, BIA, and Recovery Prioritization 2.6 Personnel Security, Training, Awareness, and Culture 2.7 Threat Modeling, Supply Chain Risk, and Third-Party Governance 2.8 Security and Risk Management Case Lab

3 Chapter 3: Asset Security and Data Lifecycle

3.1 Asset and Data Classification, Ownership, and Roles 3.2 Handling Requirements, Labeling, Privacy, and Cross-Border Data 3.3 Data States and Protection Methods: DLP, DRM, and CASB 3.4 Data Lifecycle, Retention, Remanence, and Destruction 3.5 Secure Provisioning, Inventory, and Asset Management 3.6 Asset Security Case Lab

4 Chapter 4: Security Architecture, Engineering, and Cryptography

4.1 Secure Design Principles and Security Models 4.2 Control Selection, System Security, and Architecture Risk 4.3 Cryptography Foundations: Symmetric, Asymmetric, Hashing, and PKI 4.4 Cryptographic Lifecycle, Key Management, and Attack Patterns 4.5 Cloud, Container, IoT, Edge, and Shared Responsibility Architecture 4.6 Physical Site, Facility, and Environmental Security 4.7 Information System Lifecycle Engineering and Retirement 4.8 Architecture and Engineering Case Lab

5 Chapter 5: Communication, Network Security, and Zero Trust

5.1 Network Architecture, OSI/TCP/IP, and Secure Design 5.2 Secure Protocols, Encryption in Transit, and Channel Protection 5.3 Segmentation, Microsegmentation, SDN, VPC, and Zero Trust 5.4 Wireless, Cellular, Remote Access, and Third-Party Connectivity 5.5 Network Components: NAC, IDS/IPS, Firewalls, and Endpoints 5.6 Monitoring, Observability, Capacity, and Resilient Communications 5.7 Communication and Network Security Case Lab

6 Chapter 6: Identity and Access Management

6.1 Identity Proofing, Authentication, Authorization, and Accountability 6.2 Access Control Models: RBAC, MAC, DAC, ABAC, and Risk-Based Access 6.3 Federation, SSO, MFA, Passwordless, and Session Management 6.4 Provisioning, Deprovisioning, JML, and Access Reviews 6.5 Service Accounts, Non-Human Identities, and Privilege Management 6.6 Physical, Logical, Cloud, and Hybrid Access Boundaries 6.7 IAM Case Lab

7 Chapter 7: Security Assessment, Testing, and Audit Strategy

7.1 Assessment, Test, and Audit Strategy Selection 7.2 Control Testing, Vulnerability Assessment, and Penetration Testing 7.3 Log Review, Code Review, Misuse Cases, and Compliance Checks 7.4 Security Process Data, KPIs, KRIs, and Reporting 7.5 Remediation, Exceptions, Risk Acceptance, and Evidence Quality 7.6 Security Assessment and Testing Case Lab

8 Chapter 8: Security Operations, Incident Response, and Resilience

8.1 Investigations, Evidence, Forensics, and Legal Readiness 8.2 Logging, Monitoring, SOC, and Alert Triage 8.3 Configuration, Change, Patch, and Vulnerability Operations 8.4 Incident Management, Containment, Eradication, and Recovery 8.5 Disaster Recovery, Backup, Availability, and Resilience 8.6 Physical Security Operations and Safety 8.7 Security Operations Case Lab

9 Chapter 9: Software Development Security and DevSecOps

9.1 Secure SDLC Governance and Requirements 9.2 Architecture, Threat Modeling, and Design Review 9.3 Secure Coding, Code Review, and Application Testing 9.4 CI/CD, Source Control, and Environment Separation 9.5 Software Supply Chain, Third-Party Components, and Deployment 9.6 DevSecOps Vulnerability Management and Release Risk 9.7 Software Development Security Case Lab

10 Chapter 10: Integrated CISSP Governance Scenario Labs

10.1 Enterprise Risk Committee Decision Lab 10.2 Cloud Migration Security Architecture Lab 10.3 Ransomware Incident and Business Continuity Lab 10.4 Identity Modernization and Zero Trust Lab 10.5 Third-Party Breach and Contract Governance Lab 10.6 Secure SDLC Transformation Lab 10.7 Full CISSP Manager Simulation

11 Chapter 11: Final Review, Endorsement, CPE, and Test-Day Strategy

11.1 Final 45-Day CISSP Study Plan 11.2 CAT Timing and Forward-Only Decision Workflow 11.3 Mixed-Domain Remediation and Manager Mindset Review 11.4 Test-Day Checklist and Pearson VUE Readiness 11.5 Endorsement, Associate Path, and Work Experience Documentation 11.6 CPE, AMF, and Three-Year Maintenance Plan 11.7 CISSP Final Mixed Review

3.5 Secure Provisioning, Inventory, and Asset Management

Key Takeaways Explain This Topic AI

An organization cannot protect assets it cannot identify, locate, classify, and assign to an accountable owner.

Secure provisioning establishes approved baselines before assets enter service, including identity, configuration, encryption, logging, and management controls.

Inventory must include hardware, software, cloud resources, SaaS applications, data stores, certificates, keys, service accounts, containers, and third-party dependencies where relevant.

Asset management supports vulnerability management, incident response, license compliance, data protection, financial control, and decommissioning.

Lifecycle governance should prevent orphaned systems, stale data, unmanaged accounts, and forgotten cloud resources from becoming hidden risk.

Last updated: May 2026

Inventory Is A Security Control

Asset inventory is often treated as administrative housekeeping, but it is a core security control. If an organization cannot identify a server, cloud bucket, SaaS tenant, endpoint, application, data repository, certificate, API key, container image, or vendor integration, it cannot reliably patch it, monitor it, classify its data, remove access, or destroy it at end of life. Unknown assets become unmanaged attack surface.

A mature inventory is not just a list of serial numbers. It links the asset to a business owner, custodian, location, classification, function, criticality, network zone, software stack, data type, dependency, support model, lifecycle state, and recovery requirement. The level of detail should match risk. A restricted-data platform needs richer records than a low-risk shared monitor, but both still need accountable handling.

Asset category Inventory attributes to capture Why it matters

Endpoint and mobile device User, owner group, management state, encryption, operating system, last check-in. Supports access control, patching, loss response, and remote wipe.

Server or workload Application, owner, environment, network zone, data classification, patch group. Supports vulnerability management and incident response.

Cloud resource Account, region, tags, owner, data classification, exposure, logging state. Prevents orphaned storage, public exposure, and cost drift.

SaaS application Business owner, users, data types, vendor, contract, SSO, retention. Supports privacy review, access recertification, and exit planning.

Data store Data owner, classification, retention, backup, legal hold capability. Connects asset management to data lifecycle governance.

Secret or certificate Owner, system dependency, rotation date, storage location, expiration. Prevents outages, compromise, and emergency overbroad access.

Secure provisioning is the controlled path by which assets enter service. A new laptop should receive an approved image, endpoint management, disk encryption, anti-malware or endpoint detection, configuration baseline, patch policy, user assignment, and asset record before use. A new server should receive hardened configuration, logging, monitoring, vulnerability scanning, backup classification, identity integration, and owner approval. A new cloud resource should be tagged, logged, network-scoped, encrypted, and policy-checked before production data arrives.

Provisioning should separate environments. Development, test, staging, and production assets have different risk profiles. Production data should not automatically flow to lower environments. Administrative access in development should not imply administrative access in production. Asset records should identify environment so scanning, logging, backup, and retention expectations are clear.

Configuration baselines support consistent protection. Baselines define required settings for operating systems, databases, network devices, containers, cloud services, and applications. They may include password or authentication policy, disabled services, logging, time synchronization, encryption, firewall rules, secure protocols, patch sources, endpoint protection, and remote access restrictions. Deviations should be documented as exceptions with owner approval and review dates.

Asset management connects to vulnerability management. A scanner may find a critical vulnerability on an IP address, but remediation depends on knowing who owns the system, whether it is internet-facing, what data it processes, what business function it supports, and which maintenance window is acceptable. Without ownership metadata, critical findings become orphan tickets. With good inventory, remediation can be prioritized by exposure, exploitability, and asset value.

Cloud and SaaS make inventory harder because teams can create assets quickly. Shadow IT may appear when business teams adopt SaaS tools without security review. Cloud resources may be created for a project and left running after the project ends. Containers and serverless functions may exist briefly but process sensitive data. Automated discovery, tagging policy, account governance, CASB discovery, procurement controls, and identity logs can help identify these assets.

Provisioning checklist:

Assign business owner, technical custodian, cost center, and support group.

Record classification, data types, criticality, environment, and approved purpose.

Apply secure baseline, hardening standard, and patch source.

Enforce identity integration, least privilege, and privileged access process.

Enable encryption, key ownership, logging, monitoring, and backup where required.

Register dependencies, certificates, secrets, service accounts, and vendor connections.

Confirm vulnerability scanning, configuration monitoring, and incident response contact.

Define review date, expected retirement date, and decommission procedure.

Decommissioning is part of secure provisioning because assets need a clean exit. Before a system is retired, owners should identify data to migrate, archive, delete, or preserve under hold. Custodians should remove network exposure, revoke accounts and keys, terminate vendor access, remove DNS and certificates, update documentation, sanitize media, and close monitoring. Finance and procurement may need to end licenses or contracts. A system that is powered off but still has active credentials, open firewall rules, or retained data remains a risk.

Scenario: an application team creates a temporary cloud database for a migration test. It uses production customer data, has no owner tag, and remains open to a broad network range. This is an asset management failure as much as a cloud configuration failure. A good program would require tagging, approved data use, network boundaries, encryption, logging, retention limit, and automatic review or expiration for temporary resources.

Scenario: a certificate expires on a customer portal and causes an outage. The security lesson is not only certificate renewal. Certificates and keys are assets with owners, dependencies, expiration dates, storage requirements, and rotation procedures. Inventory should support alerts before expiration and emergency contacts when renewal fails.

Scenario: a SaaS marketing tool was purchased on a credit card and contains customer emails. It bypassed privacy review, SSO, retention policy, and access recertification. CASB discovery or procurement monitoring may find it, but leadership still needs a process to onboard it securely, migrate data, restrict use, or retire it. Shadow IT is often a governance symptom, not just user misconduct.

The CISSP perspective is that asset management makes other controls possible. Incident responders need asset context. Privacy teams need data location. Vulnerability teams need owners. Business continuity planners need criticality. Auditors need evidence. Secure provisioning and inventory convert scattered technology into governed assets with accountable lifecycle states.