The Cisco CCIE Security exam topics have been refreshed from v4.0 to v5.0. The new exam curriculum comprises six domains. The new segmentation into these six domains was done to improve the logical structure of the topics and to align them with Cisco’s security solutions portfolio.
Each domain lists the tasks that a minimally qualified candidate should be able to perform. Please note that the topics in the exam serve as a general guideline for the content likely to be included in the exam. Other related topics may also appear on any delivery of the exam. All domains and their tasks can appear in both the written and lab exams, making for unified exam topics.
CCIE Security v4.0
|Written Exam Topics
Lab Exam Topics
CCIE Security v5.0
|Unified Exam Topics
Compared to v4.0, the domains were renamed, reshuffled, and combined to focus more on technologies than on hardware and to create a logical structure from the perspective of security solutions deployment. The v5.0 exam introduces the latest technologies and solutions, such as NGIPS, AMP, APIC-EM, and information exchange, to keep the new unified exam topics relevant to the cutting-edge customer-based production deployment.
NOTE: Even though Domain 7 in v4.0 (Security Policies and Procedures, Best Practices, and Standards) is not specifically called out in the new exam, it is now part of Domain 5 in v5.0 (Infrastructure Security, Virtualization, and Automation).
CCIE Security Exam Changes
The decision to add or remove any task was based on the feedback received from security subject matter experts during the job role analysis and job task analysis of the v5.0 exam. Any variations in v5.0 topics from v4.0 reflect both the evolving network security environment and security job roles in the market.
Topics Removed in v4.0
Topics Added in v5.0
For the v5.0 lab exam, the hardware and software have been updated with significant virtualization of Cisco security appliances. The written exam may present questions based on the virtual instance as well the physical hardware of Cisco security appliances.
Below is comparison of hardware and software changes between v4.0 and v5.0.
CCIE Security v4.0 Hardware and Software
CCIE Security v5.0 Hardware and Software
Unified Exam Topics
The CCIE Security v5.0 exam unifies the written and lab exam topics into a unique curriculum, while explicitly disclosing which domains pertain to which exam, with their relative weight distribution.
CCIE Security v5.0 Written Exam Format
The written exam number has changed from 350-081 to 400-251. The exam will include a new educational approach ensuring that Expert-level candidates demonstrate knowledge and skills with evolving technologies such as network programmability, cloud, and the Internet of Things. The intent is to ensure that certified experts are well equipped to participate in meaningful discussions with business leaders about these new technical areas that greatly influence businesses globally.
CCIE Security v5.0 Lab Exam Format
The web-based delivery infrastructure supporting the v5.0 lab exam is very similar to v4.0. The format of the lab exam itself, however, has changed significantly. The v5.0 lab exam now comprises three modules:
- Troubleshooting Module
- Diagnostic Module
- Configuration Module
1. Troubleshooting Module
The Troubleshooting module delivers incidents that are independent of each other, meaning that the resolution of one incident does not depend on the resolution of another.
The topology that is used in the Troubleshooting module is different from the topology that is used in the Configuration module.
The Troubleshooting module is two hours long; however, the candidate can borrow up to 30 minutes from the five hours allotted to the Configuration module. In other words, the candidate can choose to use an extra 30 minutes for either the Troubleshooting module or the Configuration module.
2. Diagnostic Module
The new Diagnostic module is one hour long, and its main objective is to assess the skills required to properly diagnose network issues without having device access. These skills include the following:
- Correlate: Discerning multiple sources of documentation (such as e-mail threads, network topology diagrams, console outputs, logs, and even traffic captures.)
These activities are naturally part of overall troubleshooting skills. They are designed as a separate lab module because the format of the items is significantly different. In the Troubleshooting module, the candidate needs to be able to troubleshoot and resolve network security issues on actual devices. In the Diagnostic module, the candidate needs to make choices from among predefined options:
- What the root cause of the issue is?
- Where the issue is located in the diagram?
- What critical piece of information allows you to identify the root cause?
- What missing piece of information allows you to identify the root cause?
3. Configuration Module
The Configuration module provides a setup very close to an actual production network having security components providing various layers of security at various points in the network.
Though the major part of the module is based on virtual instances of Cisco security appliances, the candidate may be asked to work with the physical devices as well.
At the beginning of a module, the candidate has full visibility of the entire module. A candidate can choose to work in the sequence in which the items are presented or can resolve items in whatever order seems preferable and logical.
The modules in the lab exam are delivered in a fixed sequence: the Troubleshooting module, followed by the Diagnostic module, and lastly, the Configuration module. The entire lab exam is up to eight hours long.
It is important to note that the system does not allow the candidate to go back and forth between modules. When working in the Troubleshooting module, the candidate can choose to use an extra 30 minutes in addition to the two hours allotted to complete the module. However, the candidate cannot see the Configuration module at that point and cannot know where the extra time will be needed more. The total exam time is eight hours, so using the extra 30 minutes for the Troubleshooting module, means that the candidate will have only four and a half hours to complete the Configuration module. If the candidate spends only two hours on the Troubleshooting module, the Configuration module is credited by the time gained, so the candidate then has five hours to complete that module.
The web-based delivery system displays a warning message when the allotted two hours has expired in the Troubleshooting module. The system asks whether the candidate wants to continue working on the Troubleshooting module (if so, adding up to 30 extra minutes before advancing to the next module) or wants to stop working on the Troubleshooting module and advance to the Diagnostic module.
The Diagnostic module does not have terminal sessions to access the device console. This module provides the candidate with a set of documentation that represents a snapshot of a realistic situation: a point in time in an investigation that a network engineer might be facing. For example, a support engineer might need to provide a root cause analysis to a customer, help a colleague who is stuck in a troubleshooting process, or summarize the previous investigation steps.
Within the Diagnostic module, the items are presented in a format that is similar to the written exam. It includes these formats:
- Multiple choice (single answer or multiple answers)
- Point and click diagrams
The Diagnostic module questions (called troubleshoot tickets) contain a set of documentation that the candidate must consult to understand the problem scenario. Then the candidate analyzes and correlates information (after distinguishing between valuable and worthless information) to make a correct choice from among the predefined options listed in the item.
The troubleshoot tickets do not require candidates to write anything to provide the answer. All tickets are close-ended; in other words, the grading is deterministic, which ensures fair and consistent scoring. This approach also helps to grant credit to candidates who accurately identify the root cause of a networking issue but fail to resolve it within the defined constraints, which the Troubleshooting module does not offer.
Real-life experience is certainly the best training to prepare for the module. Candidates with limited experience should focus on discovering, practicing, and applying the efficient and effective troubleshooting methodologies that are used for any realistic networking challenge.
To pass the lab exam, the candidate must meet these two conditions:
- The total sum of all of modules must equal at least the minimum overall cut score.
- The sum for each individual module must equal at least the minimum cut score for the module.
These criteria prevent the candidate from passing the lab exam while failing or even bypassing a module; for example, the Diagnostic module.
The point value of each item in each lab module is shown on the candidate guide, which is provided at the lab exam. The points are granted only when all the criteria of the item are met. No partial score is granted on any item.