Practice Exams:

ISC CCSP Dumps

EXAM: Certified Cloud Security Professional (CCSP)
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

CCSP Premium Bundle


  • Premium File 512 Questions & Answers
  • Training Course 43 Lectures
  • Study Guide 571 Pages

ISC CCSP Practice Test 53

Question 520

A research cloud team introduces third-party packages each sprint without updating its security review. Suppose the team makes this shortcut instead: Run a single annual security review and let every weekly release bypass threat modeling and dependency checks. Which outcome is the most likely direct consequence?

  1. A leaked image or source bundle grants enduring privileged access across unrelated services
  2. Authenticated attackers retrieve or modify other tenants' application records by changing resource IDs
  3. An attacker uses an ordinary content upload to trigger unauthorized tool actions or data disclosure
  4. New vulnerabilities reach production long before the next scheduled security audit

Answer & Explanations

Correct answer: D

A.

This failure concerns another scenario: A bank's serverless functions all reuse a broad database administrator password stored in their source code. In the stated case: A research cloud team introduces third-party packages each sprint without updating its security review. The relevant consequence is: New vulnerabilities reach production long before the next scheduled security audit. The control that prevents it is: Use risk-based secure design and code validation throughout agile iterations instead of relying on one end-stage checklist.

B.

This failure concerns another scenario: A SaaS team repeatedly introduces broken object-level authorization despite enforcing user login. In the stated case: A research cloud team introduces third-party packages each sprint without updating its security review. The relevant consequence is: New vulnerabilities reach production long before the next scheduled security audit. The control that prevents it is: Use risk-based secure design and code validation throughout agile iterations instead of relying on one end-stage checklist.

C.

This failure concerns another scenario: A customer support assistant reads uploaded tickets and has permission to change billing access lists. In the stated case: A research cloud team introduces third-party packages each sprint without updating its security review. The relevant consequence is: New vulnerabilities reach production long before the next scheduled security audit. The control that prevents it is: Use risk-based secure design and code validation throughout agile iterations instead of relying on one end-stage checklist.

D.

New vulnerabilities reach production long before the next scheduled security audit. This is the risk in the stated situation: A research cloud team introduces third-party packages each sprint without updating its security review. The risky shortcut is: Run a single annual security review and let every weekly release bypass threat modeling and dependency checks. Prevent it by: Use risk-based secure design and code validation throughout agile iterations instead of relying on one end-stage checklist.

Question 521

A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. Which cloud security control or governance decision most directly addresses the described issue while keeping the change scoped?

  1. Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation
  2. Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied
  3. Provide role-specific secure cloud coding education on object authorization, API authentication and negative security tests
  4. Teach application teams to treat retrieved documents and model output as untrusted inputs before triggering sensitive cloud actions

Answer & Explanations

Correct answer: A

A.

Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation. The technical reason is: Threat modeling connects system architecture to plausible abuse paths so authorization and rate-limit controls address actual threats. The stated condition is: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. Confirm the result by: Walk an attacker path through the model and verify mitigations are tied to specific data flows and security tests.

B.

This action is appropriate in a different case: A university uses shared infrastructure templates containing hard-coded production API tokens. There, the reason is: Configuration is executable architecture, so insecure defaults and exposed credentials can propagate instantly through automation. The current case is: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. The appropriate response is: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

C.

This action is appropriate in a different case: A SaaS team repeatedly introduces broken object-level authorization despite enforcing user login. There, the reason is: Cloud API routes often expose object identifiers, and a valid login does not authorize access to every tenant object. The current case is: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. The appropriate response is: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

D.

This action is appropriate in a different case: A customer support assistant reads uploaded tickets and has permission to change billing access lists. There, the reason is: A model can follow malicious instructions embedded in lower-trust text unless tools, data and privileges are bounded outside the prompt. The current case is: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. The appropriate response is: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

Question 522

A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. An engineer recommends: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation. Which technical explanation most directly justifies this recommendation?

  1. A model can follow malicious instructions embedded in lower-trust text unless tools, data and privileges are bounded outside the prompt
  2. Threat modeling connects system architecture to plausible abuse paths so authorization and rate-limit controls address actual threats
  3. Security requirements discovered only after deployment become expensive or incompatible with existing application architecture
  4. Frequent deployment creates repeated change risk, so security review must track each material feature and dependency update

Answer & Explanations

Correct answer: B

A.

This principle explains a different technical intervention: Teach application teams to treat retrieved documents and model output as untrusted inputs before triggering sensitive cloud actions. It applies to: A customer support assistant reads uploaded tickets and has permission to change billing access lists. The actual case is: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. The mechanism relevant here is: Threat modeling connects system architecture to plausible abuse paths so authorization and rate-limit controls address actual threats.

