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