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.

Autor Flashcards Open Source App

Ucz się z tej talii za darmo

Otworzy się Nibomo, żeby od razu zacząć naukę.

Szczegóły talii

Karty: 340 kart
Wersja: 1
Opublikowano: 27 sierpnia 2026
Ostatnia aktualizacja: 10 września 2026
Licencja: Common knowledge · CC0 1.0
Języki odbiorców: en
Przedmiot: Cloud security
Poziom: CCSP
Tagi: 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

Podobne talie

O tej talii

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.

Karty w tej talii

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