- What the GCPN Certification Actually Certifies
- The Exam at a Glance
- The 12 Published Exam Objectives
- Hands-On Topics You Must Know Cold
- Working With an Open-Book Format
- Where SANS SEC588 Fits
- Fees, Registration and Attempt Mechanics
- Validity and Renewal
- Who Hires GCPN Holders
- Sequencing Your Preparation Around the Domains
- Frequently Asked Questions
- GCPN is GIAC's Cloud Penetration Tester credential: one proctored exam, 75 questions, 2 hours, 70% minimum to pass.
- GIAC publishes 12 objective headings but no percentage weights, so prepare evenly rather than guessing at emphasis.
- No prerequisites exist, and SANS SEC588 training is recommended but optional.
- The exam is open book with paper references only; electronic materials and practice Q&A content are prohibited.
What the GCPN Certification Actually Certifies
The GCPN credential is the GIAC Cloud Penetration Tester certification, issued by GIAC Certifications. It validates that a candidate can plan and execute penetration tests against cloud environments, with a clear emphasis on Amazon Web Services and Microsoft Azure, along with the containers, pipelines and web applications that run on them. If you are new to the name itself, our explainers on what GCPN certification is and what GCPN stands for cover the basics.
One naming note is worth knowing before you search for resources. GIAC's current public page titles the credential "GIAC Cloud Penetration Tester," yet some older listings and even a testimonial on the issuer's page still use the "Cloud Penetration Testing" variant. They refer to the same GCPN credential, and no formal rename date has been published, so do not read anything into the wording difference when you see both in the wild.
This is an offensive-security certification, not a cloud-architecture or general cloud-security one. The objectives lean toward how an attacker discovers, authenticates to, pivots through and abuses cloud services, which shapes everything about how you should prepare.
The Exam at a Glance
The format is deliberately compact. Here is what GIAC publishes for the exam:
| Item | Detail |
|---|---|
| Number of exams | One web-based, proctored exam |
| Questions | 75 |
| Time limit | 2 hours |
| Minimum passing score | 70% (for exam versions released on or after 2021-02-13) |
| Reference policy | Open book, paper references only |
| Testing providers | Pearson VUE onsite or ProctorU remote, per GIAC's assigned modality |
| Prerequisites | None required |
| Validity | 4 years |
Do the arithmetic early: 75 questions in 120 minutes leaves roughly 96 seconds per question. That is generous for recall items and tight for anything that asks you to interpret command output, read a policy document or reason through an attack path. For a deeper look at the pass threshold, see our GCPN passing score breakdown.
Your GIAC account's Certification Information governs the details of the specific attempt you purchase, including the objectives, question types, format and passing score that apply to it. Check it after you register, because that private page is the final word for your attempt.
The 12 Published Exam Objectives
GIAC lists twelve objective headings. It does not publish percentage weights for them, so there is no honest way to say which one is "worth the most." The list below reproduces the headings in the order GIAC presents them, with notes on what each implies for your preparation. For a fuller walkthrough, see our complete guide to all 12 GCPN content areas.
1. AWS Authentication and Cloud Services
Understanding how identities, credentials and permissions work in AWS, and how the core services behave when you are testing them.
- How AWS credentials and sessions are issued and used
- How core AWS services expose data and functionality to an authenticated principal
2. Azure Functions and Windows Containers
Serverless and containerized workloads on the Microsoft side of the house, including how they can be reached and abused.
- Attack surface of Azure Functions
- Windows container behavior in Azure contexts
3. Cloud CLI and Application Mapping
Using vendor command-line tooling to enumerate what exists, and mapping how applications are assembled from cloud components.
- Reading CLI output quickly and accurately
- Turning enumeration results into a map of the target
4. Cloud Native Applications and CI/CD Pipelines
Modern delivery pipelines are a target in their own right, because they hold secrets and deployment authority.
- How pipelines are structured and where trust is placed in them
- What a compromised pipeline lets an attacker do
5. Cloud Penetration Testing Fundamentals
The foundations: scoping, rules of engagement and how cloud testing differs from traditional network testing.
- Shared-responsibility implications for what you may test
- Methodology adapted to cloud environments
6. Containers and Kubernetes Structure
The architecture of container platforms and orchestration, which you need to understand before you can attack it.
- Components of a Kubernetes cluster and how they relate
- Container isolation and where it breaks down
7. Discovering Cloud Services and Data
Finding what an organization actually has exposed in the cloud, including data stores.
- Identifying cloud-hosted assets from the outside
- Locating exposed storage and data
8. Microsoft Azure Cloud Services and Attacks
The Azure counterpart to the AWS authentication objective, covering services and the attacks that apply to them.
- Azure identity and service behavior
- Attack techniques specific to Azure resources
9. Password Attacks on Cloud Environments
Credential-focused attacks as they apply to cloud-facing authentication.
- How password attacks differ when the target is a cloud identity endpoint
- Recognizing what defenses change the attack approach
10. Red Team Penetration Testing of Cloud Environments
Adversary-style engagements against cloud estates, going beyond finding individual flaws to chaining them.
- Moving from initial access to meaningful objectives
- Thinking in attack paths rather than isolated findings
11. Redirection and Attack Obfuscation
Techniques for routing and disguising offensive activity in cloud contexts.
- How attackers use cloud infrastructure to hide origin
- How defenders and testers reason about that traffic
12. Web Application Attacks
Classic web vulnerabilities, viewed through the cloud lens: applications that run on, and reach into, cloud services.
- Web flaws that become cloud compromise, such as reaching metadata or credentials
- How application bugs bridge into the underlying cloud account
Hands-On Topics You Must Know Cold
Because the exam is open book, memorizing definitions matters less than being able to apply them quickly. Several themes run across the twelve objectives and deserve repeated hands-on practice.
Authentication is the connective tissue
Two of the twelve objectives name AWS and Azure directly, and a third covers password attacks. Identity is where cloud compromises usually begin and where they escalate. Know how each platform represents a principal, how temporary credentials are obtained, and what a leaked credential can reach. If you can reason fluently about "I have this identity, what can I do next?" on both platforms, you are covering a large share of the exam's practical logic.
Enumeration through the CLI
The objective on cloud CLI and application mapping signals that command-line fluency is tested. Practice running enumeration commands and, more importantly, interpreting the output without hesitation. Questions in this area tend to reward candidates who have actually typed these commands rather than only read about them.
Containers, Kubernetes and pipelines together
Containers and Kubernetes structure, cloud-native applications and CI/CD pipelines are three separate objectives, but real engagements blur them. A pipeline holds secrets, deploys containers, and those containers run in a cluster. Build a mental model of that chain so that a question about one link does not catch you out because you only studied it in isolation.
The web-to-cloud bridge
Web application attacks appear as their own objective, but their cloud-specific value is as an entry point. A flaw in a web application can expose credentials or reach internal cloud services. Practice thinking about web bugs in terms of what cloud access they ultimately deliver.
Working With an Open-Book Format
The exam allows paper references. Electronic references, internet access and any materials containing exam or practice Q&A are prohibited, according to GIAC's proctored exam reference guidance. That last restriction matters: do not bring annotated copies of question banks, and read the rules before exam day rather than assuming.
The practical implication is that the value of your notes lies in their organization, not their volume. A well-indexed set of your own notes, mapped to the twelve objective headings, lets you find a command syntax or a service behavior in seconds. A pile of unindexed printouts will cost you minutes you do not have at roughly 96 seconds per question. Build the index as you study, and treat the process of building it as a learning exercise in itself. Our GCPN cheat sheet is a useful starting point for deciding what belongs on your quick-reference pages, and the GCPN study guide goes further on organizing your preparation.
Key Takeaway
Structure your paper references by the twelve GIAC objective headings, with a tabbed index. In an open-book exam with a short clock, retrieval speed decides how much your references are actually worth.
Where SANS SEC588 Fits
GIAC recommends the SANS course SEC588: Cloud Penetration Testing as the associated training. The training is optional: no prerequisites are required to begin the certification process, so you may attempt the exam without taking the course. Our pages on GCPN training and GCPN requirements cover this in more detail.
Be careful about one distinction. The SEC588 syllabus is a preparation curriculum, and its sections inform what you should study, but they do not establish the exam's official domain structure or guarantee exhaustive exam coverage. The twelve objective headings above are the issuer's published scope; the course is a means of building the skills. Likewise, course hours, labs and capstones are separate from the two hours of proctored exam time, so do not confuse time spent in training with exam pacing.
Fees, Registration and Attempt Mechanics
The published figures, all excluding tax, are as follows:
| Item | Price (USD) |
|---|---|
| Exam attempt | 999 |
| Retake | 899 |
| Optional practice exam | 399 |
| Certification renewal | 499 |
A standalone attempt gives you initial access for 120 days from activation, and extensions are available under GIAC's attempt delivery policy. That window is your real deadline, so activate your attempt when you are ready to start the clock, not simply when you pay. A full cost breakdown, including training considerations, is in our GCPN certification cost guide, and scheduling specifics are covered in GCPN exam dates and windows.
Testing is delivered by Pearson VUE at test centers or by ProctorU remotely, depending on the modality GIAC assigns to your attempt. If you test remotely, confirm your environment and equipment requirements well in advance, since proctoring rules are strict about workspace and materials.
Validity and Renewal
The certification is valid for four years. To renew, you need either 36 approved CPE credits earned during the active four-year cycle or a passing renewal exam, plus the renewal fee. Because the cloud landscape changes quickly, the CPE route is attractive for working practitioners, since the learning you do on the job and at conferences can count toward renewal. Keep records as you go, rather than reconstructing them in the final months.
Who Hires GCPN Holders
The credential maps most directly to roles where someone is paid to attack cloud environments on behalf of the organization that owns them. Typical employers include:
- Security consultancies that sell penetration testing and red team engagements to clients migrating to or operating in AWS and Azure.
- Internal red teams and offensive security groups at organizations with large cloud footprints.
- Product security and application security teams that need to validate cloud-hosted applications and delivery pipelines.
- Cloud security assessment practices within larger technology and managed-services providers.
Job titles vary widely, so search on the skills (cloud penetration testing, red team, AWS and Azure assessment) rather than on a single title. For more on roles, see GCPN jobs. On compensation, we deliberately avoid quoting figures here because none are published by the certifying body; the GCPN salary guide and the GCPN ROI analysis discuss the question qualitatively.
Sequencing Your Preparation Around the Domains
Since GIAC publishes no weights, an even spread of effort is the sensible default, with extra time on whichever objectives are weakest for you. The one place where order genuinely matters is dependency: later objectives assume earlier foundations. A reasonable sequence follows the logic below.
Foundations and identity
- Cloud Penetration Testing Fundamentals, to settle scoping and shared-responsibility rules
- AWS Authentication and Cloud Services, then Microsoft Azure Cloud Services and Attacks, since identity underpins everything after
Enumeration and discovery
- Cloud CLI and Application Mapping, with daily hands-on command practice
- Discovering Cloud Services and Data, and Password Attacks on Cloud Environments
Compute, containers and delivery
- Containers and Kubernetes Structure before attacking it
- Azure Functions and Windows Containers, plus Cloud Native Applications and CI/CD Pipelines
Chaining and integration
- Web Application Attacks as a bridge into the cloud account
- Red Team Penetration Testing of Cloud Environments and Redirection and Attack Obfuscation, then a full-length timed review and a final pass over your paper index
The reasoning is simple: the red team and obfuscation objectives are easiest once you can already enumerate, authenticate and move through the individual services, so save them for the end. Adjust the timeline to your own experience; someone with strong Kubernetes background can compress weeks 5-6, while a candidate new to Azure should lengthen weeks 1-2. For a sense of calibration, see how hard the GCPN exam is, and when you want timed repetition under exam-like conditions, use our GCPN practice tests to find the objectives that still need work.
Frequently Asked Questions
GCPN is the GIAC Cloud Penetration Tester credential, issued by GIAC Certifications and administered by GIAC, LLC. It is the same credential some sources label "GIAC Cloud Penetration Testing."
The exam is one web-based, proctored test with 75 questions and a 2-hour limit. The minimum passing score is 70% for exam versions released on or after 2021-02-13.
No. No prerequisites are required to begin the certification process, and training is optional. SEC588 is the recommended preparation course, but the exam can be attempted without it.
Yes, in paper form only. The exam is open book with paper references. Electronic references, internet access and materials containing exam or practice Q&A are prohibited under GIAC's proctoring rules.
It is valid for four years. Renewal requires either 36 approved CPE credits earned in the cycle or a passing renewal exam, plus the USD 499 renewal fee, exclusive of tax.
For a broader introduction to the credential, you can also read our overview of the GCPN, then return to the objectives above and build your plan around them.