CCSP 2026 Flashcards: August Exam Outline Review
A 340-card, six-domain review for the CCSP outline effective August 1, 2026, including cloud AI/ML, dataset, model, and LLM application security.
Over dit deck
This 340-card deck reviews all six domains in the English CCSP exam outline effective August 1, 2026: Cloud Concepts, Architecture and Design; Cloud Data Security; Cloud Platform and Infrastructure Security; Cloud Application Security; Cloud Security Operations; and Legal, Risk and Compliance.
What you'll retrieve
- Separate cloud service, deployment, architecture, data, identity, assurance, operations, risk, privacy, audit, and contract concepts that are easy to confuse.
- Map customer, provider, security, data, privacy, audit, incident, and vendor roles to their primary responsibility boundary.
- Choose a practical control for a short cloud scenario, then state the risk or failure mode it chiefly addresses.
- Make focused architecture, lifecycle, recovery, testing, monitoring, service-management, and outsourcing decisions from stated requirements, including service-level management, availability management, Quality Assurance, audit planning, and provider-risk assessment.
- Recognize revised AI and ML concerns across cloud threat detection, dataset and model privacy, data and model poisoning, provenance, model inversion and extraction, human oversight, and LLM application risks.
Selected reverse and contrast prompts are included where they improve retrieval, such as elasticity versus scalability, portability versus interoperability, RTO versus RPO, hashing versus encryption, controller versus processor, IDS versus IPS, and incident versus problem management. The deck does not mechanically reverse every fact.
Exam-format multiple choice, memorized answer patterns, dumps, vendor-console trivia, copied course wording, and legal advice are excluded. The cards do not reproduce real or simulated ISC2 exam items. They also stay outside deep cryptographic mathematics, product-specific implementation recipes, and specialist AI research that does not change a cloud-security control decision.
The order is deliberate. Each domain advances through short, coherent topic tracks from prerequisite concepts and responsibility boundaries to controls and applied decisions. The final 340-card sequence was reviewed as one topic-progressive order, with identified forward, reverse, near-duplicate, and answer-cue variants deliberately separated to reduce short-range cueing. Its topic tracks are interleaved so the sequence does not become a concept run followed by role, control, and decision runs. Domain 1 establishes cloud characteristics, actors, service and deployment models, secure design, provider evidence, and AI governance. Domain 2 follows data through flows, storage, protection, discovery, classification, rights, retention, evidence, and dataset or model risk. Domains 3 and 4 apply those foundations to infrastructure, resilience, secure development, software supply chains, APIs, LLM applications, and IAM. Domains 5 and 6 close with secure operations, monitoring, incident response, forensics, law, privacy, audit, enterprise risk, and contracts.
Reviewed for the CCSP outline effective August 1, 2026. Coverage was bounded by the official English exam outline PDF, the ISC2 outline page, and ISC2's June 2026 revision notice. NIST and OWASP primary publications were used to check standard control and AI/application-security distinctions.
Every prompt, answer, explanation, sequence choice, and metadata field was independently written from common cloud-security knowledge. The CC0 label applies to that original expression, organization, metadata, and generated cover to the extent applicable rights exist; it does not claim ownership of facts, standards, certification marks, or third-party material.
This is an independently authored, unofficial educational deck by Flashcards Open Source App. It is not affiliated with, sponsored by, or endorsed by ISC2. CCSP is a registered certification mark of ISC2. No ISC2 exam questions, answer keys, course text, outline prose, logos, badges, or trade dress were copied.
Kaarten in dit deck
Kaart 1
Vraag
What makes a computing environment a cloud rather than ordinary hosted infrastructure?
Antwoord
It provides shared, configurable resources on demand with rapid provisioning and minimal provider interaction. A hosted server without those operating characteristics is not automatically a cloud.
Kaart 2
Vraag
What is the security significance of broad network access?
Antwoord
Services are reachable through standard network mechanisms from varied clients. That reach increases the need for strong identity, transport protection, and endpoint-aware access.
Kaart 3
Vraag
How do resource pooling and multi-tenancy differ?
Antwoord
Resource pooling dynamically assigns shared capacity; multi-tenancy lets multiple customers use that shared environment with logical isolation. Pooling is the allocation model, while multi-tenancy is the customer-sharing model.
Kaart 4
Vraag
What separates elasticity from scalability?
Antwoord
Elasticity adjusts capacity with demand; scalability is the ability to handle growth by adding or changing capacity. Elasticity stresses timely adjustment, often in both directions.
Kaart 5
Vraag
What does measured service provide?
Antwoord
Metered visibility into resource consumption. The measurements support billing, capacity decisions, anomaly detection, and accountability.
Kaart 6
Vraag
What does on-demand self-service let a cloud customer do?
Antwoord
Provision needed capabilities without waiting for a provider employee. Policy and quota controls can still constrain the request.
Kaart 7
Vraag
What does virtualization contribute to cloud computing?
Antwoord
It abstracts physical resources into isolated, assignable compute, storage, or network units. Orchestration turns those units into an on-demand service.
Kaart 8
Vraag
What remains the cloud customer's responsibility in every service category?
Antwoord
Governing its identities, data, configuration choices, and lawful use. The exact technical boundary changes, but accountability does not vanish when infrastructure is outsourced.
Kaart 9
Vraag
What does a cloud service broker add?
Antwoord
Intermediation, aggregation, or management across cloud services. A broker may compare, combine, or govern services without owning their underlying infrastructure.
Kaart 10
Vraag
What is a regulator's cloud-security role?
Antwoord
Set or enforce legal and regulatory obligations that apply to the service and its data. The customer must map those duties into provider selection, controls, and evidence.
Kaart 11
Vraag
What is the cloud service provider's core responsibility?
Antwoord
Deliver the contracted cloud capabilities and secure the layers assigned to it. The service model and contract define the boundary.
Kaart 12
Vraag
What is orchestration in a cloud environment?
Antwoord
Coordinated automation of provisioning, configuration, scaling, and lifecycle actions across resources. It applies policy consistently across many components.
Kaart 13
Vraag
What capability does SaaS give the customer?
Antwoord
Use of a provider-run application. The customer mainly manages users, data, and allowed configuration rather than the platform beneath it.
Kaart 14
Vraag
Which four deployment models does NIST SP 800-145 define?
Antwoord
Public, private, community, and hybrid cloud. Multi-cloud describes using more than one cloud provider or service environment; it is distinct from NIST's canonical four-model taxonomy.
Kaart 15
Vraag
How do portability and interoperability differ?
Antwoord
Portability moves a workload or data between environments; interoperability lets different environments exchange and use information or services. One reduces switching friction, while the other supports cooperation.
Kaart 16
Vraag
What does a cloud service partner do?
Antwoord
Supports or enhances cloud service delivery, use, or assurance. Examples include auditors, integrators, and developers acting beside the customer and provider.
Kaart 17
Vraag
Who controls user entitlements inside a SaaS tenant?
Antwoord
The customer organization. The provider supplies the application and access mechanisms, but the customer decides which of its users need which privileges.
Kaart 18
Vraag
When is hybrid cloud a better description than multi-cloud?
Antwoord
When the architecture deliberately combines distinct private and public environments. Multi-cloud focuses on using multiple cloud services or providers and may contain no private cloud.
Kaart 19
Vraag
What problem does confidential computing address?
Antwoord
Protection of data while it is being processed. Hardware-backed trusted execution environments reduce exposure to the host or platform layer, but do not replace application controls.
Kaart 20
Vraag
When does blockchain add useful assurance to a cloud workflow?
Antwoord
When multiple parties need a shared, tamper-evident record without relying on one writer. It does not make source data true, private, lawful, or immune to key and smart-contract failures.
Kaart 21
Vraag
When does edge computing improve resilience but complicate security?
Antwoord
When local processing reduces central latency or dependency while distributing data, software, and physical exposure. The decision needs remote attestation, patching, inventory, and failure handling.
Kaart 22
Vraag
What does reversibility require in a cloud design?
Antwoord
A practical way to exit or change providers while recovering data, configurations, dependencies, and needed evidence. A theoretical export button is not enough if the result cannot be used elsewhere.
Kaart 23
Vraag
What is the first security question before connecting IoT devices to a cloud service?
Antwoord
Can each device be uniquely identified, updated, constrained, and monitored throughout its lifecycle? Cheap connectivity does not offset unmanaged device risk.
Kaart 24
Vraag
What capability does PaaS give the customer?
Antwoord
Deployment of customer applications onto a provider-managed platform. The provider runs the underlying infrastructure and runtime, while the customer secures code, data, and configuration.
Kaart 25
Vraag
What is a practical cloud decision for quantum-related cryptographic risk today?
Antwoord
Inventory cryptographic dependencies and design for algorithm agility. Replace algorithms according to authoritative migration guidance rather than adopting unreviewed schemes.
Kaart 26
Vraag
Which SLA measure is useful only when paired with a clear measurement method and remedy?
Antwoord
Any availability or performance target. Define the service boundary, observation window, exclusions, data source, notification, and remedy before treating the number as assurance.
Kaart 27
Vraag
How should a team use a Well-Architected pattern, SANS security principles, or CSA enterprise architecture?
Antwoord
As structured design input mapped to the workload's risks, responsibilities, and evidence. A named framework guides decisions but does not prove that the resulting architecture is secure.
Kaart 28
Vraag
What does a FIPS 140 validation establish?
Antwoord
That a named cryptographic module was validated against the stated standard and boundary. It does not prove the surrounding application uses the module safely.
Kaart 29
Vraag
Who normally patches the managed runtime in PaaS?
Antwoord
The cloud provider. The customer still owns secure application code, dependencies it supplies, data, identities, and configuration.
Kaart 30
Vraag
Who should approve a cloud data classification?
Antwoord
The accountable data owner. Security and privacy teams advise, while custodians implement the handling controls.
Kaart 31
Vraag
What should the cloud architect own in secure design?
Antwoord
The documented trust boundaries, security requirements, resilience choices, and responsibility mapping. Operations and product teams then implement and test those decisions.
Kaart 32
Vraag
What does DevSecOps change about security ownership?
Antwoord
It makes security a shared, automated part of delivery rather than a final external gate. Product teams still need independent challenge for high-risk decisions.
Kaart 33
Vraag
Which controls reduce container escape impact?
Antwoord
Hardened runtimes, minimal privileges, trusted images, isolation boundaries, and prompt patching. Treat a container as a process boundary, not automatically as a security boundary equal to a separate host.
Kaart 34
Vraag
Who should own a cloud service's business recovery requirements?
Antwoord
The business or service owner. Technical teams translate the owner's impact tolerance into RTO, RPO, architecture, and tests.
Kaart 35
Vraag
What capability does IaaS give the customer?
Antwoord
Provisioning of fundamental compute, storage, and network resources. The customer usually controls operating systems, workloads, and many network settings.
Kaart 36
Vraag
Which key-management design limits a cloud provider compromise from exposing customer data?
Antwoord
Separate data from independently controlled encryption keys where the threat model requires it. Access policy, rotation, backup, and recovery for those keys matter as much as their location.
Kaart 37
Vraag
What is the safer identity pattern for a cloud workload?
Antwoord
A short-lived, narrowly scoped workload identity. It avoids embedded long-lived credentials and supports rotation and traceability.
Kaart 38
Vraag
When can cryptographic erase sanitize cloud data?
Antwoord
When destroying the correct encryption key makes all protected copies computationally unreadable and the encryption implementation is trustworthy. Key copies, snapshots, and replicas must be in scope.
Kaart 39
Vraag
What is the first network control for limiting east-west movement between cloud workloads?
Antwoord
Explicit segmentation with deny-by-default rules. Identity-aware policy and traffic telemetry strengthen the boundary; geofencing can add a location condition but cannot replace it.
Kaart 40
Vraag
Who normally patches a guest operating system in IaaS?
Antwoord
The cloud customer. The provider secures the underlying facilities and virtualization layer, while the customer manages the guest unless a separate managed service changes that boundary.
Kaart 41
Vraag
What is the most important permission control for a serverless function?
Antwoord
A dedicated least-privilege execution identity. Also restrict triggers, secrets, outbound access, and runtime duration; ephemeral execution does not erase external logs, queues, or data.
Kaart 42
Vraag
How does immutable infrastructure reduce configuration drift?
Antwoord
Replace changed instances from a controlled image instead of repairing them in place. The image pipeline, secrets, and state stores still need protection.
Kaart 43
Vraag
What turns a security baseline into an operating control?
Antwoord
Automated assessment plus timely remediation of deviations. A baseline document alone does not prevent drift.
Kaart 44
Vraag
What control keeps protection aligned as cloud data moves through its lifecycle?
Antwoord
Lifecycle-aware policy tied to classification and ownership. Access, encryption, retention, monitoring, and disposal should change with the data's state and purpose.
Kaart 45
Vraag
What makes a cloud recovery plan credible?
Antwoord
Regular restore, failover, dependency, and failback tests against business targets. A provider's availability claim does not prove the customer's service can recover.
Kaart 46
Vraag
What evidence should be checked first when evaluating a cloud provider?
Antwoord
Evidence mapped to the organization's own requirements and risk criteria. Certifications help only when their scope, period, system, and exceptions cover the intended service.
Kaart 47
Vraag
What should drive a cloud BC/DR design before products are selected?
Antwoord
A business impact analysis. It identifies critical services, dependencies, impact over time, and acceptable recovery targets.
Kaart 48
Vraag
Who is accountable for approving an AI model's intended cloud use?
Antwoord
The designated AI or business system owner. Model builders provide evidence, while risk, security, privacy, and legal roles challenge the use against policy.
Kaart 49
Vraag
What should be tested before accepting a provider's portability claim?
Antwoord
Export the data and configuration, rebuild elsewhere, and measure missing features, time, cost, and dependencies. Contract wording alone cannot prove reversibility.
Kaart 50
Vraag
What control most directly reduces hypervisor compromise risk for a customer?
Antwoord
Use a provider with strong isolation assurance, rapid patching, and evidence for the virtualization layer. The customer cannot harden a provider-managed hypervisor directly.
Kaart 51
Vraag
How should CBA and ROI inform a cloud recovery design after the BIA?
Antwoord
CBA compares each option's lifecycle cost with expected benefit; ROI expresses the expected return relative to investment. Neither overrides mandatory duties or the BIA's approved impact tolerance.
Kaart 52
Vraag
What control helps validate training or detection data before AI use?
Antwoord
Provenance, integrity checks, schema checks, and approval for the intended source. Statistical anomaly checks can add evidence but should not replace ownership.
Kaart 53
Vraag
What is the human reviewer's role in AI-assisted security operations?
Antwoord
Validate consequential findings and actions before relying on them. Automation can rank and enrich signals, but the accountable human handles ambiguity and impact.
Kaart 54
Vraag
Why read an assurance report's scope before relying on its conclusion?
Antwoord
The report may exclude the exact service, region, control, subservice, or period you need. Assurance cannot be extended beyond its stated boundary.
Kaart 55
Vraag
Which controls make model extraction harder at a cloud API?
Antwoord
Strong access control, rate and budget limits, query monitoring, response minimization, and abuse detection. No single control removes the risk from a publicly queryable model.
Kaart 56
Vraag
Why is high predictive accuracy insufficient for a cloud data-science or AI model?
Antwoord
The use can still create unacceptable legal, privacy, fairness, security, safety, or operational risk. Accuracy is one quality measure, not automatic authorization to deploy.
Kaart 57
Vraag
How should SOAR handle a high-impact containment action?
Antwoord
Use explicit authorization, bounded playbooks, and human approval when impact or uncertainty is high. Automation should be reversible and fully logged.
Kaart 58
Vraag
When is Common Criteria evidence relevant to provider evaluation?
Antwoord
When a specific evaluated product and assurance target match the component and threat being assessed. It does not certify an entire cloud service by association.
Kaart 59
Vraag
Which data lifecycle sequence is useful for cloud control planning?
Antwoord
Create, store, use, share, archive, and destroy. Real data may move between phases, but each transition needs an owner and handling rule.
Kaart 60
Vraag
What is data dispersion in cloud computing?
Antwoord
The distribution of data and copies across systems, regions, media, services, and providers. Replicas, caches, logs, snapshots, and backups all expand the control boundary.
Kaart 61
Vraag
What does a cloud data flow describe?
Antwoord
Where data originates, moves, is transformed, is stored, and exits. A useful flow also names trust boundaries, actors, purposes, and protections.
Kaart 62
Vraag
How do object and volume storage differ?
Antwoord
Object storage addresses data as objects with metadata; volume storage presents block-like storage to a host. Their access paths, sharing models, snapshots, and permission risks differ.
Kaart 63
Vraag
How does ephemeral storage differ from long-term storage?
Antwoord
Ephemeral storage is tied to a short-lived workload or execution; long-term storage is designed to persist independently. Ephemeral does not mean automatically sanitized.
Kaart 64
Vraag
What is raw data storage?
Antwoord
Storage of collected data before full cleaning, transformation, or enrichment. Its broad content and uncertain quality make isolation, discovery, provenance, and access control especially important.
Kaart 65
Vraag
What makes a data-flow map useful for control design?
Antwoord
It names sources, destinations, transformations, actors, purposes, trust boundaries, and protections. Update it when architecture or processing changes.
Kaart 66
Vraag
What should decide whether data may move to another cloud region?
Antwoord
Classification, purpose, residency and transfer rules, contract terms, threat model, and required controls. Region availability alone is not authorization.
Kaart 67
Vraag
Which storage type fits immutable, widely shared blobs better than a mounted transactional filesystem?
Antwoord
Object storage. Use volume storage when the workload needs block-style filesystem or database access semantics.
Kaart 68
Vraag
A short-lived AI training node is terminated. Why can data risk remain?
Antwoord
Ephemeral compute can leave snapshots, caches, logs, attached volumes, or provider-level remnants. Verify the full storage and key lifecycle, not only instance deletion.
Kaart 69
Vraag
What control exposes unknown cloud data stores before they bypass policy?
Antwoord
Continuous asset and data discovery across accounts, regions, services, and shadow paths. Findings need ownership and remediation, not just inventory.
Kaart 70
Vraag
What security property does encryption primarily provide?
Antwoord
Confidentiality against parties without the key. Integrity and authenticity require an appropriate authenticated mode or separate mechanism.
Kaart 71
Vraag
What does tokenization do?
Antwoord
Replaces sensitive data with a non-sensitive token whose mapping is protected separately. The token can preserve application format while reducing where original data appears.
Kaart 72
Vraag
How do structured, semi-structured, and unstructured data differ?
Antwoord
Structured data follows a fixed schema, semi-structured data carries flexible labels or structure, and unstructured data lacks a consistent field model. Discovery needs techniques suited to each form.
Kaart 73
Vraag
What is data masking?
Antwoord
A transformation that hides selected data while preserving a usable shape or view. Reversible or weak masking is not anonymization.
Kaart 74
Vraag
What does Data Loss Prevention monitor or restrict?
Antwoord
Sensitive-data movement or use across selected channels. DLP depends on discovery, classification, context, coverage, and tuned response.
Kaart 75
Vraag
What security property does a cryptographic hash support?
Antwoord
Integrity by detecting change. A plain hash does not hide the input, prove who created it, or prevent guessing of low-entropy values.
Kaart 76
Vraag
What does Information Rights Management add beyond storage permissions?
Antwoord
Persistent usage rules attached to protected content, such as view, print, copy, expiry, or revocation. Enforcement still depends on trusted identities, clients, and key services.
Kaart 77
Vraag
Where should application secrets be kept?
Antwoord
In a managed secret store with narrow access, audit logs, rotation, and short-lived retrieval. Source code, images, and general configuration files are poor secret stores.
Kaart 78
Vraag
What is anonymization trying to achieve?
Antwoord
Make data no longer reasonably linkable to an identifiable person. Re-identification risk must be assessed against auxiliary data and the release context.
Kaart 79
Vraag
Why separate key-custodian duties from data administration?
Antwoord
To reduce the chance that one person can both reach ciphertext and independently unlock it. Separation of duties should also cover recovery and emergency access.
Kaart 80
Vraag
What control reduces dependence on provider-held encryption keys?
Antwoord
Customer-controlled keys with independent policy and lifecycle management. The choice adds recovery, availability, rotation, and administrator risks that must be designed explicitly.
Kaart 81
Vraag
How can tokenization reduce exposure in an application database?
Antwoord
Store tokens in routine workflows and isolate the token vault or mapping service. Access to detokenization should be rarer and more tightly logged.
Kaart 82
Vraag
How can a hash support evidence integrity?
Antwoord
Record a strong hash at acquisition and verify it after each transfer or analysis step. Chain-of-custody records explain who handled the evidence and why.
Kaart 83
Vraag
What is the safer source for non-production test data?
Antwoord
Synthetic or appropriately transformed data that meets the test need without exposing production identities. Validate re-identification risk before release.
Kaart 84
Vraag
What makes DLP enforcement practical instead of noisy?
Antwoord
Accurate discovery and classification, contextual rules, staged response, tuned exceptions, and incident ownership. Blocking every pattern match can disrupt work without reducing real leakage.
Kaart 85
Vraag
What enables IRM revocation after a file leaves its original repository?
Antwoord
A trusted client that checks current rights and can no longer obtain the needed key or license. Offline copies and screenshots remain boundary cases.
Kaart 86
Vraag
How should cloud data discovery handle false positives?
Antwoord
Route uncertain matches for risk-based validation and tune detection with evidence. Silently discarding them hides coverage gaps; blocking them all creates operational failure.
Kaart 87
Vraag
What keeps certificates trustworthy after issuance?
Antwoord
Inventory, protected private keys, renewal, revocation, validation, and monitored expiry. Issuing a certificate is only the start of its lifecycle.
Kaart 88
Vraag
What is envelope encryption?
Antwoord
Encrypt data with a data-encryption key, then protect that key with a separate key-encryption key. Rotating or rewrapping the key-encryption key can protect existing data-encryption keys without re-encrypting payload data; replacing a data-encryption key may require payload re-encryption.
Kaart 89
Vraag
What is data classification?
Antwoord
Assignment of a sensitivity or business category that drives handling requirements. The category should reflect impact, law, contract, and business need.
Kaart 90
Vraag
When is tokenization preferable to ordinary encryption?
Antwoord
When workflows can use a surrogate while original values stay in a tightly isolated mapping service. Encryption is better when authorized systems must recover data directly with keys.
Kaart 91
Vraag
Should a password be encrypted or hashed for verification?
Antwoord
Hash it with a password-specific salted, slow derivation function. Reversible encryption creates unnecessary recovery of the original password.
Kaart 92
Vraag
When is masking insufficient for a public dataset release?
Antwoord
When remaining fields or external data can reasonably re-identify people. Public release needs a defensible anonymization assessment, not cosmetic redaction.
Kaart 93
Vraag
Why should DLP not be the only control against cloud exfiltration?
Antwoord
It sees only covered channels and recognized content. Least privilege, segmentation, egress control, encryption, monitoring, and response reduce gaps.
Kaart 94
Vraag
When is IRM more useful than a repository access control list?
Antwoord
When usage restrictions must follow a file beyond the original repository. If data never leaves a controlled service, native authorization may be simpler and stronger.
Kaart 95
Vraag
Why perform discovery before broad classification enforcement?
Antwoord
You need to know what data exists and where it lives before applying reliable labels and controls. Enforcement on an incomplete inventory leaves blind spots.
Kaart 96
Vraag
What should trigger data reclassification?
Antwoord
A change in content, use, law, contract, business impact, aggregation, or identifiability. Review should also occur on a defined schedule.
Kaart 97
Vraag
Why rotate encryption keys?
Antwoord
To limit exposure, meet policy, and replace keys after age, role, algorithm, or compromise changes. Rotation must preserve authorized access to older data until it is safely reprotected or retired.
Kaart 98
Vraag
Who sets a cloud dataset's business classification?
Antwoord
The accountable data owner. Automated tools can propose labels, but the owner resolves business context and exceptions.
Kaart 99
Vraag
How does a data label differ from a classification policy?
Antwoord
The label marks a specific asset; the policy defines what the category means and how it must be handled. Labels without enforcement are only metadata.
Kaart 100
Vraag
What is a data steward responsible for?
Antwoord
Day-to-day quality, definition, and policy consistency for data. A steward supports the owner but does not replace the owner's accountability.
Kaart 101
Vraag
How do retention and archiving differ?
Antwoord
Retention states how long data must or may be kept; archiving moves data into a managed long-term state. Archived data remains subject to access, integrity, discovery, and deletion rules.
Kaart 102
Vraag
What does a data controller decide?
Antwoord
The purposes and essential means of processing personal data. The exact legal definition depends on the applicable law.
Kaart 103
Vraag
When should a derived dataset inherit its source classification?
Antwoord
By default, until an accountable owner proves the transformation changed sensitivity. Aggregation can reduce or increase risk depending on content and linkability.
Kaart 104
Vraag
How should classification labels affect cloud controls?
Antwoord
Drive access, encryption, sharing, location, retention, monitoring, and deletion policy. Enforcement should follow the label across supported copies and transformations.
Kaart 105
Vraag
What does a legal hold do?
Antwoord
Suspends normal deletion for information relevant to a legal or regulatory matter. It preserves authorized access and evidence until the hold is released.
Kaart 106
Vraag
What should a privacy role contribute to cloud data design?
Antwoord
Purpose, minimization, transparency, rights, transfer, retention, and impact requirements. Security protects data, while privacy also asks whether processing should occur and under what conditions.
Kaart 107
Vraag
What control turns a retention schedule into repeatable cloud behavior?
Antwoord
Policy-driven lifecycle automation with holds, approvals, exceptions, and audit evidence. Automation must cover replicas and backups where the platform supports it.
Kaart 108
Vraag
What is a data custodian responsible for?
Antwoord
Implementing and operating the technical handling controls. Storage, backup, access, logging, and deletion are typical custody duties.
Kaart 109
Vraag
Who should own the retention schedule?
Antwoord
The records or information-governance function with legal and business input. Technology teams implement the approved schedule and evidence.
Kaart 110
Vraag
What does a data processor do?
Antwoord
Processes personal data for a controller under documented instructions. Using the data for its own new purpose may change the role and obligations.
Kaart 111
Vraag
What proves a cloud deletion request was completed responsibly?
Antwoord
Provider and customer evidence tied to the asset, method, scope, time, and remaining copies. A successful API response alone may not cover backups, replicas, or exported data.
Kaart 112
Vraag
Which controls protect a long-term cloud archive?
Antwoord
Restricted access, durable integrity checks, format and key preservation, redundancy, retention policy, and tested retrieval. An archive that cannot be read or trusted has failed its purpose.
Kaart 113
Vraag
Who should approve a training dataset and model version for production?
Antwoord
The accountable model or system owner using evidence from data, security, privacy, and validation roles. Approval must bind the exact versions and intended use.
Kaart 114
Vraag
Which event fields most often establish accountability for cloud data access?
Antwoord
Trusted identity, action, target, result, timestamp, source context, and relevant network or location data. Collect only attributes needed for the security, legal, and privacy purpose.
Kaart 115
Vraag
Why synchronize clocks across cloud evidence sources?
Antwoord
To correlate events into a defensible timeline. Record time source, zone, drift, and collection context when precision matters.
Kaart 116
Vraag
Which risk is present when model outputs reveal features of sensitive training records?
Antwoord
Model inversion or related privacy inference. Data minimization, privacy testing, output controls, and access limits reduce exposure.
Kaart 117
Vraag
Who authorizes and scopes a legal hold?
Antwoord
An authorized legal or records function. Cloud administrators implement it without deciding the legal scope themselves.
Kaart 118
Vraag
What must AI dataset validation check besides file integrity?
Antwoord
Source authority, consent or permitted use, representativeness, quality, labeling, poisoning indicators, and intended-use fit. A matching checksum only proves the bytes did not change after that checkpoint.
Kaart 119
Vraag
Why is an archive not a substitute for a recovery backup?
Antwoord
An archive optimizes long-term preservation and retrieval; a backup supports restoration after loss or corruption. One system can sometimes serve both only if it meets both control sets and tests.
Kaart 120
Vraag
What protects AI dataset and model provenance?
Antwoord
Versioned inventories, signed or hashed artifacts, controlled pipelines, approval records, and lineage from source to deployment. Bind validation results to the exact artifact versions.
Kaart 121
Vraag
Which context should be omitted from a data event log?
Antwoord
Data that is unnecessary for the defined security, accountability, or legal purpose. More logging can create privacy, cost, and breach risk without improving evidence.
Kaart 122
Vraag
What happens when a valid legal hold conflicts with scheduled deletion?
Antwoord
The authorized hold suspends deletion for the in-scope data. Keep access limited, document the exception, and resume policy when the hold is released.
Kaart 123
Vraag
What adds non-repudiation evidence beyond a plain event log?
Antwoord
Strong identity binding, protected timestamps, integrity controls, and controlled custody. The strength depends on the whole evidence process, not a single hash field.
Kaart 124
Vraag
What privacy question does a membership-inference attack answer?
Antwoord
Whether a particular record was likely part of a model's training data. Limit exposed confidence, query abuse, overfitting, and unnecessary sensitive training data.
Kaart 125
Vraag
What is the clearest sign that training-data poisoning controls failed?
Antwoord
Untrusted or manipulated examples changed model behavior or inserted a hidden trigger. Investigate provenance, pipeline access, validation, and the exact affected versions.
Kaart 126
Vraag
What is the strongest first step when an AI use case asks for every available customer field?
Antwoord
Reduce collection to data necessary for the approved purpose. Minimization lowers privacy, poisoning, access, retention, and breach exposure before technical controls are added.
Kaart 127
Vraag
What is the cloud network team's primary security role?
Antwoord
Implement approved segmentation, routing, edge protection, secure connectivity, and network telemetry. Application teams still define workload access needs.
Kaart 128
Vraag
Which layers make up a cloud infrastructure trust stack?
Antwoord
Physical facilities, network, compute, storage, virtualization, and management services. A workload inherits dependencies and failure modes from every layer beneath or beside it.
Kaart 129
Vraag
How do the management plane and data plane differ?
Antwoord
The management plane configures and governs resources; the data plane carries or processes workload traffic and data. Compromise of the management plane can change many data-plane controls at once.
Kaart 130
Vraag
What is a trust boundary in cloud architecture?
Antwoord
A point where identity, control, ownership, or assurance changes. Data crossing it needs an explicit policy, validation, and protected channel.
Kaart 131
Vraag
Who owns a customer's cloud network and identity configuration?
Antwoord
The customer for the configuration choices it controls. Provider defaults and guardrails help, but do not approve the customer's architecture.
Kaart 132
Vraag
What logical control prevents one tenant from reaching another tenant's resources?
Antwoord
Enforced tenant partitioning across identity, network, compute, storage, and management paths. Test the negative boundary, not only valid access.
Kaart 133
Vraag
Why is the cloud management plane a high-value target?
Antwoord
It can create, modify, expose, or destroy many resources through one privileged interface. Protect it more strongly than routine workload access.
Kaart 134
Vraag
What limits lateral movement after one cloud workload is compromised?
Antwoord
Microsegmentation with identity-aware, least-privilege communication policy. Monitor denied and unusual flows to find attempted spread.
Kaart 135
Vraag
How does infrastructure as code improve control assurance?
Antwoord
It makes configuration reviewable, repeatable, testable, and traceable. Protect the repository, pipeline, state, modules, and deployment identity.
Kaart 136
Vraag
How should a team verify an infrastructure control still works?
Antwoord
Test its intended outcome with current evidence and representative failure or attack conditions. Configuration presence alone does not prove effectiveness.
Kaart 137
Vraag
What security boundary should virtualization create between tenants?
Antwoord
Strong isolation of compute, memory, storage, network, and management operations. Shared hardware still creates side-channel, escape, and noisy-neighbor considerations.
Kaart 138
Vraag
Which controls should protect cloud management-plane access?
Antwoord
Phishing-resistant MFA, privileged access management, separate admin identities, conditional access, least privilege, and immutable logging. Restrict source networks where practical.
Kaart 139
Vraag
How do type 1 and type 2 hypervisors differ?
Antwoord
A type 1 hypervisor runs directly on hardware; a type 2 hypervisor runs on a host operating system. The extra host layer changes attack surface and operational use.
Kaart 140
Vraag
Who secures the public cloud facility and physical host?
Antwoord
The cloud provider. Customers still evaluate the provider's physical assurance and design their service around disclosed locations and failure domains.
Kaart 141
Vraag
What protects a cloud AI training cluster from unrelated tenant traffic?
Antwoord
Dedicated identities, microsegmentation, controlled data paths, hardened images, and monitored management access. Accelerator scheduling and storage paths belong in the boundary.
Kaart 142
Vraag
When is packet capture useful in cloud infrastructure?
Antwoord
When network-level detail is needed and collection is lawful, technically available, scoped, and protected. Flow logs may be safer and sufficient for many investigations.
Kaart 143
Vraag
Which control protects detached cloud volumes and snapshots?
Antwoord
Encryption with governed keys plus explicit access policy. Inventory and delete orphaned copies because detachment does not remove their data.
Kaart 144
Vraag
Why correlate infrastructure logs across layers?
Antwoord
To connect identity, management, network, host, and workload events into one incident path. Preserve original records and normalization context.
Kaart 145
Vraag
What is a platform owner's responsibility for tenant isolation?
Antwoord
Configure, patch, monitor, and test the shared platform so one workload cannot cross its authorized boundary. Consumers must use the platform's isolation features correctly.
Kaart 146
Vraag
When should an AI training cluster use stronger isolation than ordinary batch compute?
Antwoord
When valuable models, sensitive datasets, untrusted code, or high-cost accelerators raise confidentiality, integrity, or exhaustion risk. Match isolation to the workload threat model.
Kaart 147
Vraag
What does an HSM protect in cloud infrastructure?
Antwoord
Cryptographic keys and operations inside a hardened, policy-controlled boundary. An HSM does not decide whether the requesting workload is authorized unless surrounding policy enforces it.
Kaart 148
Vraag
What is a failure domain?
Antwoord
A set of components likely to fail together because they share a dependency. Regions, zones, racks, power feeds, control services, or software versions can define one.
Kaart 149
Vraag
A volume is deleted but its snapshots remain. Is the data gone?
Antwoord
No. The snapshots are separate retained copies. Apply inventory, retention, hold, encryption-key, and deletion policy to every snapshot and replica.
Kaart 150
Vraag
How should a platform reduce virtualization escape risk?
Antwoord
Minimize and patch the virtualization stack, isolate management interfaces, restrict device exposure, monitor anomalies, and contain workloads by risk. Stronger workload boundaries may be needed for hostile tenants.
Kaart 151
Vraag
What is the first response to an internet-exposed cloud management endpoint?
Antwoord
Remove unnecessary public reachability, then enforce strong identity and monitored privileged access. A hidden URL or uncommon port is not a control.
Kaart 152
Vraag
What is the facilities team's role in a private cloud data center?
Antwoord
Operate physical access, power, cooling, fire protection, and environmental monitoring. Security requirements should define evidence and escalation for those systems.
Kaart 153
Vraag
Which site-location condition creates direct legal exposure for a cloud workload?
Antwoord
The jurisdictions that can reach the facility, operator, customers, or data. Cost, hazards, utilities, connectivity, workforce, and physical threats require separate location analysis.
Kaart 154
Vraag
How does diverse pathway connectivity improve resilience?
Antwoord
It prevents one cable route, conduit, carrier handoff, or excavation from cutting every link. Verify physical diversity rather than relying on different circuit names.
Kaart 155
Vraag
When does building a private data center make more sense than buying cloud capacity?
Antwoord
When requirements for control, latency, sovereignty, specialized hardware, or long-term economics outweigh the build and operating burden. Compare full lifecycle cost and resilience, not purchase price alone.
Kaart 156
Vraag
Which physical controls protect cloud hardware from unauthorized handling?
Antwoord
Zoned access, least privilege, identity checks, surveillance, visitor controls, alarms, and custody records. The strength should match asset and data impact.
Kaart 157
Vraag
What power design reduces a data center's single-point risk?
Antwoord
Independent feeds, conditioned distribution, UPS capacity, generators, fuel plans, and tested transfer. Maintenance paths must preserve the intended redundancy.
Kaart 158
Vraag
What should environmental monitoring detect in a data center?
Antwoord
Temperature, humidity, airflow, water, smoke, power, and equipment conditions that threaten service. Alerts need thresholds, escalation, and tested response.
Kaart 159
Vraag
How does resilience differ from simple redundancy?
Antwoord
Redundancy adds alternatives; resilience keeps or restores acceptable service despite disruption. Redundant components can still share one failure domain or bad configuration.
Kaart 160
Vraag
Which on-premises physical control remains a customer duty when workloads move to public cloud?
Antwoord
Protection of customer-controlled offices, endpoints, network links, and any retained equipment. The provider's data-center controls do not secure the customer's physical environment.
Kaart 161
Vraag
What are the core outputs of an infrastructure risk assessment?
Antwoord
Prioritized risks tied to assets, threats, vulnerabilities, likelihood, impact, existing controls, and owners. The output should lead to treatment and follow-up.
Kaart 162
Vraag
Who may accept residual infrastructure risk?
Antwoord
The authorized business risk owner, not the engineer who found it. Acceptance should state scope, duration, rationale, and review trigger.
Kaart 163
Vraag
How do a threat, vulnerability, and risk differ?
Antwoord
A threat can cause harm, a vulnerability is a weakness it may exploit, and risk combines uncertain harm with business impact. A weakness without relevant exposure may be lower priority.
Kaart 164
Vraag
What reveals that two supposedly redundant cloud systems share fate?
Antwoord
They depend on the same control plane, account, region, identity service, network path, software defect, operator, or key. Model those dependencies before counting redundancy.
Kaart 165
Vraag
What does a security control owner do?
Antwoord
Ensures an assigned control is designed, implemented, evidenced, monitored, and corrected. The role may coordinate several technical operators.
Kaart 166
Vraag
Which risk treatment options should a cloud team recognize?
Antwoord
Avoid, mitigate, transfer or share, and accept. Treatment changes exposure or ownership; it does not erase accountability.
Kaart 167
Vraag
What is a recovery service level?
Antwoord
The minimum service capacity or functionality that must be restored, often stated as a percentage of normal service. RSL defines how much service must work; RTO sets the time limit, while RPO sets the maximum data-loss interval.
Kaart 168
Vraag
What makes a machine image trustworthy for cloud deployment?
Antwoord
Known provenance, minimal contents, current patches, signed or verified integrity, vulnerability results, and controlled promotion. Revalidate it when dependencies age.
Kaart 169
Vraag
When do multiple availability zones materially improve resilience?
Antwoord
When the service, data, network, identities, and operations can continue after one zone and its shared dependencies fail. Merely placing instances in two zones is not a tested design.
Kaart 170
Vraag
What should determine the strength of an infrastructure security control?
Antwoord
The asset impact, threat, vulnerability, exposure, legal duties, and risk tolerance. Use control frameworks as structured input, not as an automatic one-size baseline.
340 kaarten
CCSP 2026 Flashcards: August Exam Outline Review
Gratis leren met dit deckNibomo opent zodat je meteen kunt beginnen met leren.
Kaart 171
Vraag
Which layered controls improve availability against cloud DDoS?
Antwoord
Provider edge absorption, rate controls, resilient scaling, caching, WAF or protocol filtering, and an exercised response plan. Scaling alone can turn attack traffic into cost exhaustion.
Kaart 172
Vraag
A cloud contract shifts breach costs to a provider. Has the risk been removed?
Antwoord
No. Financial risk may be transferred, while operational, legal, reputational, and customer harm can remain. Retained exposure still needs mitigation and acceptance.
Kaart 173
Vraag
Why map dependencies across compute, storage, and network services?
Antwoord
A resilient application can still fail when a shared supporting service fails. Dependency maps expose hidden single points, circular recovery steps, and shared fate.
Kaart 174
Vraag
What does RPO constrain in an infrastructure recovery design?
Antwoord
The maximum acceptable data-loss interval measured backward from disruption. It drives backup or replication frequency and consistency choices.
Kaart 175
Vraag
What should trigger automated failover?
Antwoord
Reliable health evidence that the primary cannot meet the service objective, with safeguards against split-brain and false triggers. Manual approval may remain appropriate for ambiguous high-impact cases.
Kaart 176
Vraag
When is an IPS preferable to an IDS?
Antwoord
When inline blocking is justified, tested, and safe for the traffic and availability requirements. Use detection-only when false positives or inline failure would create unacceptable impact.
Kaart 177
Vraag
What makes residual infrastructure risk ready for acceptance?
Antwoord
A clear scenario, affected assets, existing controls, likelihood and impact, owner, duration, alternatives, and review trigger. Vague acceptance is not governance.
Kaart 178
Vraag
What makes a cloud backup resistant to account compromise?
Antwoord
Separate administration, immutable or offline retention, encryption, protected deletion, and tested restore. Keep recovery credentials outside the routine production trust path.
Kaart 179
Vraag
What does a BC/DR coordinator own during cloud recovery planning?
Antwoord
The cross-team plan, exercises, dependencies, contacts, evidence, and follow-up. Service owners still set business priorities and targets.
Kaart 180
Vraag
Which recovery design supports a near-zero RPO?
Antwoord
Synchronous or otherwise strongly consistent replication across independent failure domains, if latency and shared-fate limits are acceptable. Backups still protect against corruption and deletion.
Kaart 181
Vraag
Which overlooked dependency can stop users from reaching replicated application servers after failover?
Antwoord
The identity service. Recovery planning should also cover DNS, keys, secrets, routes, data stores, quotas, and external services.
Kaart 182
Vraag
Why test restore separately from backup completion?
Antwoord
A completed backup may be corrupt, incomplete, inaccessible, or too slow for the target. Restore testing proves usability and measures recovery performance.
Kaart 183
Vraag
Why plan failback before declaring a DR design complete?
Antwoord
Returning to the preferred environment can create another outage, conflict, or data loss. Define authority, synchronization, validation, rollback, and communication.
Kaart 184
Vraag
Which design choice most directly supports a short RTO?
Antwoord
Pre-provisioned or rapidly deployable recovery capacity with automated, tested orchestration. Data, identities, network, dependencies, and operators must be ready too.
Kaart 185
Vraag
What should application-security awareness change in a cloud team?
Antwoord
Daily design and delivery decisions, not just annual quiz results. Use role-specific OWASP, ASVS, SANS Top 25, and LLM-risk examples as practical boundaries, then reinforce them with real defects.
Kaart 186
Vraag
What makes an SDLC a secure SDLC?
Antwoord
Security requirements, design analysis, implementation controls, verification, release evidence, maintenance, and retirement are built into the lifecycle. A final penetration test alone is not a lifecycle.
Kaart 187
Vraag
How do functional and non-functional security requirements differ?
Antwoord
Functional requirements specify security behavior; non-functional requirements set qualities such as availability, performance, resilience, or assurance. Both need measurable acceptance criteria.
Kaart 188
Vraag
Who turns business needs into testable application security requirements?
Antwoord
The product or business owner with security, privacy, legal, and engineering input. Requirements need an accountable owner and acceptance evidence.
Kaart 189
Vraag
How should a security requirement remain visible through delivery?
Antwoord
Trace it to design decisions, code or configuration, tests, approval, and operating evidence. Untraceable requirements are easy to drop during change.
Kaart 190
Vraag
What is the purpose of threat modeling?
Antwoord
Identify likely abuse paths and design mitigations before or during development. Keep the model tied to assets, trust boundaries, architecture changes, and evidence.
Kaart 191
Vraag
What makes developer security training actionable?
Antwoord
Role-specific examples, secure alternatives, practice in the delivery toolchain, and feedback from real defects. Refresh it as platforms and threats change.
Kaart 192
Vraag
Should agile delivery remove formal security gates?
Antwoord
No. It should make them smaller, earlier, automated where reliable, and tied to risk. High-impact changes can still require independent approval.
Kaart 193
Vraag
Which cloud-specific application risks need explicit SDLC decisions before coding?
Antwoord
Shared-technology exposure, provider insiders, limited visibility or control, and legal or jurisdiction boundaries. Record the provider boundary, evidence, data location, isolation, and compensating controls.
Kaart 194
Vraag
How do federation and SSO differ?
Antwoord
Federation establishes trust across identity domains; SSO lets a user authenticate once for multiple services. Federation can enable SSO, but the concepts are not identical.
Kaart 195
Vraag
What is a developer's responsibility in secure cloud delivery?
Antwoord
Use approved patterns, validate inputs and outputs, protect secrets, handle errors safely, review dependencies, and fix findings. Security tools support that judgment rather than replace it.
Kaart 196
Vraag
What should a peer security reviewer verify?
Antwoord
That the change preserves requirements, trust boundaries, authorization, data handling, failure behavior, and evidence. Review the actual diff and deployment effect, not only style.
Kaart 197
Vraag
What is the application security architect accountable for?
Antwoord
Security patterns, trust boundaries, threat decisions, control integration, and documented exceptions. Teams share implementation, but architecture needs coherent ownership.
Kaart 198
Vraag
Which threat categories does STRIDE prompt a team to examine?
Antwoord
Spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege. It is a coverage aid, not a risk score.
Kaart 199
Vraag
What secure-coding rule most directly prevents broken object authorization?
Antwoord
Check the current subject's permission for the specific object on every request. ASVS or SAFECode guidance can structure assurance, but hiding identifiers or checking only authentication is insufficient.
Kaart 200
Vraag
What should a secret-scanning gate do when it finds a real credential?
Antwoord
Block exposure, revoke or rotate the credential, remove it from reachable history, and investigate use. Deleting the latest line does not invalidate copied history.
Kaart 201
Vraag
How does protected version control support software assurance?
Antwoord
It creates tamper-evident, access-controlled history for reviewed code and configuration changes. Protect references from unauthorized rewrite, retain audit logs, control bypass, and bind signed artifacts to approved releases; content-addressed commits alone do not make branch history immutable.
Kaart 202
Vraag
Which threat-model method is the simplest checklist for threat categories at trust boundaries?
Antwoord
STRIDE. Use a process-centered method when business impact, attacker paths, and staged analysis need deeper treatment.
Kaart 203
Vraag
What is an abuse case?
Antwoord
A description of how an actor could misuse a feature or violate a security goal. It turns attacker intent into testable defensive behavior.
Kaart 204
Vraag
Why should a team avoid treating DREAD scores as objective truth?
Antwoord
Its ratings are judgment-based and can create false precision. Document evidence, assumptions, impact, and uncertainty instead of relying on one number.
Kaart 205
Vraag
How do SAST and DAST differ?
Antwoord
SAST examines code or compiled artifacts without running the full application; DAST probes a running application from the outside. They find different classes of weakness.
Kaart 206
Vraag
What does Software Composition Analysis examine?
Antwoord
Third-party components, versions, licenses, and known vulnerability or policy data. It does not prove that a dependency is safe in context or detect every malicious package.
Kaart 207
Vraag
When should a cloud application's threat model be updated?
Antwoord
When trust boundaries, data, identities, dependencies, deployment, features, or threats materially change. Periodic review catches slow drift.
Kaart 208
Vraag
How do black-box and white-box security testing differ?
Antwoord
Black-box testing uses external behavior with little internal knowledge; white-box testing uses code, design, or configuration knowledge. Gray-box testing combines partial knowledge with external interaction.
Kaart 209
Vraag
What should a CI/CD security gate block?
Antwoord
A defined, evidence-based release condition such as an exposed secret, failed critical control, unapproved artifact, or unacceptable vulnerability. Keep exceptions explicit, owned, and time-bounded.
Kaart 210
Vraag
When is PASTA or ATASM more useful than a short threat checklist?
Antwoord
When the team needs a structured path from business objectives and architecture to attacker behavior, attack surfaces, and mitigations. Match method depth to decision risk.
Kaart 211
Vraag
Where does SAST provide the earliest useful feedback?
Antwoord
During coding and pull-request review, before deployment. Tune rules, confirm reachability and context, and fix root causes rather than chasing raw counts.
Kaart 212
Vraag
When is IAST worth adding to a cloud test pipeline?
Antwoord
When representative automated tests exist and runtime path-to-code insight will improve triage. Without exercised paths, instrumentation has little to observe.
Kaart 213
Vraag
How should an application handle LLM output before passing it to a browser, shell, database, or tool?
Antwoord
Treat it as untrusted data and validate, encode, constrain, or approve it for the destination. Model fluency is not a security guarantee.
Kaart 214
Vraag
What should an abuse-case test assert for a sensitive workflow?
Antwoord
The application safely rejects or contains a realistic misuse path and leaves useful evidence. Test rate, sequence, privilege, data, and failure-state abuse where relevant.
Kaart 215
Vraag
What environment makes DAST results most useful?
Antwoord
A representative running deployment with safe test data, reachable paths, and observable results. Production testing needs explicit authorization and safeguards.
Kaart 216
Vraag
Who owns risk from a third-party software component?
Antwoord
The organization that chooses and operates it. The supplier supplies evidence and remediation, but outsourcing the component does not outsource customer accountability.
Kaart 217
Vraag
How do an SBOM and SCA work together?
Antwoord
SCA identifies component and policy findings; an SBOM records the released component inventory. Bind both to the exact artifact and update risk when new information appears.
Kaart 218
Vraag
What does artifact signing protect in a software supply chain?
Antwoord
Integrity and authenticated provenance of the signed artifact. Verification policy must also trust the signer, build path, and release authorization.
Kaart 219
Vraag
What makes open-source software validated for a cloud application?
Antwoord
Its source, release, integrity, dependencies, license, maintenance, vulnerabilities, and intended use have been assessed. Open code is inspectable, not automatically safe.
Kaart 220
Vraag
Which cloud application control validates XML message structure before processing?
Antwoord
An XML firewall. A WAF filters web traffic, an API gateway applies API-facing policy, DAM monitors database activity, and a load balancer distributes traffic.
Kaart 221
Vraag
What authorization check belongs behind every sensitive API operation?
Antwoord
A server-side decision for the current identity, action, object, tenant, and context. Gateway authentication alone cannot decide application-level ownership.
Kaart 222
Vraag
How should an API treat untrusted input?
Antwoord
Validate type, structure, size, range, encoding, and allowed semantics before use. Reject unexpected fields where ambiguity or mass assignment creates risk.
Kaart 223
Vraag
What is an Identity Provider responsible for in federation?
Antwoord
Authenticating subjects and issuing trustworthy identity assertions under agreed policy. The relying application still authorizes each requested action.
Kaart 224
Vraag
What does sandboxing add to cloud application security?
Antwoord
A constrained execution boundary for untrusted or risky code and content. Restrict identity, network, files, secrets, time, and compute outside the sandbox too.
Kaart 225
Vraag
What should block adoption of a third-party software component?
Antwoord
Unacceptable provenance, integrity, vulnerability, maintenance, license, access, or exit risk. Popularity and a clean scan do not settle supplier risk.
Kaart 226
Vraag
Which test perspective should verify hidden authorization logic?
Antwoord
White-box review and testing, supported by black-box attempts to cross the boundary. Internal knowledge finds code paths; external tests confirm observable enforcement.
Kaart 227
Vraag
Which practice verifies that a cloud release consistently meets defined quality and security criteria?
Antwoord
Quality Assurance (QA). It plans and tracks repeatable reviews, tests, acceptance evidence, defect handling, and process improvement across delivery.
Kaart 228
Vraag
Which IAM controls reduce takeover of a federated cloud account?
Antwoord
Strong MFA, trusted federation configuration, short sessions, conditional access, lifecycle automation, and monitored privilege. Secure both the IdP and relying service.
Kaart 229
Vraag
What is the safest response when retrieved content tells an LLM to ignore system rules?
Antwoord
Treat the instruction as untrusted data, preserve higher-priority policy, and prevent unauthorized tool or data access. Input filtering alone cannot eliminate prompt injection.
Kaart 230
Vraag
How should an LLM application reduce sensitive information disclosure?
Antwoord
Minimize prompt and training data, enforce retrieval authorization, redact where justified, constrain outputs, and test leakage. A system prompt telling the model to keep secrets is not sufficient.
Kaart 231
Vraag
A model repository account is compromised and a backdoored model is published. Which risks overlap?
Antwoord
Supply-chain compromise and data or model poisoning. Pin trusted versions, verify provenance and signatures, scan safely, validate behavior, and control promotion.
Kaart 232
Vraag
What identity should one microservice use to call another?
Antwoord
A distinct, short-lived workload identity with least-privilege authorization. Avoid sharing broad static credentials across services.
Kaart 233
Vraag
How should an agentic LLM be constrained before it can delete cloud resources?
Antwoord
Give it minimal scoped tools, validate arguments, require approval for destructive actions, enforce budgets, and log every decision and result. Capability should match the smallest authorized task.
Kaart 234
Vraag
Should a system prompt be treated as a secret control boundary?
Antwoord
No. Design as if instructions may be exposed. Keep credentials and authorization outside the prompt, minimize sensitive details, and enforce policy in trusted code.
Kaart 235
Vraag
What is the main risk of weak authorization in a shared vector store?
Antwoord
Retrieval can cross tenant or user boundaries and expose embeddings, documents, or poisoned context. Partition, authorize, validate provenance, and monitor ingestion and queries.
Kaart 236
Vraag
When does a CASB add value beside an IdP?
Antwoord
When the organization needs visibility or policy over cloud-service use, data movement, sessions, or unmanaged access beyond authentication. The IdP establishes identity; the CASB governs selected cloud interactions.
Kaart 237
Vraag
How should a high-impact workflow use an LLM answer that may be plausible but false?
Antwoord
Verify it against authoritative data or require qualified human review before action. Communicate uncertainty and preserve source evidence.
Kaart 238
Vraag
Which controls address unbounded LLM consumption?
Antwoord
Per-user and per-task quotas, rate limits, token and tool budgets, timeouts, concurrency limits, anomaly alerts, and safe cancellation. Monitor financial as well as availability impact.
Kaart 239
Vraag
How do an HSM and a TPM differ?
Antwoord
An HSM protects shared or service cryptographic operations; a TPM anchors trust to one platform. Both protect keys, but their scope and use cases differ.
Kaart 240
Vraag
What does secure by default mean for cloud infrastructure?
Antwoord
A new resource starts in the least exposed, least privileged, approved state. Users must make an explicit, reviewed choice to widen access or capability.
Kaart 241
Vraag
Why do virtual CPU, memory, storage, and network settings have security impact?
Antwoord
They define resource exposure, isolation, exhaustion limits, and device access. Overbroad virtual hardware can create attack paths or noisy-neighbor risk.
Kaart 242
Vraag
Which hypervisor type is usually preferred for production cloud hosts?
Antwoord
A type 1 hypervisor because it removes the general-purpose host OS layer. The actual choice still depends on assurance, patching, management, and workload needs.
Kaart 243
Vraag
How can TPM-backed measured boot support cloud host assurance?
Antwoord
Measurements anchor boot components to hardware so an attestation service can compare them with approved state. The decision still depends on trusted reference values and response policy.
Kaart 244
Vraag
How should guest OS virtualization tools be installed and maintained?
Antwoord
Use provider-authorized packages, enable only needed features, match supported versions, patch promptly, and monitor their privilege. Remove stale tools that widen the host-to-guest boundary.
Kaart 245
Vraag
What is cloud platform operations responsible for after secure build?
Antwoord
Maintaining approved configuration, availability, patching, monitoring, backup, access, and evidence. Operations should feed recurring defects back into design.
Kaart 246
Vraag
What does a privileged access administrator control?
Antwoord
The issuance, elevation, monitoring, review, and revocation of administrative access. Separate the access-control role from routine use where practical.
Kaart 247
Vraag
What is the safer pattern for remote SSH administration?
Antwoord
Short-lived identity-based access through a controlled path with host verification, least privilege, session logging, and no shared keys. Disable direct root login.
Kaart 248
Vraag
When should a cloud workload require platform attestation?
Antwoord
When access depends on proof that the host or confidential environment is in an approved measured state. Define what is measured, who verifies it, and what failure does.
Kaart 249
Vraag
Which protocol adds origin authentication and integrity to DNS data?
Antwoord
DNSSEC. TLS protects a transport session, a VPN protects traffic across an untrusted boundary, and DHCP safeguards prevent rogue address or configuration assignment.
Kaart 250
Vraag
What should enforce separation between cloud network zones?
Antwoord
Routing and firewall or security-group policy tied to explicit allowed flows. VLANs can organize segments but do not enforce policy by themselves.
Kaart 251
Vraag
How do IDS and IPS differ operationally?
Antwoord
An IDS alerts on suspected activity; an IPS sits inline and can block it. Inline prevention adds availability and false-positive risk.
Kaart 252
Vraag
What reduces RDP exposure in a cloud environment?
Antwoord
Remove direct internet access, require a hardened gateway or private path, strong MFA, current patches, device checks, and session monitoring. Limit clipboard and drive redirection by need.
Kaart 253
Vraag
What makes a honeypot safe enough to operate?
Antwoord
Isolation, no production trust, controlled data, monitored egress, legal approval, and an incident plan. It should observe attackers without becoming their launch point.
Kaart 254
Vraag
How do high availability and backup differ?
Antwoord
High availability keeps service running through component failure; backup restores data or state after loss or corruption. One does not replace the other.
Kaart 255
Vraag
How should firewall, IDS, and IPS controls be layered?
Antwoord
Firewalls constrain allowed paths, IDS detects suspicious activity, and IPS may block selected attacks inline. Central telemetry and tuned ownership make the layers useful.
Kaart 256
Vraag
When is a cloud security group insufficient as the only network control?
Antwoord
When application-aware filtering, centralized inspection, advanced threat detection, or cross-environment policy is required. Keep security groups as workload-level least-privilege boundaries.
Kaart 257
Vraag
How should management-plane tools be installed?
Antwoord
From verified sources through a controlled, minimal, hardened build with separate privileged access and logging. Remove sample accounts, unused plugins, and default exposure.
Kaart 258
Vraag
What is patch management?
Antwoord
A controlled lifecycle for identifying, prioritizing, testing, deploying, verifying, and documenting security and reliability updates. Asset inventory and exception ownership are prerequisites.
Kaart 259
Vraag
How do performance and capacity monitoring differ?
Antwoord
Performance monitoring measures current service behavior; capacity monitoring forecasts whether resources can meet future demand. Both need business thresholds and trends.
Kaart 260
Vraag
How do change, release, and deployment management differ?
Antwoord
Change management authorizes and controls modification; release management packages approved capability; deployment management moves it into an environment. One workflow may integrate all three without erasing their goals.
Kaart 261
Vraag
What should decide whether an IPS blocks automatically?
Antwoord
Detection confidence, asset criticality, attack impact, false-positive cost, bypass behavior, and rollback. Start with observation when evidence is weak.
Kaart 262
Vraag
Who owns a patch exception?
Antwoord
The authorized system or risk owner, with technical evidence from operations and security. The exception needs compensating controls, expiry, and review.
Kaart 263
Vraag
What does a capacity manager protect?
Antwoord
The service's ability to meet current and forecast demand within cost and resilience constraints. The role tracks trends, thresholds, quotas, and scaling lead time.
Kaart 264
Vraag
What is the change manager's security role?
Antwoord
Ensure risk, testing, authorization, scheduling, rollback, and communication are proportionate to the change. Emergency changes still need retrospective evidence.
Kaart 265
Vraag
What should a backup-and-restore control verify for guest systems?
Antwoord
Required data and configuration are captured, protected, retained, and restored within targets. Include application consistency, keys, dependencies, and documented restore order.
Kaart 266
Vraag
Which management process keeps a cloud service able to meet its agreed uptime and reliability targets?
Antwoord
Availability management. It analyzes failure patterns, resilience, maintainability, and recovery so the service can meet those targets.
Kaart 267
Vraag
What improves patch prioritization beyond a severity score?
Antwoord
Exploitability, exposure, asset importance, compensating controls, dependency, and business impact. Verify remediation and track unsupported assets separately.
Kaart 268
Vraag
What turns performance and capacity alerts into an availability control?
Antwoord
Thresholds tied to service objectives, trend analysis, ownership, safe scaling, and tested response. Alert volume without action is not capacity management.
Kaart 269
Vraag
What should a configuration-management system record?
Antwoord
Approved items, owners, versions, relationships, baselines, changes, and current state. Cloud discovery should reconcile actual resources with declared configuration.
Kaart 270
Vraag
Why place a cluster host into maintenance mode?
Antwoord
To drain or protect workloads before planned work while preserving cluster policy. Verify capacity, placement constraints, and stateful-service behavior first.
Kaart 271
Vraag
Which management process agrees, monitors, and reviews measurable service targets with customers?
Antwoord
Service-level management. It turns business needs into agreed service objectives, tracks results, and drives action when performance misses them.
Kaart 272
Vraag
Which hardware signals should cloud facilities monitor?
Antwoord
Disk health, CPU and memory errors, fan and temperature state, power, and vendor fault telemetry. Correlate physical signals with host and workload impact.
Kaart 273
Vraag
How should an OS hardening baseline be maintained?
Antwoord
Version it, test it, measure compliance, remediate drift, record exceptions, and update it for new threats and platform changes. Apply separate profiles to distinct workloads.
Kaart 274
Vraag
How do incident management and problem management differ?
Antwoord
Incident management restores service and limits harm; problem management finds and removes underlying causes. The same event can open both tracks.
Kaart 275
Vraag
Which management process coordinates security risk and controls across cloud service operation?
Antwoord
Information security management. It aligns policy, risk treatment, control operation, evidence, incidents, and improvement with the service-management system.
Kaart 276
Vraag
Which management process turns recurring service-control gaps into measured improvements?
Antwoord
Continual service improvement management. It prioritizes opportunities, defines a measurable target and owner, implements change, and verifies the outcome.
Kaart 277
Vraag
How should operations choose among NIST, ISO, COBIT, CIS Controls, COSO, ITIL, or ISO/IEC 20000-1?
Antwoord
Map the applicable framework or standard to the organization's legal duties, risks, service goals, and evidence needs. The names are not interchangeable, and adoption alone does not prove control effectiveness.
Kaart 278
Vraag
A service is restored after repeated crashes. Which process continues the root-cause work?
Antwoord
Problem management. Incident management can close after stable restoration while the underlying defect, workaround, and prevention remain tracked.
Kaart 279
Vraag
Which management process owns tested arrangements for sustaining or restoring critical services after severe disruption?
Antwoord
Continuity management. Incident management handles the current event, while availability management focuses on meeting service uptime and reliability targets.
Kaart 280
Vraag
What does a cloud forensic lead decide?
Antwoord
The lawful collection strategy, volatile-data priorities, tools, provider coordination, preservation, and analysis plan. The lead should understand cloud-specific evidence limits.
Kaart 281
Vraag
What does chain of custody record?
Antwoord
Who collected, handled, transferred, stored, analyzed, and disposed of evidence, when and why. Integrity checks support the record but do not replace it.
Kaart 282
Vraag
What does an incident commander own?
Antwoord
Priorities, roles, decisions, coordination, cadence, and safe handoffs during an incident. Technical responders investigate and act within that structure.
Kaart 283
Vraag
What does the incident communications lead control?
Antwoord
Approved messages, audiences, channels, timing, records, and coordination with legal and leadership. Technical certainty and disclosure obligations may change during the event.
Kaart 284
Vraag
How do a SOC, SIEM, and SOAR relate?
Antwoord
A SOC is the operating function, a SIEM centralizes and analyzes security events, and SOAR coordinates automated workflows. People, process, authority, and evidence connect the tools.
Kaart 285
Vraag
What is an evidence custodian responsible for?
Antwoord
Controlled storage, access, transfer, integrity verification, retention, and chain-of-custody records. The custodian preserves evidence without altering its meaning.
Kaart 286
Vraag
How should a SOC use threat intelligence?
Antwoord
Map relevant, timely indicators and adversary behavior to assets, detections, hunts, and decisions. Expire stale indicators and separate confidence from fact.
Kaart 287
Vraag
How should AI-assisted security monitoring be governed?
Antwoord
Validate data and models, measure errors and drift, limit action authority, log reasoning inputs and outcomes, and keep human review for consequential cases. Compare against a safe manual path.
Kaart 288
Vraag
When is a cloud snapshot suitable forensic evidence?
Antwoord
When collection is authorized, scope and timing are documented, integrity is protected, and the snapshot preserves relevant state. It may omit memory, external services, or rapidly changing logs.
Kaart 289
Vraag
Who decides whether a regulator must be notified during a cloud incident?
Antwoord
The authorized legal or compliance owner under the incident plan. Vendor and communications owners coordinate channels; engineers supply verified facts.
Kaart 290
Vraag
What should a forensic plan obtain from the cloud provider before an incident?
Antwoord
Available logs and APIs, retention, time sources, support contacts, legal process, evidence formats, isolation options, and responsibility boundaries. Confirm access with an exercise.
Kaart 291
Vraag
How should vulnerability assessment and penetration testing work together?
Antwoord
Assessment finds and prioritizes likely weaknesses broadly; authorized penetration testing demonstrates selected exploit paths and impact. Both require scoped remediation and retest.
Kaart 292
Vraag
How should a SIEM protect cloud log value?
Antwoord
Normalize without losing source evidence, control access, preserve time and integrity, correlate identities and assets, tune detections, and retain by purpose. Monitor collection gaps.
Kaart 293
Vraag
What should SOAR do when a playbook's evidence is incomplete?
Antwoord
Pause or take only a safe reversible step, preserve context, and escalate to an authorized human. Do not let automation convert uncertainty into broad containment damage.
Kaart 294
Vraag
When should incident communication wait?
Antwoord
Only when authorized coordination is needed to verify facts, protect response, or meet a defined legal strategy. Do not delay a mandatory notice past its trigger or deadline.
Kaart 295
Vraag
When is penetration testing more useful than another vulnerability scan?
Antwoord
When the organization needs authorized evidence that selected weaknesses can combine into a meaningful attack path. Scanning remains better for broad, repeatable coverage.
Kaart 296
Vraag
Which evidence should be collected first from a running cloud workload?
Antwoord
The most volatile, relevant evidence that will disappear earliest, if collection is authorized and safe. Balance volatility against service impact and contamination risk.
Kaart 297
Vraag
Why can cloud data be subject to more than one jurisdiction?
Antwoord
Customers, providers, processing, storage, people, contracts, and affected individuals may sit in different places. Location and legal reach are related but not identical.
Kaart 298
Vraag
Why are privacy roles contextual rather than permanent labels?
Antwoord
An organization can be controller for one processing purpose and processor for another. Determine the role from actual decisions and instructions, not the company type.
Kaart 299
Vraag
What should legal counsel contribute to cloud design?
Antwoord
Interpret applicable law, privilege, contracts, disputes, preservation, disclosure, and legal risk. Counsel advises; accountable business owners still decide within authority.
Kaart 300
Vraag
What is eDiscovery?
Antwoord
The identification, preservation, collection, processing, review, and production of electronically stored information for a legal matter. Cloud scale and provider control affect each step.
Kaart 301
Vraag
How do contractual and regulated private data differ?
Antwoord
Contractual duties come from agreed terms; regulated duties come from applicable law. The same data can be subject to both, and the stricter combined obligations may govern.
Kaart 302
Vraag
What is the controller's contract duty toward a cloud processor?
Antwoord
Give documented instructions, choose and oversee a capable processor, and define required privacy and security terms. Applicable law may add specific clauses and audit duties.
Kaart 303
Vraag
What is a Privacy Impact Assessment?
Antwoord
A structured evaluation of how planned processing affects people and how privacy risk will be handled. Perform it early enough to change the design.
Kaart 304
Vraag
What is an ISMS?
Antwoord
A managed system of policies, risk processes, controls, evidence, review, and continual improvement for information security. It is broader than a control checklist or toolset.
Kaart 305
Vraag
What does a contract's choice-of-law clause do?
Antwoord
Names the law intended to govern the contract. It does not automatically override mandatory laws or every court's jurisdiction.
Kaart 306
Vraag
What makes a legal hold operationally defensible in cloud systems?
Antwoord
Authorized scope, prompt preservation, deletion suspension, controlled collection, access logging, periodic review, and documented release. Test whether provider features cover all copies.
Kaart 307
Vraag
Does calling a field PII or PHI settle every privacy obligation?
Antwoord
No. Applicability depends on the data, person, entity, purpose, context, and governing law or contract. Classify with qualified privacy and legal input.
Kaart 308
Vraag
Which design control reduces privacy risk before consent screens and notices?
Antwoord
Data minimization tied to a specific approved purpose. Collecting less reduces exposure, rights handling, retention, and breach impact.
Kaart 309
Vraag
What is a processor's core duty toward controller data?
Antwoord
Process it only under authorized instructions and required legal obligations, while applying agreed controls and assistance. Subprocessors need governed approval and flow-down terms.
Kaart 310
Vraag
What control reveals cross-border cloud data processing before it becomes a compliance surprise?
Antwoord
A maintained data and subprocessors map tied to locations, purposes, roles, transfers, and safeguards. Reconcile contracts with actual telemetry and provider disclosures.
Kaart 311
Vraag
How do internal and external audits differ?
Antwoord
Internal audit provides independent assurance inside the organization; external audit is performed by an outside party for a defined objective. Both require scope, criteria, evidence, and independence.
Kaart 312
Vraag
When should a PIA be reopened?
Antwoord
When purpose, data, people, model, provider, location, sharing, retention, or risk materially changes. A one-time assessment becomes stale as processing evolves.
Kaart 313
Vraag
How should a cloud team use GDPR, PIPEDA, India's DPDP Act, FERPA, HIPAA, ISO/IEC 27018, or GAPP?
Antwoord
First determine which laws apply, then map their obligations and any selected framework guidance to actual processing and controls. A named standard or provider region is not automatic compliance.
Kaart 314
Vraag
Two countries impose conflicting duties on the same cloud records. What is the first move?
Antwoord
Escalate to qualified counsel with the exact data, actors, locations, contracts, orders, and timelines. Preserve evidence and avoid an irreversible technical action based on guesswork.
Kaart 315
Vraag
What protects an internal auditor's independence?
Antwoord
Authority to assess outside the operation being audited, objective reporting, and freedom from designing or owning the control under review. Internal employment does not prevent independence if governance is sound.
Kaart 316
Vraag
What does a privacy officer oversee?
Antwoord
Privacy governance, impact assessment, rights, transparency, lawful processing, transfers, incidents, and regulator engagement. The exact statutory role varies by jurisdiction.
Kaart 317
Vraag
What do SOC, SSAE, and ISAE labels tell an assurance-report reader?
Antwoord
SOC identifies a service-organization report family, while SSAE and ISAE identify attestation standards used for defined engagements. The exact report type, criteria, period, scope, exceptions, and subservices determine its value.
Kaart 318
Vraag
What must an audit plan define before cloud audit fieldwork starts?
Antwoord
The objective, criteria, scope, responsibilities, schedule, methods, evidence access, and reporting path. The plan should also name constraints and follow-up ownership.
Kaart 319
Vraag
How do risk appetite and risk tolerance differ?
Antwoord
Risk appetite expresses the amount and type of risk an organization is willing to pursue or retain; tolerance sets acceptable variation around objectives. Both guide escalation and treatment.
Kaart 320
Vraag
What does an enterprise risk owner decide?
Antwoord
Whether to avoid, mitigate, transfer or share, or accept a documented risk within authority. The owner tracks residual exposure and review triggers.
Kaart 321
Vraag
How should risk metrics be designed?
Antwoord
Tie each metric to a decision, owner, threshold, reliable source, trend, and response. Separate leading indicators from lagging outcomes and guard against easy gaming.
Kaart 322
Vraag
What is gap analysis?
Antwoord
Comparison of current control state with a required or target state. Each gap needs impact, owner, treatment, evidence, and due date.
Kaart 323
Vraag
What makes cloud audit evidence reliable?
Antwoord
Clear criteria, complete scope, trustworthy source, protected integrity, accurate time, repeatable collection, and accountable ownership. Screenshots without context are weak evidence.
Kaart 324
Vraag
Why does a distributed cloud model complicate audit scope?
Antwoord
Controls, evidence, people, providers, and data span locations and jurisdictions with different access and retention limits. Define boundaries and shared responsibilities before fieldwork.
Kaart 325
Vraag
Can a clean SOC report prove compliance with a customer's specialized regulation?
Antwoord
No. Map the report's criteria, period, scope, exceptions, subservices, and customer controls to the specific requirement. NERC CIP, HIPAA, HITECH, PCI, or another regime may need additional evidence.
Kaart 326
Vraag
What should a customer assess in a cloud provider's risk-management program?
Antwoord
Whether its policies, methods, controls, risk profile, and appetite fit the customer's requirements and exposure. Review evidence before selection and when material risk changes.
Kaart 327
Vraag
What is a data owner's enterprise-risk role?
Antwoord
Set business value, classification, allowed use, access, retention, and acceptable risk for the data. Custodians implement the resulting controls.
Kaart 328
Vraag
What AI evidence supports accountability and explainability without promising perfect interpretation?
Antwoord
Document intended use, data and model versions, decision roles, testing, limitations, human oversight, outputs, changes, and incident history. Match explanation depth to affected people and legal duties.
Kaart 329
Vraag
What does a data steward add to governance?
Antwoord
Consistent definitions, quality rules, metadata, lineage, and policy application across business use. The steward connects business meaning to operational handling.
Kaart 330
Vraag
What is procurement's security role in cloud outsourcing?
Antwoord
Make required risk, assurance, pricing, ownership, exit, and supplier terms part of selection and negotiation. Security requirements lose force if added after commercial commitment.
Kaart 331
Vraag
When should an organization avoid a cloud risk rather than mitigate it?
Antwoord
When stopping the activity is feasible and residual exposure would remain outside appetite or legal authority. Compare the business consequence of avoidance with other treatments.
Kaart 332
Vraag
What is an external auditor responsible for?
Antwoord
Perform the agreed independent engagement against stated criteria and report within its scope. The auditor does not own management's controls or risk decisions.
Kaart 333
Vraag
How do an MSA, SOW, and SLA differ?
Antwoord
The MSA sets the general legal relationship, the SOW defines specific work and deliverables, and the SLA sets measurable service commitments. Read them together for the full obligation.
Kaart 334
Vraag
What should a cloud risk register contain?
Antwoord
Scenario, assets, cause, consequence, owner, likelihood, impact, controls, treatment, residual risk, due dates, and review triggers. Link evidence and dependencies where useful.
Kaart 335
Vraag
Who should own a cloud contract after signature?
Antwoord
A named contract or vendor manager with business, legal, security, privacy, and service stakeholders. Ownership includes obligations, evidence, changes, renewals, disputes, and exit.
Kaart 336
Vraag
Which contract controls support a safe cloud exit?
Antwoord
Data and configuration export, assistance, timing, format, cost, continued access, verified deletion, transition support, and survival of needed duties. Exercise the exit path before a crisis.
Kaart 337
Vraag
What makes a contractual right to audit usable?
Antwoord
Defined scope, notice, frequency, methods, evidence access, confidentiality, cost, remediation, and alternatives when direct testing is unsafe. A vague right may be impossible to exercise.
Kaart 338
Vraag
When does source-code escrow reduce cloud vendor viability risk?
Antwoord
When usable code plus dependencies, documentation, rights, updates, and release triggers can support continuity. Escrow adds little if the customer cannot operate the service.
Kaart 339
Vraag
What should a cloud incident-notification clause define?
Antwoord
Trigger, timing, recipient, secure channel, minimum facts, updates, cooperation, evidence, regulator support, and subcontractor flow-down. Avoid waiting for the provider's final root cause before notice.
Kaart 340
Vraag
What should happen to customer data when a cloud contract ends?
Antwoord
Return or export it in a usable form, preserve only what is lawfully required, revoke access, and verify deletion across in-scope copies under the contract. Data ownership and transition duties should be settled before purchase.
340 kaarten
CCSP 2026 Flashcards: August Exam Outline Review
Nibomo opent zodat je meteen kunt beginnen met leren.