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.

Informazioni su questo mazzo

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.

Carte in questo mazzo

  1. Carta 1

    Domanda

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

    Risposta

    It provides shared, configurable resources on demand with rapid provisioning and minimal provider interaction. A hosted server without those operating characteristics is not automatically a cloud.

  2. Carta 2

    Domanda

    What is the security significance of broad network access?

    Risposta

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

  3. Carta 3

    Domanda

    How do resource pooling and multi-tenancy differ?

    Risposta

    Resource pooling dynamically assigns shared capacity; multi-tenancy lets multiple customers use that shared environment with logical isolation. Pooling is the allocation model, while multi-tenancy is the customer-sharing model.

  4. Carta 4

    Domanda

    What separates elasticity from scalability?

    Risposta

    Elasticity adjusts capacity with demand; scalability is the ability to handle growth by adding or changing capacity. Elasticity stresses timely adjustment, often in both directions.

  5. Carta 5

    Domanda

    What does measured service provide?

    Risposta

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

  6. Carta 6

    Domanda

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

    Risposta

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

  7. Carta 7

    Domanda

    What does virtualization contribute to cloud computing?

    Risposta

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

  8. Carta 8

    Domanda

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

    Risposta

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

  9. Carta 9

    Domanda

    What does a cloud service broker add?

    Risposta

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

  10. Carta 10

    Domanda

    What is a regulator's cloud-security role?

    Risposta

    Set or enforce legal and regulatory obligations that apply to the service and its data. The customer must map those duties into provider selection, controls, and evidence.

  11. Carta 11

    Domanda

    What is the cloud service provider's core responsibility?

    Risposta

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

  12. Carta 12

    Domanda

    What is orchestration in a cloud environment?

    Risposta

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

  13. Carta 13

    Domanda

    What capability does SaaS give the customer?

    Risposta

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

  14. Carta 14

    Domanda

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

    Risposta

    Public, private, community, and hybrid cloud. Multi-cloud describes using more than one cloud provider or service environment; it is distinct from NIST's canonical four-model taxonomy.

  15. Carta 15

    Domanda

    How do portability and interoperability differ?

    Risposta

    Portability moves a workload or data between environments; interoperability lets different environments exchange and use information or services. One reduces switching friction, while the other supports cooperation.

  16. Carta 16

    Domanda

    What does a cloud service partner do?

    Risposta

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

  17. Carta 17

    Domanda

    Who controls user entitlements inside a SaaS tenant?

    Risposta

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

  18. Carta 18

    Domanda

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

    Risposta

    When the architecture deliberately combines distinct private and public environments. Multi-cloud focuses on using multiple cloud services or providers and may contain no private cloud.

  19. Carta 19

    Domanda

    What problem does confidential computing address?

    Risposta

    Protection of data while it is being processed. Hardware-backed trusted execution environments reduce exposure to the host or platform layer, but do not replace application controls.

  20. Carta 20

    Domanda

    When does blockchain add useful assurance to a cloud workflow?

    Risposta

    When multiple parties need a shared, tamper-evident record without relying on one writer. It does not make source data true, private, lawful, or immune to key and smart-contract failures.

  21. Carta 21

    Domanda

    When does edge computing improve resilience but complicate security?

    Risposta

    When local processing reduces central latency or dependency while distributing data, software, and physical exposure. The decision needs remote attestation, patching, inventory, and failure handling.

  22. Carta 22

    Domanda

    What does reversibility require in a cloud design?

    Risposta

    A practical way to exit or change providers while recovering data, configurations, dependencies, and needed evidence. A theoretical export button is not enough if the result cannot be used elsewhere.

  23. Carta 23

    Domanda

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

    Risposta

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

  24. Carta 24

    Domanda

    What capability does PaaS give the customer?

    Risposta

    Deployment of customer applications onto a provider-managed platform. The provider runs the underlying infrastructure and runtime, while the customer secures code, data, and configuration.

  25. Carta 25

    Domanda

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

    Risposta

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

  26. Carta 26

    Domanda

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

    Risposta

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

  27. Carta 27

    Domanda

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

    Risposta

    As structured design input mapped to the workload's risks, responsibilities, and evidence. A named framework guides decisions but does not prove that the resulting architecture is secure.

  28. Carta 28

    Domanda

    What does a FIPS 140 validation establish?

    Risposta

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

  29. Carta 29

    Domanda

    Who normally patches the managed runtime in PaaS?

    Risposta

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

  30. Carta 30

    Domanda

    Who should approve a cloud data classification?

    Risposta

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

  31. Carta 31

    Domanda

    What should the cloud architect own in secure design?

    Risposta

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

  32. Carta 32

    Domanda

    What does DevSecOps change about security ownership?

    Risposta

    It makes security a shared, automated part of delivery rather than a final external gate. Product teams still need independent challenge for high-risk decisions.

  33. Carta 33

    Domanda

    Which controls reduce container escape impact?

    Risposta

    Hardened runtimes, minimal privileges, trusted images, isolation boundaries, and prompt patching. Treat a container as a process boundary, not automatically as a security boundary equal to a separate host.

  34. Carta 34

    Domanda

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

    Risposta

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

  35. Carta 35

    Domanda

    What capability does IaaS give the customer?

    Risposta

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

  36. Carta 36

    Domanda

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

    Risposta

    Separate data from independently controlled encryption keys where the threat model requires it. Access policy, rotation, backup, and recovery for those keys matter as much as their location.

  37. Carta 37

    Domanda

    What is the safer identity pattern for a cloud workload?

    Risposta

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

  38. Carta 38

    Domanda

    When can cryptographic erase sanitize cloud data?

    Risposta

    When destroying the correct encryption key makes all protected copies computationally unreadable and the encryption implementation is trustworthy. Key copies, snapshots, and replicas must be in scope.

  39. Carta 39

    Domanda

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

    Risposta

    Explicit segmentation with deny-by-default rules. Identity-aware policy and traffic telemetry strengthen the boundary; geofencing can add a location condition but cannot replace it.

  40. Carta 40

    Domanda

    Who normally patches a guest operating system in IaaS?

    Risposta

    The cloud customer. The provider secures the underlying facilities and virtualization layer, while the customer manages the guest unless a separate managed service changes that boundary.

  41. Carta 41

    Domanda

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

    Risposta

    A dedicated least-privilege execution identity. Also restrict triggers, secrets, outbound access, and runtime duration; ephemeral execution does not erase external logs, queues, or data.

  42. Carta 42

    Domanda

    How does immutable infrastructure reduce configuration drift?

    Risposta

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

  43. Carta 43

    Domanda

    What turns a security baseline into an operating control?

    Risposta

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

  44. Carta 44

    Domanda

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

    Risposta

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

  45. Carta 45

    Domanda

    What makes a cloud recovery plan credible?

    Risposta

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

  46. Carta 46

    Domanda

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

    Risposta

    Evidence mapped to the organization's own requirements and risk criteria. Certifications help only when their scope, period, system, and exceptions cover the intended service.

  47. Carta 47

    Domanda

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

    Risposta

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

  48. Carta 48

    Domanda

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

    Risposta

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

  49. Carta 49

    Domanda

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

    Risposta

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

  50. Carta 50

    Domanda

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

    Risposta

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

  51. Carta 51

    Domanda

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

    Risposta

    CBA compares each option's lifecycle cost with expected benefit; ROI expresses the expected return relative to investment. Neither overrides mandatory duties or the BIA's approved impact tolerance.

  52. Carta 52

    Domanda

    What control helps validate training or detection data before AI use?

    Risposta

    Provenance, integrity checks, schema checks, and approval for the intended source. Statistical anomaly checks can add evidence but should not replace ownership.

  53. Carta 53

    Domanda

    What is the human reviewer's role in AI-assisted security operations?

    Risposta

    Validate consequential findings and actions before relying on them. Automation can rank and enrich signals, but the accountable human handles ambiguity and impact.

  54. Carta 54

    Domanda

    Why read an assurance report's scope before relying on its conclusion?

    Risposta

    The report may exclude the exact service, region, control, subservice, or period you need. Assurance cannot be extended beyond its stated boundary.

  55. Carta 55

    Domanda

    Which controls make model extraction harder at a cloud API?

    Risposta

    Strong access control, rate and budget limits, query monitoring, response minimization, and abuse detection. No single control removes the risk from a publicly queryable model.

  56. Carta 56

    Domanda

    Why is high predictive accuracy insufficient for a cloud data-science or AI model?

    Risposta

    The use can still create unacceptable legal, privacy, fairness, security, safety, or operational risk. Accuracy is one quality measure, not automatic authorization to deploy.

  57. Carta 57

    Domanda

    How should SOAR handle a high-impact containment action?

    Risposta

    Use explicit authorization, bounded playbooks, and human approval when impact or uncertainty is high. Automation should be reversible and fully logged.

  58. Carta 58

    Domanda

    When is Common Criteria evidence relevant to provider evaluation?

    Risposta

    When a specific evaluated product and assurance target match the component and threat being assessed. It does not certify an entire cloud service by association.

  59. Carta 59

    Domanda

    Which data lifecycle sequence is useful for cloud control planning?

    Risposta

    Create, store, use, share, archive, and destroy. Real data may move between phases, but each transition needs an owner and handling rule.

  60. Carta 60

    Domanda

    What is data dispersion in cloud computing?

    Risposta

    The distribution of data and copies across systems, regions, media, services, and providers. Replicas, caches, logs, snapshots, and backups all expand the control boundary.

  61. Carta 61

    Domanda

    What does a cloud data flow describe?

    Risposta

    Where data originates, moves, is transformed, is stored, and exits. A useful flow also names trust boundaries, actors, purposes, and protections.

  62. Carta 62

    Domanda

    How do object and volume storage differ?

    Risposta

    Object storage addresses data as objects with metadata; volume storage presents block-like storage to a host. Their access paths, sharing models, snapshots, and permission risks differ.

  63. Carta 63

    Domanda

    How does ephemeral storage differ from long-term storage?

    Risposta

    Ephemeral storage is tied to a short-lived workload or execution; long-term storage is designed to persist independently. Ephemeral does not mean automatically sanitized.

  64. Carta 64

    Domanda

    What is raw data storage?

    Risposta

    Storage of collected data before full cleaning, transformation, or enrichment. Its broad content and uncertain quality make isolation, discovery, provenance, and access control especially important.

  65. Carta 65

    Domanda

    What makes a data-flow map useful for control design?

    Risposta

    It names sources, destinations, transformations, actors, purposes, trust boundaries, and protections. Update it when architecture or processing changes.

  66. Carta 66

    Domanda

    What should decide whether data may move to another cloud region?

    Risposta

    Classification, purpose, residency and transfer rules, contract terms, threat model, and required controls. Region availability alone is not authorization.

  67. Carta 67

    Domanda

    Which storage type fits immutable, widely shared blobs better than a mounted transactional filesystem?

    Risposta

    Object storage. Use volume storage when the workload needs block-style filesystem or database access semantics.

  68. Carta 68

    Domanda

    A short-lived AI training node is terminated. Why can data risk remain?

    Risposta

    Ephemeral compute can leave snapshots, caches, logs, attached volumes, or provider-level remnants. Verify the full storage and key lifecycle, not only instance deletion.

  69. Carta 69

    Domanda

    What control exposes unknown cloud data stores before they bypass policy?

    Risposta

    Continuous asset and data discovery across accounts, regions, services, and shadow paths. Findings need ownership and remediation, not just inventory.

  70. Carta 70

    Domanda

    What security property does encryption primarily provide?

    Risposta

    Confidentiality against parties without the key. Integrity and authenticity require an appropriate authenticated mode or separate mechanism.

  71. Carta 71

    Domanda

    What does tokenization do?

    Risposta

    Replaces sensitive data with a non-sensitive token whose mapping is protected separately. The token can preserve application format while reducing where original data appears.

  72. Carta 72

    Domanda

    How do structured, semi-structured, and unstructured data differ?

    Risposta

    Structured data follows a fixed schema, semi-structured data carries flexible labels or structure, and unstructured data lacks a consistent field model. Discovery needs techniques suited to each form.

  73. Carta 73

    Domanda

    What is data masking?

    Risposta

    A transformation that hides selected data while preserving a usable shape or view. Reversible or weak masking is not anonymization.

  74. Carta 74

    Domanda

    What does Data Loss Prevention monitor or restrict?

    Risposta

    Sensitive-data movement or use across selected channels. DLP depends on discovery, classification, context, coverage, and tuned response.

  75. Carta 75

    Domanda

    What security property does a cryptographic hash support?

    Risposta

    Integrity by detecting change. A plain hash does not hide the input, prove who created it, or prevent guessing of low-entropy values.

  76. Carta 76

    Domanda

    What does Information Rights Management add beyond storage permissions?

    Risposta

    Persistent usage rules attached to protected content, such as view, print, copy, expiry, or revocation. Enforcement still depends on trusted identities, clients, and key services.

  77. Carta 77

    Domanda

    Where should application secrets be kept?

    Risposta

    In a managed secret store with narrow access, audit logs, rotation, and short-lived retrieval. Source code, images, and general configuration files are poor secret stores.

  78. Carta 78

    Domanda

    What is anonymization trying to achieve?

    Risposta

    Make data no longer reasonably linkable to an identifiable person. Re-identification risk must be assessed against auxiliary data and the release context.

  79. Carta 79

    Domanda

    Why separate key-custodian duties from data administration?

    Risposta

    To reduce the chance that one person can both reach ciphertext and independently unlock it. Separation of duties should also cover recovery and emergency access.

  80. Carta 80

    Domanda

    What control reduces dependence on provider-held encryption keys?

    Risposta

    Customer-controlled keys with independent policy and lifecycle management. The choice adds recovery, availability, rotation, and administrator risks that must be designed explicitly.

  81. Carta 81

    Domanda

    How can tokenization reduce exposure in an application database?

    Risposta

    Store tokens in routine workflows and isolate the token vault or mapping service. Access to detokenization should be rarer and more tightly logged.

  82. Carta 82

    Domanda

    How can a hash support evidence integrity?

    Risposta

    Record a strong hash at acquisition and verify it after each transfer or analysis step. Chain-of-custody records explain who handled the evidence and why.

  83. Carta 83

    Domanda

    What is the safer source for non-production test data?

    Risposta

    Synthetic or appropriately transformed data that meets the test need without exposing production identities. Validate re-identification risk before release.

  84. Carta 84

    Domanda

    What makes DLP enforcement practical instead of noisy?

    Risposta

    Accurate discovery and classification, contextual rules, staged response, tuned exceptions, and incident ownership. Blocking every pattern match can disrupt work without reducing real leakage.

  85. Carta 85

    Domanda

    What enables IRM revocation after a file leaves its original repository?

    Risposta

    A trusted client that checks current rights and can no longer obtain the needed key or license. Offline copies and screenshots remain boundary cases.

  86. Carta 86

    Domanda

    How should cloud data discovery handle false positives?

    Risposta

    Route uncertain matches for risk-based validation and tune detection with evidence. Silently discarding them hides coverage gaps; blocking them all creates operational failure.

  87. Carta 87

    Domanda

    What keeps certificates trustworthy after issuance?

    Risposta

    Inventory, protected private keys, renewal, revocation, validation, and monitored expiry. Issuing a certificate is only the start of its lifecycle.

  88. Carta 88

    Domanda

    What is envelope encryption?

    Risposta

    Encrypt data with a data-encryption key, then protect that key with a separate key-encryption key. Rotating or rewrapping the key-encryption key can protect existing data-encryption keys without re-encrypting payload data; replacing a data-encryption key may require payload re-encryption.

  89. Carta 89

    Domanda

    What is data classification?

    Risposta

    Assignment of a sensitivity or business category that drives handling requirements. The category should reflect impact, law, contract, and business need.

  90. Carta 90

    Domanda

    When is tokenization preferable to ordinary encryption?

    Risposta

    When workflows can use a surrogate while original values stay in a tightly isolated mapping service. Encryption is better when authorized systems must recover data directly with keys.

  91. Carta 91

    Domanda

    Should a password be encrypted or hashed for verification?

    Risposta

    Hash it with a password-specific salted, slow derivation function. Reversible encryption creates unnecessary recovery of the original password.

  92. Carta 92

    Domanda

    When is masking insufficient for a public dataset release?

    Risposta

    When remaining fields or external data can reasonably re-identify people. Public release needs a defensible anonymization assessment, not cosmetic redaction.

  93. Carta 93

    Domanda

    Why should DLP not be the only control against cloud exfiltration?

    Risposta

    It sees only covered channels and recognized content. Least privilege, segmentation, egress control, encryption, monitoring, and response reduce gaps.

  94. Carta 94

    Domanda

    When is IRM more useful than a repository access control list?

    Risposta

    When usage restrictions must follow a file beyond the original repository. If data never leaves a controlled service, native authorization may be simpler and stronger.

  95. Carta 95

    Domanda

    Why perform discovery before broad classification enforcement?

    Risposta

    You need to know what data exists and where it lives before applying reliable labels and controls. Enforcement on an incomplete inventory leaves blind spots.

  96. Carta 96

    Domanda

    What should trigger data reclassification?

    Risposta

    A change in content, use, law, contract, business impact, aggregation, or identifiability. Review should also occur on a defined schedule.

  97. Carta 97

    Domanda

    Why rotate encryption keys?

    Risposta

    To limit exposure, meet policy, and replace keys after age, role, algorithm, or compromise changes. Rotation must preserve authorized access to older data until it is safely reprotected or retired.

  98. Carta 98

    Domanda

    Who sets a cloud dataset's business classification?

    Risposta

    The accountable data owner. Automated tools can propose labels, but the owner resolves business context and exceptions.

  99. Carta 99

    Domanda

    How does a data label differ from a classification policy?

    Risposta

    The label marks a specific asset; the policy defines what the category means and how it must be handled. Labels without enforcement are only metadata.

  100. Carta 100

    Domanda

    What is a data steward responsible for?

    Risposta

    Day-to-day quality, definition, and policy consistency for data. A steward supports the owner but does not replace the owner's accountability.

  101. Carta 101

    Domanda

    How do retention and archiving differ?

    Risposta

    Retention states how long data must or may be kept; archiving moves data into a managed long-term state. Archived data remains subject to access, integrity, discovery, and deletion rules.

  102. Carta 102

    Domanda

    What does a data controller decide?

    Risposta

    The purposes and essential means of processing personal data. The exact legal definition depends on the applicable law.

  103. Carta 103

    Domanda

    When should a derived dataset inherit its source classification?

    Risposta

    By default, until an accountable owner proves the transformation changed sensitivity. Aggregation can reduce or increase risk depending on content and linkability.

  104. Carta 104

    Domanda

    How should classification labels affect cloud controls?

    Risposta

    Drive access, encryption, sharing, location, retention, monitoring, and deletion policy. Enforcement should follow the label across supported copies and transformations.

  105. Carta 105

    Domanda

    What does a legal hold do?

    Risposta

    Suspends normal deletion for information relevant to a legal or regulatory matter. It preserves authorized access and evidence until the hold is released.

  106. Carta 106

    Domanda

    What should a privacy role contribute to cloud data design?

    Risposta

    Purpose, minimization, transparency, rights, transfer, retention, and impact requirements. Security protects data, while privacy also asks whether processing should occur and under what conditions.

  107. Carta 107

    Domanda

    What control turns a retention schedule into repeatable cloud behavior?

    Risposta

    Policy-driven lifecycle automation with holds, approvals, exceptions, and audit evidence. Automation must cover replicas and backups where the platform supports it.

  108. Carta 108

    Domanda

    What is a data custodian responsible for?

    Risposta

    Implementing and operating the technical handling controls. Storage, backup, access, logging, and deletion are typical custody duties.

  109. Carta 109

    Domanda

    Who should own the retention schedule?

    Risposta

    The records or information-governance function with legal and business input. Technology teams implement the approved schedule and evidence.

  110. Carta 110

    Domanda

    What does a data processor do?

    Risposta

    Processes personal data for a controller under documented instructions. Using the data for its own new purpose may change the role and obligations.

  111. Carta 111

    Domanda

    What proves a cloud deletion request was completed responsibly?

    Risposta

    Provider and customer evidence tied to the asset, method, scope, time, and remaining copies. A successful API response alone may not cover backups, replicas, or exported data.

  112. Carta 112

    Domanda

    Which controls protect a long-term cloud archive?

    Risposta

    Restricted access, durable integrity checks, format and key preservation, redundancy, retention policy, and tested retrieval. An archive that cannot be read or trusted has failed its purpose.

  113. Carta 113

    Domanda

    Who should approve a training dataset and model version for production?

    Risposta

    The accountable model or system owner using evidence from data, security, privacy, and validation roles. Approval must bind the exact versions and intended use.

  114. Carta 114

    Domanda

    Which event fields most often establish accountability for cloud data access?

    Risposta

    Trusted identity, action, target, result, timestamp, source context, and relevant network or location data. Collect only attributes needed for the security, legal, and privacy purpose.

  115. Carta 115

    Domanda

    Why synchronize clocks across cloud evidence sources?

    Risposta

    To correlate events into a defensible timeline. Record time source, zone, drift, and collection context when precision matters.

  116. Carta 116

    Domanda

    Which risk is present when model outputs reveal features of sensitive training records?

    Risposta

    Model inversion or related privacy inference. Data minimization, privacy testing, output controls, and access limits reduce exposure.

  117. Carta 117

    Domanda

    Who authorizes and scopes a legal hold?

    Risposta

    An authorized legal or records function. Cloud administrators implement it without deciding the legal scope themselves.

  118. Carta 118

    Domanda

    What must AI dataset validation check besides file integrity?

    Risposta

    Source authority, consent or permitted use, representativeness, quality, labeling, poisoning indicators, and intended-use fit. A matching checksum only proves the bytes did not change after that checkpoint.

  119. Carta 119

    Domanda

    Why is an archive not a substitute for a recovery backup?

    Risposta

    An archive optimizes long-term preservation and retrieval; a backup supports restoration after loss or corruption. One system can sometimes serve both only if it meets both control sets and tests.

  120. Carta 120

    Domanda

    What protects AI dataset and model provenance?

    Risposta

    Versioned inventories, signed or hashed artifacts, controlled pipelines, approval records, and lineage from source to deployment. Bind validation results to the exact artifact versions.

  121. Carta 121

    Domanda

    Which context should be omitted from a data event log?

    Risposta

    Data that is unnecessary for the defined security, accountability, or legal purpose. More logging can create privacy, cost, and breach risk without improving evidence.

  122. Carta 122

    Domanda

    What happens when a valid legal hold conflicts with scheduled deletion?

    Risposta

    The authorized hold suspends deletion for the in-scope data. Keep access limited, document the exception, and resume policy when the hold is released.

  123. Carta 123

    Domanda

    What adds non-repudiation evidence beyond a plain event log?

    Risposta

    Strong identity binding, protected timestamps, integrity controls, and controlled custody. The strength depends on the whole evidence process, not a single hash field.

  124. Carta 124

    Domanda

    What privacy question does a membership-inference attack answer?

    Risposta

    Whether a particular record was likely part of a model's training data. Limit exposed confidence, query abuse, overfitting, and unnecessary sensitive training data.

  125. Carta 125

    Domanda

    What is the clearest sign that training-data poisoning controls failed?

    Risposta

    Untrusted or manipulated examples changed model behavior or inserted a hidden trigger. Investigate provenance, pipeline access, validation, and the exact affected versions.

  126. Carta 126

    Domanda

    What is the strongest first step when an AI use case asks for every available customer field?

    Risposta

    Reduce collection to data necessary for the approved purpose. Minimization lowers privacy, poisoning, access, retention, and breach exposure before technical controls are added.

  127. Carta 127

    Domanda

    What is the cloud network team's primary security role?

    Risposta

    Implement approved segmentation, routing, edge protection, secure connectivity, and network telemetry. Application teams still define workload access needs.

  128. Carta 128

    Domanda

    Which layers make up a cloud infrastructure trust stack?

    Risposta

    Physical facilities, network, compute, storage, virtualization, and management services. A workload inherits dependencies and failure modes from every layer beneath or beside it.

  129. Carta 129

    Domanda

    How do the management plane and data plane differ?

    Risposta

    The management plane configures and governs resources; the data plane carries or processes workload traffic and data. Compromise of the management plane can change many data-plane controls at once.

  130. Carta 130

    Domanda

    What is a trust boundary in cloud architecture?

    Risposta

    A point where identity, control, ownership, or assurance changes. Data crossing it needs an explicit policy, validation, and protected channel.

  131. Carta 131

    Domanda

    Who owns a customer's cloud network and identity configuration?

    Risposta

    The customer for the configuration choices it controls. Provider defaults and guardrails help, but do not approve the customer's architecture.

  132. Carta 132

    Domanda

    What logical control prevents one tenant from reaching another tenant's resources?

    Risposta

    Enforced tenant partitioning across identity, network, compute, storage, and management paths. Test the negative boundary, not only valid access.

  133. Carta 133

    Domanda

    Why is the cloud management plane a high-value target?

    Risposta

    It can create, modify, expose, or destroy many resources through one privileged interface. Protect it more strongly than routine workload access.

  134. Carta 134

    Domanda

    What limits lateral movement after one cloud workload is compromised?

    Risposta

    Microsegmentation with identity-aware, least-privilege communication policy. Monitor denied and unusual flows to find attempted spread.

  135. Carta 135

    Domanda

    How does infrastructure as code improve control assurance?

    Risposta

    It makes configuration reviewable, repeatable, testable, and traceable. Protect the repository, pipeline, state, modules, and deployment identity.

  136. Carta 136

    Domanda

    How should a team verify an infrastructure control still works?

    Risposta

    Test its intended outcome with current evidence and representative failure or attack conditions. Configuration presence alone does not prove effectiveness.

  137. Carta 137

    Domanda

    What security boundary should virtualization create between tenants?

    Risposta

    Strong isolation of compute, memory, storage, network, and management operations. Shared hardware still creates side-channel, escape, and noisy-neighbor considerations.

  138. Carta 138

    Domanda

    Which controls should protect cloud management-plane access?

    Risposta

    Phishing-resistant MFA, privileged access management, separate admin identities, conditional access, least privilege, and immutable logging. Restrict source networks where practical.

  139. Carta 139

    Domanda

    How do type 1 and type 2 hypervisors differ?

    Risposta

    A type 1 hypervisor runs directly on hardware; a type 2 hypervisor runs on a host operating system. The extra host layer changes attack surface and operational use.

  140. Carta 140

    Domanda

    Who secures the public cloud facility and physical host?

    Risposta

    The cloud provider. Customers still evaluate the provider's physical assurance and design their service around disclosed locations and failure domains.

  141. Carta 141

    Domanda

    What protects a cloud AI training cluster from unrelated tenant traffic?

    Risposta

    Dedicated identities, microsegmentation, controlled data paths, hardened images, and monitored management access. Accelerator scheduling and storage paths belong in the boundary.

  142. Carta 142

    Domanda

    When is packet capture useful in cloud infrastructure?

    Risposta

    When network-level detail is needed and collection is lawful, technically available, scoped, and protected. Flow logs may be safer and sufficient for many investigations.

  143. Carta 143

    Domanda

    Which control protects detached cloud volumes and snapshots?

    Risposta

    Encryption with governed keys plus explicit access policy. Inventory and delete orphaned copies because detachment does not remove their data.

  144. Carta 144

    Domanda

    Why correlate infrastructure logs across layers?

    Risposta

    To connect identity, management, network, host, and workload events into one incident path. Preserve original records and normalization context.

  145. Carta 145

    Domanda

    What is a platform owner's responsibility for tenant isolation?

    Risposta

    Configure, patch, monitor, and test the shared platform so one workload cannot cross its authorized boundary. Consumers must use the platform's isolation features correctly.

  146. Carta 146

    Domanda

    When should an AI training cluster use stronger isolation than ordinary batch compute?

    Risposta

    When valuable models, sensitive datasets, untrusted code, or high-cost accelerators raise confidentiality, integrity, or exhaustion risk. Match isolation to the workload threat model.

  147. Carta 147

    Domanda

    What does an HSM protect in cloud infrastructure?

    Risposta

    Cryptographic keys and operations inside a hardened, policy-controlled boundary. An HSM does not decide whether the requesting workload is authorized unless surrounding policy enforces it.

  148. Carta 148

    Domanda

    What is a failure domain?

    Risposta

    A set of components likely to fail together because they share a dependency. Regions, zones, racks, power feeds, control services, or software versions can define one.

  149. Carta 149

    Domanda

    A volume is deleted but its snapshots remain. Is the data gone?

    Risposta

    No. The snapshots are separate retained copies. Apply inventory, retention, hold, encryption-key, and deletion policy to every snapshot and replica.

  150. Carta 150

    Domanda

    How should a platform reduce virtualization escape risk?

    Risposta

    Minimize and patch the virtualization stack, isolate management interfaces, restrict device exposure, monitor anomalies, and contain workloads by risk. Stronger workload boundaries may be needed for hostile tenants.

  151. Carta 151

    Domanda

    What is the first response to an internet-exposed cloud management endpoint?

    Risposta

    Remove unnecessary public reachability, then enforce strong identity and monitored privileged access. A hidden URL or uncommon port is not a control.

  152. Carta 152

    Domanda

    What is the facilities team's role in a private cloud data center?

    Risposta

    Operate physical access, power, cooling, fire protection, and environmental monitoring. Security requirements should define evidence and escalation for those systems.

  153. Carta 153

    Domanda

    Which site-location condition creates direct legal exposure for a cloud workload?

    Risposta

    The jurisdictions that can reach the facility, operator, customers, or data. Cost, hazards, utilities, connectivity, workforce, and physical threats require separate location analysis.

  154. Carta 154

    Domanda

    How does diverse pathway connectivity improve resilience?

    Risposta

    It prevents one cable route, conduit, carrier handoff, or excavation from cutting every link. Verify physical diversity rather than relying on different circuit names.

  155. Carta 155

    Domanda

    When does building a private data center make more sense than buying cloud capacity?

    Risposta

    When requirements for control, latency, sovereignty, specialized hardware, or long-term economics outweigh the build and operating burden. Compare full lifecycle cost and resilience, not purchase price alone.

  156. Carta 156

    Domanda

    Which physical controls protect cloud hardware from unauthorized handling?

    Risposta

    Zoned access, least privilege, identity checks, surveillance, visitor controls, alarms, and custody records. The strength should match asset and data impact.

  157. Carta 157

    Domanda

    What power design reduces a data center's single-point risk?

    Risposta

    Independent feeds, conditioned distribution, UPS capacity, generators, fuel plans, and tested transfer. Maintenance paths must preserve the intended redundancy.

  158. Carta 158

    Domanda

    What should environmental monitoring detect in a data center?

    Risposta

    Temperature, humidity, airflow, water, smoke, power, and equipment conditions that threaten service. Alerts need thresholds, escalation, and tested response.

  159. Carta 159

    Domanda

    How does resilience differ from simple redundancy?

    Risposta

    Redundancy adds alternatives; resilience keeps or restores acceptable service despite disruption. Redundant components can still share one failure domain or bad configuration.

  160. Carta 160

    Domanda

    Which on-premises physical control remains a customer duty when workloads move to public cloud?

    Risposta

    Protection of customer-controlled offices, endpoints, network links, and any retained equipment. The provider's data-center controls do not secure the customer's physical environment.

  161. Carta 161

    Domanda

    What are the core outputs of an infrastructure risk assessment?

    Risposta

    Prioritized risks tied to assets, threats, vulnerabilities, likelihood, impact, existing controls, and owners. The output should lead to treatment and follow-up.

  162. Carta 162

    Domanda

    Who may accept residual infrastructure risk?

    Risposta

    The authorized business risk owner, not the engineer who found it. Acceptance should state scope, duration, rationale, and review trigger.

  163. Carta 163

    Domanda

    How do a threat, vulnerability, and risk differ?

    Risposta

    A threat can cause harm, a vulnerability is a weakness it may exploit, and risk combines uncertain harm with business impact. A weakness without relevant exposure may be lower priority.

  164. Carta 164

    Domanda

    What reveals that two supposedly redundant cloud systems share fate?

    Risposta

    They depend on the same control plane, account, region, identity service, network path, software defect, operator, or key. Model those dependencies before counting redundancy.

  165. Carta 165

    Domanda

    What does a security control owner do?

    Risposta

    Ensures an assigned control is designed, implemented, evidenced, monitored, and corrected. The role may coordinate several technical operators.

  166. Carta 166

    Domanda

    Which risk treatment options should a cloud team recognize?

    Risposta

    Avoid, mitigate, transfer or share, and accept. Treatment changes exposure or ownership; it does not erase accountability.

  167. Carta 167

    Domanda

    What is a recovery service level?

    Risposta

    The minimum service capacity or functionality that must be restored, often stated as a percentage of normal service. RSL defines how much service must work; RTO sets the time limit, while RPO sets the maximum data-loss interval.

  168. Carta 168

    Domanda

    What makes a machine image trustworthy for cloud deployment?

    Risposta

    Known provenance, minimal contents, current patches, signed or verified integrity, vulnerability results, and controlled promotion. Revalidate it when dependencies age.

  169. Carta 169

    Domanda

    When do multiple availability zones materially improve resilience?

    Risposta

    When the service, data, network, identities, and operations can continue after one zone and its shared dependencies fail. Merely placing instances in two zones is not a tested design.

  170. Carta 170

    Domanda

    What should determine the strength of an infrastructure security control?

    Risposta

    The asset impact, threat, vulnerability, exposure, legal duties, and risk tolerance. Use control frameworks as structured input, not as an automatic one-size baseline.

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

    340 carte

    CCSP 2026 Flashcards: August Exam Outline Review

    Studia questo mazzo gratis

    Nibomo si apre e puoi iniziare a studiare.

  171. Carta 171

    Domanda

    Which layered controls improve availability against cloud DDoS?

    Risposta

    Provider edge absorption, rate controls, resilient scaling, caching, WAF or protocol filtering, and an exercised response plan. Scaling alone can turn attack traffic into cost exhaustion.

  172. Carta 172

    Domanda

    A cloud contract shifts breach costs to a provider. Has the risk been removed?

    Risposta

    No. Financial risk may be transferred, while operational, legal, reputational, and customer harm can remain. Retained exposure still needs mitigation and acceptance.

  173. Carta 173

    Domanda

    Why map dependencies across compute, storage, and network services?

    Risposta

    A resilient application can still fail when a shared supporting service fails. Dependency maps expose hidden single points, circular recovery steps, and shared fate.

  174. Carta 174

    Domanda

    What does RPO constrain in an infrastructure recovery design?

    Risposta

    The maximum acceptable data-loss interval measured backward from disruption. It drives backup or replication frequency and consistency choices.

  175. Carta 175

    Domanda

    What should trigger automated failover?

    Risposta

    Reliable health evidence that the primary cannot meet the service objective, with safeguards against split-brain and false triggers. Manual approval may remain appropriate for ambiguous high-impact cases.

  176. Carta 176

    Domanda

    When is an IPS preferable to an IDS?

    Risposta

    When inline blocking is justified, tested, and safe for the traffic and availability requirements. Use detection-only when false positives or inline failure would create unacceptable impact.

  177. Carta 177

    Domanda

    What makes residual infrastructure risk ready for acceptance?

    Risposta

    A clear scenario, affected assets, existing controls, likelihood and impact, owner, duration, alternatives, and review trigger. Vague acceptance is not governance.

  178. Carta 178

    Domanda

    What makes a cloud backup resistant to account compromise?

    Risposta

    Separate administration, immutable or offline retention, encryption, protected deletion, and tested restore. Keep recovery credentials outside the routine production trust path.

  179. Carta 179

    Domanda

    What does a BC/DR coordinator own during cloud recovery planning?

    Risposta

    The cross-team plan, exercises, dependencies, contacts, evidence, and follow-up. Service owners still set business priorities and targets.

  180. Carta 180

    Domanda

    Which recovery design supports a near-zero RPO?

    Risposta

    Synchronous or otherwise strongly consistent replication across independent failure domains, if latency and shared-fate limits are acceptable. Backups still protect against corruption and deletion.

  181. Carta 181

    Domanda

    Which overlooked dependency can stop users from reaching replicated application servers after failover?

    Risposta

    The identity service. Recovery planning should also cover DNS, keys, secrets, routes, data stores, quotas, and external services.

  182. Carta 182

    Domanda

    Why test restore separately from backup completion?

    Risposta

    A completed backup may be corrupt, incomplete, inaccessible, or too slow for the target. Restore testing proves usability and measures recovery performance.

  183. Carta 183

    Domanda

    Why plan failback before declaring a DR design complete?

    Risposta

    Returning to the preferred environment can create another outage, conflict, or data loss. Define authority, synchronization, validation, rollback, and communication.

  184. Carta 184

    Domanda

    Which design choice most directly supports a short RTO?

    Risposta

    Pre-provisioned or rapidly deployable recovery capacity with automated, tested orchestration. Data, identities, network, dependencies, and operators must be ready too.

  185. Carta 185

    Domanda

    What should application-security awareness change in a cloud team?

    Risposta

    Daily design and delivery decisions, not just annual quiz results. Use role-specific OWASP, ASVS, SANS Top 25, and LLM-risk examples as practical boundaries, then reinforce them with real defects.

  186. Carta 186

    Domanda

    What makes an SDLC a secure SDLC?

    Risposta

    Security requirements, design analysis, implementation controls, verification, release evidence, maintenance, and retirement are built into the lifecycle. A final penetration test alone is not a lifecycle.

  187. Carta 187

    Domanda

    How do functional and non-functional security requirements differ?

    Risposta

    Functional requirements specify security behavior; non-functional requirements set qualities such as availability, performance, resilience, or assurance. Both need measurable acceptance criteria.

  188. Carta 188

    Domanda

    Who turns business needs into testable application security requirements?

    Risposta

    The product or business owner with security, privacy, legal, and engineering input. Requirements need an accountable owner and acceptance evidence.

  189. Carta 189

    Domanda

    How should a security requirement remain visible through delivery?

    Risposta

    Trace it to design decisions, code or configuration, tests, approval, and operating evidence. Untraceable requirements are easy to drop during change.

  190. Carta 190

    Domanda

    What is the purpose of threat modeling?

    Risposta

    Identify likely abuse paths and design mitigations before or during development. Keep the model tied to assets, trust boundaries, architecture changes, and evidence.

  191. Carta 191

    Domanda

    What makes developer security training actionable?

    Risposta

    Role-specific examples, secure alternatives, practice in the delivery toolchain, and feedback from real defects. Refresh it as platforms and threats change.

  192. Carta 192

    Domanda

    Should agile delivery remove formal security gates?

    Risposta

    No. It should make them smaller, earlier, automated where reliable, and tied to risk. High-impact changes can still require independent approval.

  193. Carta 193

    Domanda

    Which cloud-specific application risks need explicit SDLC decisions before coding?

    Risposta

    Shared-technology exposure, provider insiders, limited visibility or control, and legal or jurisdiction boundaries. Record the provider boundary, evidence, data location, isolation, and compensating controls.

  194. Carta 194

    Domanda

    How do federation and SSO differ?

    Risposta

    Federation establishes trust across identity domains; SSO lets a user authenticate once for multiple services. Federation can enable SSO, but the concepts are not identical.

  195. Carta 195

    Domanda

    What is a developer's responsibility in secure cloud delivery?

    Risposta

    Use approved patterns, validate inputs and outputs, protect secrets, handle errors safely, review dependencies, and fix findings. Security tools support that judgment rather than replace it.

  196. Carta 196

    Domanda

    What should a peer security reviewer verify?

    Risposta

    That the change preserves requirements, trust boundaries, authorization, data handling, failure behavior, and evidence. Review the actual diff and deployment effect, not only style.

  197. Carta 197

    Domanda

    What is the application security architect accountable for?

    Risposta

    Security patterns, trust boundaries, threat decisions, control integration, and documented exceptions. Teams share implementation, but architecture needs coherent ownership.

  198. Carta 198

    Domanda

    Which threat categories does STRIDE prompt a team to examine?

    Risposta

    Spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege. It is a coverage aid, not a risk score.

  199. Carta 199

    Domanda

    What secure-coding rule most directly prevents broken object authorization?

    Risposta

    Check the current subject's permission for the specific object on every request. ASVS or SAFECode guidance can structure assurance, but hiding identifiers or checking only authentication is insufficient.

  200. Carta 200

    Domanda

    What should a secret-scanning gate do when it finds a real credential?

    Risposta

    Block exposure, revoke or rotate the credential, remove it from reachable history, and investigate use. Deleting the latest line does not invalidate copied history.

  201. Carta 201

    Domanda

    How does protected version control support software assurance?

    Risposta

    It creates tamper-evident, access-controlled history for reviewed code and configuration changes. Protect references from unauthorized rewrite, retain audit logs, control bypass, and bind signed artifacts to approved releases; content-addressed commits alone do not make branch history immutable.

  202. Carta 202

    Domanda

    Which threat-model method is the simplest checklist for threat categories at trust boundaries?

    Risposta

    STRIDE. Use a process-centered method when business impact, attacker paths, and staged analysis need deeper treatment.

  203. Carta 203

    Domanda

    What is an abuse case?

    Risposta

    A description of how an actor could misuse a feature or violate a security goal. It turns attacker intent into testable defensive behavior.

  204. Carta 204

    Domanda

    Why should a team avoid treating DREAD scores as objective truth?

    Risposta

    Its ratings are judgment-based and can create false precision. Document evidence, assumptions, impact, and uncertainty instead of relying on one number.

  205. Carta 205

    Domanda

    How do SAST and DAST differ?

    Risposta

    SAST examines code or compiled artifacts without running the full application; DAST probes a running application from the outside. They find different classes of weakness.

  206. Carta 206

    Domanda

    What does Software Composition Analysis examine?

    Risposta

    Third-party components, versions, licenses, and known vulnerability or policy data. It does not prove that a dependency is safe in context or detect every malicious package.

  207. Carta 207

    Domanda

    When should a cloud application's threat model be updated?

    Risposta

    When trust boundaries, data, identities, dependencies, deployment, features, or threats materially change. Periodic review catches slow drift.

  208. Carta 208

    Domanda

    How do black-box and white-box security testing differ?

    Risposta

    Black-box testing uses external behavior with little internal knowledge; white-box testing uses code, design, or configuration knowledge. Gray-box testing combines partial knowledge with external interaction.

  209. Carta 209

    Domanda

    What should a CI/CD security gate block?

    Risposta

    A defined, evidence-based release condition such as an exposed secret, failed critical control, unapproved artifact, or unacceptable vulnerability. Keep exceptions explicit, owned, and time-bounded.

  210. Carta 210

    Domanda

    When is PASTA or ATASM more useful than a short threat checklist?

    Risposta

    When the team needs a structured path from business objectives and architecture to attacker behavior, attack surfaces, and mitigations. Match method depth to decision risk.

  211. Carta 211

    Domanda

    Where does SAST provide the earliest useful feedback?

    Risposta

    During coding and pull-request review, before deployment. Tune rules, confirm reachability and context, and fix root causes rather than chasing raw counts.

  212. Carta 212

    Domanda

    When is IAST worth adding to a cloud test pipeline?

    Risposta

    When representative automated tests exist and runtime path-to-code insight will improve triage. Without exercised paths, instrumentation has little to observe.

  213. Carta 213

    Domanda

    How should an application handle LLM output before passing it to a browser, shell, database, or tool?

    Risposta

    Treat it as untrusted data and validate, encode, constrain, or approve it for the destination. Model fluency is not a security guarantee.

  214. Carta 214

    Domanda

    What should an abuse-case test assert for a sensitive workflow?

    Risposta

    The application safely rejects or contains a realistic misuse path and leaves useful evidence. Test rate, sequence, privilege, data, and failure-state abuse where relevant.

  215. Carta 215

    Domanda

    What environment makes DAST results most useful?

    Risposta

    A representative running deployment with safe test data, reachable paths, and observable results. Production testing needs explicit authorization and safeguards.

  216. Carta 216

    Domanda

    Who owns risk from a third-party software component?

    Risposta

    The organization that chooses and operates it. The supplier supplies evidence and remediation, but outsourcing the component does not outsource customer accountability.

  217. Carta 217

    Domanda

    How do an SBOM and SCA work together?

    Risposta

    SCA identifies component and policy findings; an SBOM records the released component inventory. Bind both to the exact artifact and update risk when new information appears.

  218. Carta 218

    Domanda

    What does artifact signing protect in a software supply chain?

    Risposta

    Integrity and authenticated provenance of the signed artifact. Verification policy must also trust the signer, build path, and release authorization.

  219. Carta 219

    Domanda

    What makes open-source software validated for a cloud application?

    Risposta

    Its source, release, integrity, dependencies, license, maintenance, vulnerabilities, and intended use have been assessed. Open code is inspectable, not automatically safe.

  220. Carta 220

    Domanda

    Which cloud application control validates XML message structure before processing?

    Risposta

    An XML firewall. A WAF filters web traffic, an API gateway applies API-facing policy, DAM monitors database activity, and a load balancer distributes traffic.

  221. Carta 221

    Domanda

    What authorization check belongs behind every sensitive API operation?

    Risposta

    A server-side decision for the current identity, action, object, tenant, and context. Gateway authentication alone cannot decide application-level ownership.

  222. Carta 222

    Domanda

    How should an API treat untrusted input?

    Risposta

    Validate type, structure, size, range, encoding, and allowed semantics before use. Reject unexpected fields where ambiguity or mass assignment creates risk.

  223. Carta 223

    Domanda

    What is an Identity Provider responsible for in federation?

    Risposta

    Authenticating subjects and issuing trustworthy identity assertions under agreed policy. The relying application still authorizes each requested action.

  224. Carta 224

    Domanda

    What does sandboxing add to cloud application security?

    Risposta

    A constrained execution boundary for untrusted or risky code and content. Restrict identity, network, files, secrets, time, and compute outside the sandbox too.

  225. Carta 225

    Domanda

    What should block adoption of a third-party software component?

    Risposta

    Unacceptable provenance, integrity, vulnerability, maintenance, license, access, or exit risk. Popularity and a clean scan do not settle supplier risk.

  226. Carta 226

    Domanda

    Which test perspective should verify hidden authorization logic?

    Risposta

    White-box review and testing, supported by black-box attempts to cross the boundary. Internal knowledge finds code paths; external tests confirm observable enforcement.

  227. Carta 227

    Domanda

    Which practice verifies that a cloud release consistently meets defined quality and security criteria?

    Risposta

    Quality Assurance (QA). It plans and tracks repeatable reviews, tests, acceptance evidence, defect handling, and process improvement across delivery.

  228. Carta 228

    Domanda

    Which IAM controls reduce takeover of a federated cloud account?

    Risposta

    Strong MFA, trusted federation configuration, short sessions, conditional access, lifecycle automation, and monitored privilege. Secure both the IdP and relying service.

  229. Carta 229

    Domanda

    What is the safest response when retrieved content tells an LLM to ignore system rules?

    Risposta

    Treat the instruction as untrusted data, preserve higher-priority policy, and prevent unauthorized tool or data access. Input filtering alone cannot eliminate prompt injection.

  230. Carta 230

    Domanda

    How should an LLM application reduce sensitive information disclosure?

    Risposta

    Minimize prompt and training data, enforce retrieval authorization, redact where justified, constrain outputs, and test leakage. A system prompt telling the model to keep secrets is not sufficient.

  231. Carta 231

    Domanda

    A model repository account is compromised and a backdoored model is published. Which risks overlap?

    Risposta

    Supply-chain compromise and data or model poisoning. Pin trusted versions, verify provenance and signatures, scan safely, validate behavior, and control promotion.

  232. Carta 232

    Domanda

    What identity should one microservice use to call another?

    Risposta

    A distinct, short-lived workload identity with least-privilege authorization. Avoid sharing broad static credentials across services.

  233. Carta 233

    Domanda

    How should an agentic LLM be constrained before it can delete cloud resources?

    Risposta

    Give it minimal scoped tools, validate arguments, require approval for destructive actions, enforce budgets, and log every decision and result. Capability should match the smallest authorized task.

  234. Carta 234

    Domanda

    Should a system prompt be treated as a secret control boundary?

    Risposta

    No. Design as if instructions may be exposed. Keep credentials and authorization outside the prompt, minimize sensitive details, and enforce policy in trusted code.

  235. Carta 235

    Domanda

    What is the main risk of weak authorization in a shared vector store?

    Risposta

    Retrieval can cross tenant or user boundaries and expose embeddings, documents, or poisoned context. Partition, authorize, validate provenance, and monitor ingestion and queries.

  236. Carta 236

    Domanda

    When does a CASB add value beside an IdP?

    Risposta

    When the organization needs visibility or policy over cloud-service use, data movement, sessions, or unmanaged access beyond authentication. The IdP establishes identity; the CASB governs selected cloud interactions.

  237. Carta 237

    Domanda

    How should a high-impact workflow use an LLM answer that may be plausible but false?

    Risposta

    Verify it against authoritative data or require qualified human review before action. Communicate uncertainty and preserve source evidence.

  238. Carta 238

    Domanda

    Which controls address unbounded LLM consumption?

    Risposta

    Per-user and per-task quotas, rate limits, token and tool budgets, timeouts, concurrency limits, anomaly alerts, and safe cancellation. Monitor financial as well as availability impact.

  239. Carta 239

    Domanda

    How do an HSM and a TPM differ?

    Risposta

    An HSM protects shared or service cryptographic operations; a TPM anchors trust to one platform. Both protect keys, but their scope and use cases differ.

  240. Carta 240

    Domanda

    What does secure by default mean for cloud infrastructure?

    Risposta

    A new resource starts in the least exposed, least privileged, approved state. Users must make an explicit, reviewed choice to widen access or capability.

  241. Carta 241

    Domanda

    Why do virtual CPU, memory, storage, and network settings have security impact?

    Risposta

    They define resource exposure, isolation, exhaustion limits, and device access. Overbroad virtual hardware can create attack paths or noisy-neighbor risk.

  242. Carta 242

    Domanda

    Which hypervisor type is usually preferred for production cloud hosts?

    Risposta

    A type 1 hypervisor because it removes the general-purpose host OS layer. The actual choice still depends on assurance, patching, management, and workload needs.

  243. Carta 243

    Domanda

    How can TPM-backed measured boot support cloud host assurance?

    Risposta

    Measurements anchor boot components to hardware so an attestation service can compare them with approved state. The decision still depends on trusted reference values and response policy.

  244. Carta 244

    Domanda

    How should guest OS virtualization tools be installed and maintained?

    Risposta

    Use provider-authorized packages, enable only needed features, match supported versions, patch promptly, and monitor their privilege. Remove stale tools that widen the host-to-guest boundary.

  245. Carta 245

    Domanda

    What is cloud platform operations responsible for after secure build?

    Risposta

    Maintaining approved configuration, availability, patching, monitoring, backup, access, and evidence. Operations should feed recurring defects back into design.

  246. Carta 246

    Domanda

    What does a privileged access administrator control?

    Risposta

    The issuance, elevation, monitoring, review, and revocation of administrative access. Separate the access-control role from routine use where practical.

  247. Carta 247

    Domanda

    What is the safer pattern for remote SSH administration?

    Risposta

    Short-lived identity-based access through a controlled path with host verification, least privilege, session logging, and no shared keys. Disable direct root login.

  248. Carta 248

    Domanda

    When should a cloud workload require platform attestation?

    Risposta

    When access depends on proof that the host or confidential environment is in an approved measured state. Define what is measured, who verifies it, and what failure does.

  249. Carta 249

    Domanda

    Which protocol adds origin authentication and integrity to DNS data?

    Risposta

    DNSSEC. TLS protects a transport session, a VPN protects traffic across an untrusted boundary, and DHCP safeguards prevent rogue address or configuration assignment.

  250. Carta 250

    Domanda

    What should enforce separation between cloud network zones?

    Risposta

    Routing and firewall or security-group policy tied to explicit allowed flows. VLANs can organize segments but do not enforce policy by themselves.

  251. Carta 251

    Domanda

    How do IDS and IPS differ operationally?

    Risposta

    An IDS alerts on suspected activity; an IPS sits inline and can block it. Inline prevention adds availability and false-positive risk.

  252. Carta 252

    Domanda

    What reduces RDP exposure in a cloud environment?

    Risposta

    Remove direct internet access, require a hardened gateway or private path, strong MFA, current patches, device checks, and session monitoring. Limit clipboard and drive redirection by need.

  253. Carta 253

    Domanda

    What makes a honeypot safe enough to operate?

    Risposta

    Isolation, no production trust, controlled data, monitored egress, legal approval, and an incident plan. It should observe attackers without becoming their launch point.

  254. Carta 254

    Domanda

    How do high availability and backup differ?

    Risposta

    High availability keeps service running through component failure; backup restores data or state after loss or corruption. One does not replace the other.

  255. Carta 255

    Domanda

    How should firewall, IDS, and IPS controls be layered?

    Risposta

    Firewalls constrain allowed paths, IDS detects suspicious activity, and IPS may block selected attacks inline. Central telemetry and tuned ownership make the layers useful.

  256. Carta 256

    Domanda

    When is a cloud security group insufficient as the only network control?

    Risposta

    When application-aware filtering, centralized inspection, advanced threat detection, or cross-environment policy is required. Keep security groups as workload-level least-privilege boundaries.

  257. Carta 257

    Domanda

    How should management-plane tools be installed?

    Risposta

    From verified sources through a controlled, minimal, hardened build with separate privileged access and logging. Remove sample accounts, unused plugins, and default exposure.

  258. Carta 258

    Domanda

    What is patch management?

    Risposta

    A controlled lifecycle for identifying, prioritizing, testing, deploying, verifying, and documenting security and reliability updates. Asset inventory and exception ownership are prerequisites.

  259. Carta 259

    Domanda

    How do performance and capacity monitoring differ?

    Risposta

    Performance monitoring measures current service behavior; capacity monitoring forecasts whether resources can meet future demand. Both need business thresholds and trends.

  260. Carta 260

    Domanda

    How do change, release, and deployment management differ?

    Risposta

    Change management authorizes and controls modification; release management packages approved capability; deployment management moves it into an environment. One workflow may integrate all three without erasing their goals.

  261. Carta 261

    Domanda

    What should decide whether an IPS blocks automatically?

    Risposta

    Detection confidence, asset criticality, attack impact, false-positive cost, bypass behavior, and rollback. Start with observation when evidence is weak.

  262. Carta 262

    Domanda

    Who owns a patch exception?

    Risposta

    The authorized system or risk owner, with technical evidence from operations and security. The exception needs compensating controls, expiry, and review.

  263. Carta 263

    Domanda

    What does a capacity manager protect?

    Risposta

    The service's ability to meet current and forecast demand within cost and resilience constraints. The role tracks trends, thresholds, quotas, and scaling lead time.

  264. Carta 264

    Domanda

    What is the change manager's security role?

    Risposta

    Ensure risk, testing, authorization, scheduling, rollback, and communication are proportionate to the change. Emergency changes still need retrospective evidence.

  265. Carta 265

    Domanda

    What should a backup-and-restore control verify for guest systems?

    Risposta

    Required data and configuration are captured, protected, retained, and restored within targets. Include application consistency, keys, dependencies, and documented restore order.

  266. Carta 266

    Domanda

    Which management process keeps a cloud service able to meet its agreed uptime and reliability targets?

    Risposta

    Availability management. It analyzes failure patterns, resilience, maintainability, and recovery so the service can meet those targets.

  267. Carta 267

    Domanda

    What improves patch prioritization beyond a severity score?

    Risposta

    Exploitability, exposure, asset importance, compensating controls, dependency, and business impact. Verify remediation and track unsupported assets separately.

  268. Carta 268

    Domanda

    What turns performance and capacity alerts into an availability control?

    Risposta

    Thresholds tied to service objectives, trend analysis, ownership, safe scaling, and tested response. Alert volume without action is not capacity management.

  269. Carta 269

    Domanda

    What should a configuration-management system record?

    Risposta

    Approved items, owners, versions, relationships, baselines, changes, and current state. Cloud discovery should reconcile actual resources with declared configuration.

  270. Carta 270

    Domanda

    Why place a cluster host into maintenance mode?

    Risposta

    To drain or protect workloads before planned work while preserving cluster policy. Verify capacity, placement constraints, and stateful-service behavior first.

  271. Carta 271

    Domanda

    Which management process agrees, monitors, and reviews measurable service targets with customers?

    Risposta

    Service-level management. It turns business needs into agreed service objectives, tracks results, and drives action when performance misses them.

  272. Carta 272

    Domanda

    Which hardware signals should cloud facilities monitor?

    Risposta

    Disk health, CPU and memory errors, fan and temperature state, power, and vendor fault telemetry. Correlate physical signals with host and workload impact.

  273. Carta 273

    Domanda

    How should an OS hardening baseline be maintained?

    Risposta

    Version it, test it, measure compliance, remediate drift, record exceptions, and update it for new threats and platform changes. Apply separate profiles to distinct workloads.

  274. Carta 274

    Domanda

    How do incident management and problem management differ?

    Risposta

    Incident management restores service and limits harm; problem management finds and removes underlying causes. The same event can open both tracks.

  275. Carta 275

    Domanda

    Which management process coordinates security risk and controls across cloud service operation?

    Risposta

    Information security management. It aligns policy, risk treatment, control operation, evidence, incidents, and improvement with the service-management system.

  276. Carta 276

    Domanda

    Which management process turns recurring service-control gaps into measured improvements?

    Risposta

    Continual service improvement management. It prioritizes opportunities, defines a measurable target and owner, implements change, and verifies the outcome.

  277. Carta 277

    Domanda

    How should operations choose among NIST, ISO, COBIT, CIS Controls, COSO, ITIL, or ISO/IEC 20000-1?

    Risposta

    Map the applicable framework or standard to the organization's legal duties, risks, service goals, and evidence needs. The names are not interchangeable, and adoption alone does not prove control effectiveness.

  278. Carta 278

    Domanda

    A service is restored after repeated crashes. Which process continues the root-cause work?

    Risposta

    Problem management. Incident management can close after stable restoration while the underlying defect, workaround, and prevention remain tracked.

  279. Carta 279

    Domanda

    Which management process owns tested arrangements for sustaining or restoring critical services after severe disruption?

    Risposta

    Continuity management. Incident management handles the current event, while availability management focuses on meeting service uptime and reliability targets.

  280. Carta 280

    Domanda

    What does a cloud forensic lead decide?

    Risposta

    The lawful collection strategy, volatile-data priorities, tools, provider coordination, preservation, and analysis plan. The lead should understand cloud-specific evidence limits.

  281. Carta 281

    Domanda

    What does chain of custody record?

    Risposta

    Who collected, handled, transferred, stored, analyzed, and disposed of evidence, when and why. Integrity checks support the record but do not replace it.

  282. Carta 282

    Domanda

    What does an incident commander own?

    Risposta

    Priorities, roles, decisions, coordination, cadence, and safe handoffs during an incident. Technical responders investigate and act within that structure.

  283. Carta 283

    Domanda

    What does the incident communications lead control?

    Risposta

    Approved messages, audiences, channels, timing, records, and coordination with legal and leadership. Technical certainty and disclosure obligations may change during the event.

  284. Carta 284

    Domanda

    How do a SOC, SIEM, and SOAR relate?

    Risposta

    A SOC is the operating function, a SIEM centralizes and analyzes security events, and SOAR coordinates automated workflows. People, process, authority, and evidence connect the tools.

  285. Carta 285

    Domanda

    What is an evidence custodian responsible for?

    Risposta

    Controlled storage, access, transfer, integrity verification, retention, and chain-of-custody records. The custodian preserves evidence without altering its meaning.

  286. Carta 286

    Domanda

    How should a SOC use threat intelligence?

    Risposta

    Map relevant, timely indicators and adversary behavior to assets, detections, hunts, and decisions. Expire stale indicators and separate confidence from fact.

  287. Carta 287

    Domanda

    How should AI-assisted security monitoring be governed?

    Risposta

    Validate data and models, measure errors and drift, limit action authority, log reasoning inputs and outcomes, and keep human review for consequential cases. Compare against a safe manual path.

  288. Carta 288

    Domanda

    When is a cloud snapshot suitable forensic evidence?

    Risposta

    When collection is authorized, scope and timing are documented, integrity is protected, and the snapshot preserves relevant state. It may omit memory, external services, or rapidly changing logs.

  289. Carta 289

    Domanda

    Who decides whether a regulator must be notified during a cloud incident?

    Risposta

    The authorized legal or compliance owner under the incident plan. Vendor and communications owners coordinate channels; engineers supply verified facts.

  290. Carta 290

    Domanda

    What should a forensic plan obtain from the cloud provider before an incident?

    Risposta

    Available logs and APIs, retention, time sources, support contacts, legal process, evidence formats, isolation options, and responsibility boundaries. Confirm access with an exercise.

  291. Carta 291

    Domanda

    How should vulnerability assessment and penetration testing work together?

    Risposta

    Assessment finds and prioritizes likely weaknesses broadly; authorized penetration testing demonstrates selected exploit paths and impact. Both require scoped remediation and retest.

  292. Carta 292

    Domanda

    How should a SIEM protect cloud log value?

    Risposta

    Normalize without losing source evidence, control access, preserve time and integrity, correlate identities and assets, tune detections, and retain by purpose. Monitor collection gaps.

  293. Carta 293

    Domanda

    What should SOAR do when a playbook's evidence is incomplete?

    Risposta

    Pause or take only a safe reversible step, preserve context, and escalate to an authorized human. Do not let automation convert uncertainty into broad containment damage.

  294. Carta 294

    Domanda

    When should incident communication wait?

    Risposta

    Only when authorized coordination is needed to verify facts, protect response, or meet a defined legal strategy. Do not delay a mandatory notice past its trigger or deadline.

  295. Carta 295

    Domanda

    When is penetration testing more useful than another vulnerability scan?

    Risposta

    When the organization needs authorized evidence that selected weaknesses can combine into a meaningful attack path. Scanning remains better for broad, repeatable coverage.

  296. Carta 296

    Domanda

    Which evidence should be collected first from a running cloud workload?

    Risposta

    The most volatile, relevant evidence that will disappear earliest, if collection is authorized and safe. Balance volatility against service impact and contamination risk.

  297. Carta 297

    Domanda

    Why can cloud data be subject to more than one jurisdiction?

    Risposta

    Customers, providers, processing, storage, people, contracts, and affected individuals may sit in different places. Location and legal reach are related but not identical.

  298. Carta 298

    Domanda

    Why are privacy roles contextual rather than permanent labels?

    Risposta

    An organization can be controller for one processing purpose and processor for another. Determine the role from actual decisions and instructions, not the company type.

  299. Carta 299

    Domanda

    What should legal counsel contribute to cloud design?

    Risposta

    Interpret applicable law, privilege, contracts, disputes, preservation, disclosure, and legal risk. Counsel advises; accountable business owners still decide within authority.

  300. Carta 300

    Domanda

    What is eDiscovery?

    Risposta

    The identification, preservation, collection, processing, review, and production of electronically stored information for a legal matter. Cloud scale and provider control affect each step.

  301. Carta 301

    Domanda

    How do contractual and regulated private data differ?

    Risposta

    Contractual duties come from agreed terms; regulated duties come from applicable law. The same data can be subject to both, and the stricter combined obligations may govern.

  302. Carta 302

    Domanda

    What is the controller's contract duty toward a cloud processor?

    Risposta

    Give documented instructions, choose and oversee a capable processor, and define required privacy and security terms. Applicable law may add specific clauses and audit duties.

  303. Carta 303

    Domanda

    What is a Privacy Impact Assessment?

    Risposta

    A structured evaluation of how planned processing affects people and how privacy risk will be handled. Perform it early enough to change the design.

  304. Carta 304

    Domanda

    What is an ISMS?

    Risposta

    A managed system of policies, risk processes, controls, evidence, review, and continual improvement for information security. It is broader than a control checklist or toolset.

  305. Carta 305

    Domanda

    What does a contract's choice-of-law clause do?

    Risposta

    Names the law intended to govern the contract. It does not automatically override mandatory laws or every court's jurisdiction.

  306. Carta 306

    Domanda

    What makes a legal hold operationally defensible in cloud systems?

    Risposta

    Authorized scope, prompt preservation, deletion suspension, controlled collection, access logging, periodic review, and documented release. Test whether provider features cover all copies.

  307. Carta 307

    Domanda

    Does calling a field PII or PHI settle every privacy obligation?

    Risposta

    No. Applicability depends on the data, person, entity, purpose, context, and governing law or contract. Classify with qualified privacy and legal input.

  308. Carta 308

    Domanda

    Which design control reduces privacy risk before consent screens and notices?

    Risposta

    Data minimization tied to a specific approved purpose. Collecting less reduces exposure, rights handling, retention, and breach impact.

  309. Carta 309

    Domanda

    What is a processor's core duty toward controller data?

    Risposta

    Process it only under authorized instructions and required legal obligations, while applying agreed controls and assistance. Subprocessors need governed approval and flow-down terms.

  310. Carta 310

    Domanda

    What control reveals cross-border cloud data processing before it becomes a compliance surprise?

    Risposta

    A maintained data and subprocessors map tied to locations, purposes, roles, transfers, and safeguards. Reconcile contracts with actual telemetry and provider disclosures.

  311. Carta 311

    Domanda

    How do internal and external audits differ?

    Risposta

    Internal audit provides independent assurance inside the organization; external audit is performed by an outside party for a defined objective. Both require scope, criteria, evidence, and independence.

  312. Carta 312

    Domanda

    When should a PIA be reopened?

    Risposta

    When purpose, data, people, model, provider, location, sharing, retention, or risk materially changes. A one-time assessment becomes stale as processing evolves.

  313. Carta 313

    Domanda

    How should a cloud team use GDPR, PIPEDA, India's DPDP Act, FERPA, HIPAA, ISO/IEC 27018, or GAPP?

    Risposta

    First determine which laws apply, then map their obligations and any selected framework guidance to actual processing and controls. A named standard or provider region is not automatic compliance.

  314. Carta 314

    Domanda

    Two countries impose conflicting duties on the same cloud records. What is the first move?

    Risposta

    Escalate to qualified counsel with the exact data, actors, locations, contracts, orders, and timelines. Preserve evidence and avoid an irreversible technical action based on guesswork.

  315. Carta 315

    Domanda

    What protects an internal auditor's independence?

    Risposta

    Authority to assess outside the operation being audited, objective reporting, and freedom from designing or owning the control under review. Internal employment does not prevent independence if governance is sound.

  316. Carta 316

    Domanda

    What does a privacy officer oversee?

    Risposta

    Privacy governance, impact assessment, rights, transparency, lawful processing, transfers, incidents, and regulator engagement. The exact statutory role varies by jurisdiction.

  317. Carta 317

    Domanda

    What do SOC, SSAE, and ISAE labels tell an assurance-report reader?

    Risposta

    SOC identifies a service-organization report family, while SSAE and ISAE identify attestation standards used for defined engagements. The exact report type, criteria, period, scope, exceptions, and subservices determine its value.

  318. Carta 318

    Domanda

    What must an audit plan define before cloud audit fieldwork starts?

    Risposta

    The objective, criteria, scope, responsibilities, schedule, methods, evidence access, and reporting path. The plan should also name constraints and follow-up ownership.

  319. Carta 319

    Domanda

    How do risk appetite and risk tolerance differ?

    Risposta

    Risk appetite expresses the amount and type of risk an organization is willing to pursue or retain; tolerance sets acceptable variation around objectives. Both guide escalation and treatment.

  320. Carta 320

    Domanda

    What does an enterprise risk owner decide?

    Risposta

    Whether to avoid, mitigate, transfer or share, or accept a documented risk within authority. The owner tracks residual exposure and review triggers.

  321. Carta 321

    Domanda

    How should risk metrics be designed?

    Risposta

    Tie each metric to a decision, owner, threshold, reliable source, trend, and response. Separate leading indicators from lagging outcomes and guard against easy gaming.

  322. Carta 322

    Domanda

    What is gap analysis?

    Risposta

    Comparison of current control state with a required or target state. Each gap needs impact, owner, treatment, evidence, and due date.

  323. Carta 323

    Domanda

    What makes cloud audit evidence reliable?

    Risposta

    Clear criteria, complete scope, trustworthy source, protected integrity, accurate time, repeatable collection, and accountable ownership. Screenshots without context are weak evidence.

  324. Carta 324

    Domanda

    Why does a distributed cloud model complicate audit scope?

    Risposta

    Controls, evidence, people, providers, and data span locations and jurisdictions with different access and retention limits. Define boundaries and shared responsibilities before fieldwork.

  325. Carta 325

    Domanda

    Can a clean SOC report prove compliance with a customer's specialized regulation?

    Risposta

    No. Map the report's criteria, period, scope, exceptions, subservices, and customer controls to the specific requirement. NERC CIP, HIPAA, HITECH, PCI, or another regime may need additional evidence.

  326. Carta 326

    Domanda

    What should a customer assess in a cloud provider's risk-management program?

    Risposta

    Whether its policies, methods, controls, risk profile, and appetite fit the customer's requirements and exposure. Review evidence before selection and when material risk changes.

  327. Carta 327

    Domanda

    What is a data owner's enterprise-risk role?

    Risposta

    Set business value, classification, allowed use, access, retention, and acceptable risk for the data. Custodians implement the resulting controls.

  328. Carta 328

    Domanda

    What AI evidence supports accountability and explainability without promising perfect interpretation?

    Risposta

    Document intended use, data and model versions, decision roles, testing, limitations, human oversight, outputs, changes, and incident history. Match explanation depth to affected people and legal duties.

  329. Carta 329

    Domanda

    What does a data steward add to governance?

    Risposta

    Consistent definitions, quality rules, metadata, lineage, and policy application across business use. The steward connects business meaning to operational handling.

  330. Carta 330

    Domanda

    What is procurement's security role in cloud outsourcing?

    Risposta

    Make required risk, assurance, pricing, ownership, exit, and supplier terms part of selection and negotiation. Security requirements lose force if added after commercial commitment.

  331. Carta 331

    Domanda

    When should an organization avoid a cloud risk rather than mitigate it?

    Risposta

    When stopping the activity is feasible and residual exposure would remain outside appetite or legal authority. Compare the business consequence of avoidance with other treatments.

  332. Carta 332

    Domanda

    What is an external auditor responsible for?

    Risposta

    Perform the agreed independent engagement against stated criteria and report within its scope. The auditor does not own management's controls or risk decisions.

  333. Carta 333

    Domanda

    How do an MSA, SOW, and SLA differ?

    Risposta

    The MSA sets the general legal relationship, the SOW defines specific work and deliverables, and the SLA sets measurable service commitments. Read them together for the full obligation.

  334. Carta 334

    Domanda

    What should a cloud risk register contain?

    Risposta

    Scenario, assets, cause, consequence, owner, likelihood, impact, controls, treatment, residual risk, due dates, and review triggers. Link evidence and dependencies where useful.

  335. Carta 335

    Domanda

    Who should own a cloud contract after signature?

    Risposta

    A named contract or vendor manager with business, legal, security, privacy, and service stakeholders. Ownership includes obligations, evidence, changes, renewals, disputes, and exit.

  336. Carta 336

    Domanda

    Which contract controls support a safe cloud exit?

    Risposta

    Data and configuration export, assistance, timing, format, cost, continued access, verified deletion, transition support, and survival of needed duties. Exercise the exit path before a crisis.

  337. Carta 337

    Domanda

    What makes a contractual right to audit usable?

    Risposta

    Defined scope, notice, frequency, methods, evidence access, confidentiality, cost, remediation, and alternatives when direct testing is unsafe. A vague right may be impossible to exercise.

  338. Carta 338

    Domanda

    When does source-code escrow reduce cloud vendor viability risk?

    Risposta

    When usable code plus dependencies, documentation, rights, updates, and release triggers can support continuity. Escrow adds little if the customer cannot operate the service.

  339. Carta 339

    Domanda

    What should a cloud incident-notification clause define?

    Risposta

    Trigger, timing, recipient, secure channel, minimum facts, updates, cooperation, evidence, regulator support, and subcontractor flow-down. Avoid waiting for the provider's final root cause before notice.

  340. Carta 340

    Domanda

    What should happen to customer data when a cloud contract ends?

    Risposta

    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 carte

CCSP 2026 Flashcards: August Exam Outline Review

Studia questo mazzo gratis

Nibomo si apre e puoi iniziare a studiare.