B.

Threat modeling connects system architecture to plausible abuse paths so authorization and rate-limit controls address actual threats. That mechanism explains the decision: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation. In the reported situation: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. Confirmation requires: Walk an attacker path through the model and verify mitigations are tied to specific data flows and security tests.

C.

This principle explains a different technical intervention: Translate business and privacy needs into measurable authentication, authorization, encryption and recovery criteria at the start of the SDLC. It applies to: A medical SaaS startup writes an application first and asks later how to prevent staff from viewing patient data. The actual case is: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. The mechanism relevant here is: Threat modeling connects system architecture to plausible abuse paths so authorization and rate-limit controls address actual threats.

D.

This principle explains a different technical intervention: Use risk-based secure design and code validation throughout agile iterations instead of relying on one end-stage checklist. It applies to: A finance platform releases API changes daily but schedules its only security test annually. The actual case is: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. The mechanism relevant here is: Threat modeling connects system architecture to plausible abuse paths so authorization and rate-limit controls address actual threats.

Question 523

A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?

  1. Introduce a vulnerable test change and confirm pipeline gating or required human review blocks release before production
  2. Inject a safe known vulnerable dependency and a staging runtime flaw and verify each matching scanner detects its own class of risk
  3. Walk an attacker path through the model and verify mitigations are tied to specific data flows and security tests
  4. Re-run a role-bypass abuse case after each release and verify denial and logging remain effective

Answer & Explanations

Correct answer: C

A.

This observation would verify a different remedy: Use risk-based secure design and code validation throughout agile iterations instead of relying on one end-stage checklist. That remedy applies to: A finance platform releases API changes daily but schedules its only security test annually. The present condition is: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. To assess it, check: Walk an attacker path through the model and verify mitigations are tied to specific data flows and security tests.

B.

This observation would verify a different remedy: Run complementary source, dependency and runtime security tests with severity-based release gates. That remedy applies to: A cloud payment API passes source checks but deploys an outdated parser with a published security issue. The present condition is: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. To assess it, check: Walk an attacker path through the model and verify mitigations are tied to specific data flows and security tests.

C.

Walk an attacker path through the model and verify mitigations are tied to specific data flows and security tests. This check directly tests: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation. The underlying behavior is: Threat modeling connects system architecture to plausible abuse paths so authorization and rate-limit controls address actual threats. The case is: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks.

D.

This observation would verify a different remedy: Add automated negative-path tests for cross-tenant requests, malformed tokens and privilege escalation alongside normal functional tests. That remedy applies to: A property portal's normal customer checkout succeeds but users can alter another account's billing address. The present condition is: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. To assess it, check: Walk an attacker path through the model and verify mitigations are tied to specific data flows and security tests.

Question 524

A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?

  1. Test only the happy-path administrator action and label the entire feature security validated
  2. Pull production containers from an untrusted public tag solely because the image name resembles a trusted project
  3. Assume an HTTPS endpoint can safely skip user authorization and request throttling
  4. Treat a network diagram with no identities or trust boundaries as a completed application threat model

Answer & Explanations

Correct answer: D

A.

This proposed shortcut concerns a separate case: A property portal's normal customer checkout succeeds but users can alter another account's billing address. The risk in this question concerns: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. Here the unsafe shortcut is: Treat a network diagram with no identities or trust boundaries as a completed application threat model. Use this response instead: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

B.

This proposed shortcut concerns a separate case: A healthcare startup uses an unpinned container image that an unknown publisher can replace. The risk in this question concerns: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. Here the unsafe shortcut is: Treat a network diagram with no identities or trust boundaries as a completed application threat model. Use this response instead: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

C.

This proposed shortcut concerns a separate case: A retail API terminates TLS correctly but accepts any account number from a logged-in user. The risk in this question concerns: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. Here the unsafe shortcut is: Treat a network diagram with no identities or trust boundaries as a completed application threat model. Use this response instead: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

D.

Treat a network diagram with no identities or trust boundaries as a completed application threat model. This shortcut is unsafe for: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. The resulting failure can be: An overlooked cross-tenant API path is released without a suitable authorization or monitoring control. The safer response is: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

Question 525

A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. Suppose the team makes this shortcut instead: Treat a network diagram with no identities or trust boundaries as a completed application threat model. Which outcome is the most likely direct consequence?

  1. An overlooked cross-tenant API path is released without a suitable authorization or monitoring control
  2. Attackers use stolen low-privilege tokens to read other records or exhaust backend capacity
  3. One compromised container can access host credentials or neighboring workloads
  4. A compromised low-value service pivots to sensitive internal APIs without user-facing controls

