Five CCSP Concepts Candidates Most Often Get Wrong

Five CCSP Concepts Candidates Most Often Get Wrong

6 min read5 views

Super AdminSuper Admin

The CCSP tests cloud security from the perspective of someone who designs, operates and governs cloud services, not someone who has memorised one provider's console. Experienced practitioners sometimes find that their day-to-day habits lead them to the wrong answer, because the exam asks about principles that apply across every provider and service model.

Below are five concepts that commonly trip candidates up. For each one you will find the misconception, the correct view and a short example.

The CCSP domains

For context, the exam is organised into six domains. Current details, including the exam outline, are on the ISC2 CCSP page.

CCSP domains
#Domain
1Cloud Concepts, Architecture and Design
2Cloud Data Security
3Cloud Platform and Infrastructure Security
4Cloud Application Security
5Cloud Security Operations
6Legal, Risk and Compliance

1. "The provider is responsible for security in the cloud"

The misconception

Once workloads move to a reputable provider, security becomes largely the provider's job.

The correct view

Cloud security follows a shared responsibility model, and the split depends on the service model. In IaaS the customer manages the operating system, applications and data. In PaaS the provider takes on more of the platform. In SaaS the provider runs almost everything, yet the customer still manages users, access and data. Across all three models, one thing never moves: the customer remains accountable for its data and for compliance obligations to its own customers and regulators.

Example

A company stores customer records in a SaaS application and leaves a shared link publicly accessible. The provider's infrastructure worked exactly as designed. The exposure is the customer's responsibility, because access configuration sits on the customer's side of the line.

2. "Deleting cloud data works the same as on-premises"

The misconception

Data can be destroyed in the cloud by overwriting or degaussing the media, just like in your own data centre.

The correct view

In a multi-tenant environment you do not control the physical media. Your data may be spread across many disks and replicas shared with other tenants, and you cannot ask the provider to degauss or shred a particular drive. The method the exam expects you to recognise is cryptographic erasure, often called crypto-shredding: encrypt the data with keys you control, then securely destroy the keys so the remaining ciphertext cannot be recovered.

Example

When a contract with a storage provider ends, the customer deletes its objects and then destroys the encryption keys held in its own key management service. Any copies left in the provider's backups are unreadable without the keys. This is also why key management, and who holds the keys, is such a central topic in the Cloud Data Security domain.

A server rack with brightly coloured network cables
Photo: Unsplash

3. "Any SOC report will do, and anyone can read it"

The misconception

SOC reports are interchangeable, and a provider's SOC 2 report is a public document.

The correct view

The reports serve different purposes. A SOC 1 report addresses controls relevant to customers' financial reporting. A SOC 2 report addresses controls related to the trust services criteria, such as security, availability, processing integrity, confidentiality and privacy, and is generally restricted to customers and prospects, often under a non-disclosure agreement. A SOC 3 report covers similar ground at a summary level and is intended for general distribution. In addition, a Type I report describes control design at a point in time, whereas a Type II report tests operating effectiveness over a period.

Example

A security team evaluating a provider wants evidence that access controls actually operated throughout the past year. A SOC 3 summary or a Type I report would not be sufficient; they should request a SOC 2 Type II report.

4. "Data residency is just about where the servers are"

The misconception

If data is stored in a region inside your own country, jurisdiction questions are settled.

The correct view

The physical location of the data is only one factor. Laws that may apply can also depend on where the provider is headquartered, where its support staff can access the data from, where backups and replicas are kept, and where the data subjects live. Legal processes such as eDiscovery and lawful access requests can reach data through any of these connections. The CCSP expects you to consider all of them when assessing legal risk.

Example

Hypothetical scenario: an organisation chooses a domestic region for compliance reasons, but the provider's follow-the-sun support model allows engineers in other countries to access customer environments during troubleshooting. A thorough assessment would review the contract's terms on support access, data location commitments and how the provider responds to legal requests.

5. "Portability and interoperability are the same thing"

The misconception

Both words simply mean "avoiding vendor lock-in", so they can be used interchangeably.

The correct view

They describe different properties. Interoperability is the ability of systems and services to work together and exchange information, for example a cloud service exchanging data with an on-premises system through standard interfaces. Portability is the ability to move data or applications from one environment or provider to another with minimal effort and without losing function. Both reduce lock-in, but they are evaluated differently: interoperability through interfaces and formats used in operation, portability through how easily you could leave.

Example

An application that exchanges data with the company's identity provider using open standards shows good interoperability. Whether its data can be exported in a usable format and the workload redeployed with another provider is a question of portability. A service can score well on one and poorly on the other.

Summary

Misconceptions and corrections
ConceptCommon misconceptionWhat to remember
Shared responsibilityThe provider handles securityThe split varies by model; data accountability always stays with the customer
Data destructionOverwrite or degauss the disksUse cryptographic erasure; control and destroy the keys
SOC reportsAll reports are equal and publicSOC 1 financial, SOC 2 trust criteria and restricted, SOC 3 public; Type II tests over time
JurisdictionServer location settles itProvider location, access paths, backups and data subjects all matter
Portability vs interoperabilitySame thingWorking together versus moving away

How to use this list

When you review practice questions, notice whether your wrong answers come from a gap in knowledge or from carrying over a habit from your own environment. The second kind is harder to spot, because the answer feels obviously right. For each of the five concepts above, try explaining it aloud in two sentences without referring to any specific provider. If you can, you are thinking at the level the exam expects.

Conclusion

None of these five concepts is obscure, which is exactly why they are easy to get wrong: experience suggests an answer before the question has been fully read. Slow down on questions about responsibility, data deletion, assurance reports, jurisdiction and lock-in, and ask what holds true for every provider and every service model. That vendor-neutral habit is what the CCSP is really testing.

0.0 (0 ratings)
Share:

CCSP

1,500 practice questions

How ready are you for CCSP?

Take the entry assessment and see exactly which domains need work.

Take the assessment

24 questions · about 15 minutes · no account needed

Discussion (0)

No discussion here yet — be the first to comment.

Please sign in to join the discussion.

More posts on CCSP