What makes a computing environment a cloud rather than ordinary hosted infrastructure?

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.

What is the security significance of broad network access?

Services are reachable through standard network mechanisms from varied clients. That reach increases the need for strong identity, transport protection, and endpoint-aware access.

How do resource pooling and multi-tenancy differ?

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.

What separates elasticity from scalability?

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.

What does measured service provide?

Metered visibility into resource consumption. The measurements support billing, capacity decisions, anomaly detection, and accountability.

What does on-demand self-service let a cloud customer do?

Provision needed capabilities without waiting for a provider employee. Policy and quota controls can still constrain the request.

What does virtualization contribute to cloud computing?

It abstracts physical resources into isolated, assignable compute, storage, or network units. Orchestration turns those units into an on-demand service.

What remains the cloud customer's responsibility in every service category?

Governing its identities, data, configuration choices, and lawful use. The exact technical boundary changes, but accountability does not vanish when infrastructure is outsourced.

What does a cloud service broker add?

Intermediation, aggregation, or management across cloud services. A broker may compare, combine, or govern services without owning their underlying infrastructure.

What is a regulator's cloud-security role?

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.

What is the cloud service provider's core responsibility?

Deliver the contracted cloud capabilities and secure the layers assigned to it. The service model and contract define the boundary.

What is orchestration in a cloud environment?

Coordinated automation of provisioning, configuration, scaling, and lifecycle actions across resources. It applies policy consistently across many components.

What capability does SaaS give the customer?

Use of a provider-run application. The customer mainly manages users, data, and allowed configuration rather than the platform beneath it.

Which four deployment models does NIST SP 800-145 define?

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.

How do portability and interoperability differ?

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.

What does a cloud service partner do?

Supports or enhances cloud service delivery, use, or assurance. Examples include auditors, integrators, and developers acting beside the customer and provider.

Who controls user entitlements inside a SaaS tenant?

The customer organization. The provider supplies the application and access mechanisms, but the customer decides which of its users need which privileges.

When is hybrid cloud a better description than multi-cloud?

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.

What problem does confidential computing address?

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.

When does blockchain add useful assurance to a cloud workflow?

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.

When does edge computing improve resilience but complicate security?

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.

What does reversibility require in a cloud design?

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.

What is the first security question before connecting IoT devices to a cloud service?

Can each device be uniquely identified, updated, constrained, and monitored throughout its lifecycle? Cheap connectivity does not offset unmanaged device risk.

What capability does PaaS give the customer?

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.

What is a practical cloud decision for quantum-related cryptographic risk today?

Inventory cryptographic dependencies and design for algorithm agility. Replace algorithms according to authoritative migration guidance rather than adopting unreviewed schemes.

Which SLA measure is useful only when paired with a clear measurement method and remedy?

Any availability or performance target. Define the service boundary, observation window, exclusions, data source, notification, and remedy before treating the number as assurance.

How should a team use a Well-Architected pattern, SANS security principles, or CSA enterprise architecture?

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.

What does a FIPS 140 validation establish?

That a named cryptographic module was validated against the stated standard and boundary. It does not prove the surrounding application uses the module safely.

Who normally patches the managed runtime in PaaS?

The cloud provider. The customer still owns secure application code, dependencies it supplies, data, identities, and configuration.

Who should approve a cloud data classification?

The accountable data owner. Security and privacy teams advise, while custodians implement the handling controls.

What should the cloud architect own in secure design?

The documented trust boundaries, security requirements, resilience choices, and responsibility mapping. Operations and product teams then implement and test those decisions.

What does DevSecOps change about security ownership?

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.

Which controls reduce container escape impact?

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.

Who should own a cloud service's business recovery requirements?

The business or service owner. Technical teams translate the owner's impact tolerance into RTO, RPO, architecture, and tests.

What capability does IaaS give the customer?

Provisioning of fundamental compute, storage, and network resources. The customer usually controls operating systems, workloads, and many network settings.

Which key-management design limits a cloud provider compromise from exposing customer data?

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.

What is the safer identity pattern for a cloud workload?

A short-lived, narrowly scoped workload identity. It avoids embedded long-lived credentials and supports rotation and traceability.

When can cryptographic erase sanitize cloud data?

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.

What is the first network control for limiting east-west movement between cloud workloads?

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.

Who normally patches a guest operating system in IaaS?

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.

What is the most important permission control for a serverless function?

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.

How does immutable infrastructure reduce configuration drift?

Replace changed instances from a controlled image instead of repairing them in place. The image pipeline, secrets, and state stores still need protection.

What turns a security baseline into an operating control?

Automated assessment plus timely remediation of deviations. A baseline document alone does not prevent drift.

What control keeps protection aligned as cloud data moves through its lifecycle?

Lifecycle-aware policy tied to classification and ownership. Access, encryption, retention, monitoring, and disposal should change with the data's state and purpose.

What makes a cloud recovery plan credible?

Regular restore, failover, dependency, and failback tests against business targets. A provider's availability claim does not prove the customer's service can recover.

What evidence should be checked first when evaluating a cloud provider?

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.

What should drive a cloud BC/DR design before products are selected?

A business impact analysis. It identifies critical services, dependencies, impact over time, and acceptable recovery targets.

Who is accountable for approving an AI model's intended cloud use?

The designated AI or business system owner. Model builders provide evidence, while risk, security, privacy, and legal roles challenge the use against policy.

What should be tested before accepting a provider's portability claim?

Export the data and configuration, rebuild elsewhere, and measure missing features, time, cost, and dependencies. Contract wording alone cannot prove reversibility.

What control most directly reduces hypervisor compromise risk for a customer?

Use a provider with strong isolation assurance, rapid patching, and evidence for the virtualization layer. The customer cannot harden a provider-managed hypervisor directly.

How should CBA and ROI inform a cloud recovery design after the BIA?

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.

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.

Автор Flashcards Open Source App

Вивчати цю колоду безкоштовно

Відкриється Nibomo, і ви зможете почати навчання.

Відомості про колоду

Картки: 340 карток
Версія: 1
Опубліковано: 27 серпня 2026 р.
Останнє оновлення: 10 вересня 2026 р.
Ліцензія: Common knowledge · CC0 1.0
Мови аудиторії: en
Предмет: Cloud security
Рівень: CCSP
Теги: ccsp-2026, d1-concept, d1-role, d1-decision, d1-control, d2-concept, d2-control, d2-decision, d2-role, d3-role, d3-concept, d3-control, d3-decision, d4-concept, d4-role, d4-control, d4-decision, d5-concept, d5-decision, d5-control, d5-role, d6-concept, d6-role, d6-control, d6-decision

Схожі колоди

Про цю колоду

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.

Картки в цій колоді

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

Abstract cloud infrastructure with layered security boundaries, connected control nodes, and an AI model graph.

340 карток