Answer & Explanations

Correct answer: A

A.

An overlooked cross-tenant API path is released without a suitable authorization or monitoring control. This is the risk in the stated situation: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. The risky shortcut is: Treat a network diagram with no identities or trust boundaries as a completed application threat model. Prevent it by: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

B.

This failure concerns another scenario: A retail API terminates TLS correctly but accepts any account number from a logged-in user. In the stated case: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. The relevant consequence is: An overlooked cross-tenant API path is released without a suitable authorization or monitoring control. The control that prevents it is: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

C.

This failure concerns another scenario: A university deploys student-made web containers with access to the host container engine socket. In the stated case: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. The relevant consequence is: An overlooked cross-tenant API path is released without a suitable authorization or monitoring control. The control that prevents it is: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

D.

This failure concerns another scenario: A clinic's internal appointment API trusts any caller from the cluster pod network. In the stated case: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. The relevant consequence is: An overlooked cross-tenant API path is released without a suitable authorization or monitoring control. The control that prevents it is: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

Question 526

A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. Which cloud security control or governance decision most directly addresses the described issue while keeping the change scoped?

  1. Teach application teams to treat retrieved documents and model output as untrusted inputs before triggering sensitive cloud actions
  2. Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation
  3. Translate business and privacy needs into measurable authentication, authorization, encryption and recovery criteria at the start of the SDLC
  4. Use risk-based secure design and code validation throughout agile iterations instead of relying on one end-stage checklist

Answer & Explanations

Correct answer: B

A.

This action is appropriate in a different case: A customer support assistant reads uploaded tickets and has permission to change billing access lists. There, the reason is: A model can follow malicious instructions embedded in lower-trust text unless tools, data and privileges are bounded outside the prompt. The current case is: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. The appropriate response is: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

B.

Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation. The technical reason is: Threat modeling connects system architecture to plausible abuse paths so authorization and rate-limit controls address actual threats. The stated condition is: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. Confirm the result by: Walk an attacker path through the model and verify mitigations are tied to specific data flows and security tests.

C.

This action is appropriate in a different case: A medical SaaS startup writes an application first and asks later how to prevent staff from viewing patient data. There, the reason is: Security requirements discovered only after deployment become expensive or incompatible with existing application architecture. The current case is: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. The appropriate response is: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

D.

This action is appropriate in a different case: A finance platform releases API changes daily but schedules its only security test annually. There, the reason is: Frequent deployment creates repeated change risk, so security review must track each material feature and dependency update. The current case is: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. The appropriate response is: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

Question 527

A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. An engineer recommends: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation. Which technical explanation most directly justifies this recommendation?

  1. Frequent deployment creates repeated change risk, so security review must track each material feature and dependency update
  2. Static analysis finds code patterns, software composition analysis checks third-party components and dynamic testing observes a deployed application's behavior
  3. Threat modeling connects system architecture to plausible abuse paths so authorization and rate-limit controls address actual threats
  4. Functional success does not establish that unauthorized users cannot trigger the same operation through alternate inputs

Answer & Explanations

Correct answer: C

A.

This principle explains a different technical intervention: Use risk-based secure design and code validation throughout agile iterations instead of relying on one end-stage checklist. It applies to: A finance platform releases API changes daily but schedules its only security test annually. The actual case is: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. The mechanism relevant here is: Threat modeling connects system architecture to plausible abuse paths so authorization and rate-limit controls address actual threats.

B.

This principle explains a different technical intervention: Run complementary source, dependency and runtime security tests with severity-based release gates. It applies to: A cloud payment API passes source checks but deploys an outdated parser with a published security issue. The actual case is: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. The mechanism relevant here is: Threat modeling connects system architecture to plausible abuse paths so authorization and rate-limit controls address actual threats.

C.

Threat modeling connects system architecture to plausible abuse paths so authorization and rate-limit controls address actual threats. That mechanism explains the decision: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation. In the reported situation: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. Confirmation requires: Walk an attacker path through the model and verify mitigations are tied to specific data flows and security tests.

D.

This principle explains a different technical intervention: Add automated negative-path tests for cross-tenant requests, malformed tokens and privilege escalation alongside normal functional tests. It applies to: A property portal's normal customer checkout succeeds but users can alter another account's billing address. The actual case is: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. The mechanism relevant here is: Threat modeling connects system architecture to plausible abuse paths so authorization and rate-limit controls address actual threats.

Question 528

A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?

  1. Re-run a role-bypass abuse case after each release and verify denial and logging remain effective
  2. Validate a test artifact signature and SBOM against expected build identity and reject an unsigned modified image
  3. Use a test client to verify invalid tokens, unauthorized object IDs and over-limit calls fail with correct logged outcomes
  4. Walk an attacker path through the model and verify mitigations are tied to specific data flows and security tests

Answer & Explanations

Correct answer: D

A.

This observation would verify a different remedy: Add automated negative-path tests for cross-tenant requests, malformed tokens and privilege escalation alongside normal functional tests. That remedy applies to: A property portal's normal customer checkout succeeds but users can alter another account's billing address. The present condition is: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. To assess it, check: Walk an attacker path through the model and verify mitigations are tied to specific data flows and security tests.

B.

This observation would verify a different remedy: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images. That remedy applies to: A healthcare startup uses an unpinned container image that an unknown publisher can replace. The present condition is: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. To assess it, check: Walk an attacker path through the model and verify mitigations are tied to specific data flows and security tests.

C.

This observation would verify a different remedy: Enforce token validation, per-operation authorization, schema checks and rate limits at appropriate cloud API boundaries. That remedy applies to: A retail API terminates TLS correctly but accepts any account number from a logged-in user. The present condition is: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. To assess it, check: Walk an attacker path through the model and verify mitigations are tied to specific data flows and security tests.

D.

Walk an attacker path through the model and verify mitigations are tied to specific data flows and security tests. This check directly tests: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation. The underlying behavior is: Threat modeling connects system architecture to plausible abuse paths so authorization and rate-limit controls address actual threats. The case is: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries.

Question 529

A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?

  1. Treat a network diagram with no identities or trust boundaries as a completed application threat model
  2. Assume an HTTPS endpoint can safely skip user authorization and request throttling
  3. Run every internet-facing container as privileged with the host filesystem mounted to simplify debugging
  4. Allow every workload in the Kubernetes cluster to call every financial API merely because traffic stays internal

Answer & Explanations

Correct answer: A

A.

Treat a network diagram with no identities or trust boundaries as a completed application threat model. This shortcut is unsafe for: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. The resulting failure can be: An overlooked cross-tenant API path is released without a suitable authorization or monitoring control. The safer response is: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

B.

This proposed shortcut concerns a separate case: A retail API terminates TLS correctly but accepts any account number from a logged-in user. The risk in this question concerns: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. Here the unsafe shortcut is: Treat a network diagram with no identities or trust boundaries as a completed application threat model. Use this response instead: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

C.

This proposed shortcut concerns a separate case: A university deploys student-made web containers with access to the host container engine socket. The risk in this question concerns: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. Here the unsafe shortcut is: Treat a network diagram with no identities or trust boundaries as a completed application threat model. Use this response instead: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

D.

This proposed shortcut concerns a separate case: A clinic's internal appointment API trusts any caller from the cluster pod network. The risk in this question concerns: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. Here the unsafe shortcut is: Treat a network diagram with no identities or trust boundaries as a completed application threat model. Use this response instead: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

Question 530

A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. Suppose the team makes this shortcut instead: Treat a network diagram with no identities or trust boundaries as a completed application threat model. Which outcome is the most likely direct consequence?

  1. A compromised low-value service pivots to sensitive internal APIs without user-facing controls
  2. An overlooked cross-tenant API path is released without a suitable authorization or monitoring control
  3. A compromised low-privilege user gains broad cloud control despite successful single sign-on enforcement
  4. A leaked image or source bundle grants enduring privileged access across unrelated services

Answer & Explanations

Correct answer: B

A.

This failure concerns another scenario: A clinic's internal appointment API trusts any caller from the cluster pod network. In the stated case: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. The relevant consequence is: An overlooked cross-tenant API path is released without a suitable authorization or monitoring control. The control that prevents it is: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

B.

An overlooked cross-tenant API path is released without a suitable authorization or monitoring control. This is the risk in the stated situation: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. The risky shortcut is: Treat a network diagram with no identities or trust boundaries as a completed application threat model. Prevent it by: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

C.

This failure concerns another scenario: A multinational enterprise adds SaaS login federation but accidentally maps all staff to a cloud admin group. In the stated case: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. The relevant consequence is: An overlooked cross-tenant API path is released without a suitable authorization or monitoring control. The control that prevents it is: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

D.

This failure concerns another scenario: A bank's serverless functions all reuse a broad database administrator password stored in their source code. In the stated case: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. The relevant consequence is: An overlooked cross-tenant API path is released without a suitable authorization or monitoring control. The control that prevents it is: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

Certified Cloud Security Professional (CCSP) (CCSP) Practice Tests