PDF Version DemoThree versions, one decision: the CREST Certified Red Team Manager - Scenario package from ActualPDF comes as a budget-friendly printable PDF, a Windows software engine that flags your mistakes for re-practice, and an online version for any operating system. All carry the same CCRTM-SC questions.
CREST CCRTM-SC Exam Overview:
| Certification Vendor: | CREST |
|---|---|
| Exam Name: | CREST Certified Red Team Manager - Scenario |
| Exam Number: | CCRTM-SC |
| Available Languages: | English |
| Exam Price: | $850 USD |
| Related Certifications: | CCRTM-MCLF — CREST Certified Red Team Manager - Multiple Choice & Long Form |
| Certificate Validity Period: | 3 years |
| Real Exam Qty: | Scenario-based assessment (no fixed MCQ count) |
| Exam Format: | Inject-based Assessment, Written Scenario Exam, Threat Intelligence Pack Provided, Closed Book |
| Passing Score: | Not publicly disclosed (component-based pass) |
| Exam Duration: | 195 (180 min exam + 15 min reading time) |
| Recommended Training: | CREST Accredited Training Providers |
| Exam Registration: | CREST Official Registration Pearson VUE Scheduling |
| Sample Questions: |  |
| Exam Way: | Delivered at CREST examination centres / Pearson VUE authorised test centres (onsite proctored written exam) |
| Pre Condition: | No mandatory prerequisite exams; however, CREST recommends prior experience leading red team engagements within a regulated environment. |
| Official Syllabus URL: | https://www.crest-approved.org/skills-certifications-careers/crest-certified-red-team-manager/ |
CREST CCRTM-SC Exam Syllabus Topics:
| Section | Objectives |
|---|---|
| Topic 1: Red Team Engagement Management | - Scenario-Based Engagement Planning
|
Questions and Answers About CREST Certified Red Team Manager - Scenario
CREST Certified Red Team Manager - Scenario is an official CREST exam, listed under exam code CCRTM-SC. A passing result earns you the CREST Certified Red Team Manager certification at the Manager / Advanced level. It also ties into CCRTM-MCLF — CREST Certified Red Team Manager - Multiple Choice & Long Form, extending its value across your certification roadmap. Employers read this credential as verified competence, which is why it keeps appearing in job requirements.
Expect Scenario-based assessment (no fixed MCQ count) questions inside 195 (180 min exam + 15 min reading time) on the CREST Certified Red Team Manager - Scenario exam. That pace punishes hesitation, so rehearse it: the ActualPDF software engine simulates the real exam scene, reminds you of the questions you got wrong, and pushes you to re-practice them until the clock stops being your enemy.
Passing CREST Certified Red Team Manager - Scenario requires Not publicly disclosed (component-based pass), and the official registration fee is $850 USD. Retakes charge the full $850 USD again, which is why experienced candidates treat preparation as the cheaper exam fee. Verify your readiness with repeated ActualPDF practice scores above the requirement before you commit to a date.
No mandatory prerequisite exams; however, CREST recommends prior experience leading red team engagements within a regulated environment.
Requirements evolve, so confirm the current conditions before registering on the official exam page.
Registration for CREST Certified Red Team Manager - Scenario goes through the official channels listed here.
When you schedule, note that the exam is delivered Delivered at CREST examination centres / Pearson VUE authorised test centres (onsite proctored written exam).
CREST recommends the following training for CREST Certified Red Team Manager - Scenario candidates.
Follow any course with the 20 practice questions in the ActualPDF CCRTM-SC package; the software engine will even remind you which mistakes need another round.
Yes. ActualPDF provides a free download demo of the CREST Certified Red Team Manager - Scenario material, so you can check the content before choosing a version. After purchase, a one-year warranty covers you: the latest version is sent to you as it releases, free for 365 days, and after expiry you can extend the update service at a 50% discount.
Your purchase is covered by a 100% money-back guarantee with clear conditions. Take the CREST Certified Red Team Manager - Scenario exam within 60 days of purchase; if you fail, provide your unqualified result by submitting a scanned enrollment slip and the official Score Report PDF within 2 days of the exam, and the full refund is processed within 7 days. The exam must match your product, candidate and payer names must match, and attempts within 3 days of purchase, unused downloads, free materials, and expired orders are not covered. Alternatively, exchange for two other exam products of equal value, free, or wait for updates while keeping your original product's update service.
Delivery is instant: files unlock for download at payment and are emailed within one minute. If nothing arrives within 2 hours, check spam and contact customer service, which works 7/24 and normally replies within two hours. Installation is unlimited across your computers.
The CREST Certified Red Team Manager - Scenario syllabus spans 1 domains, led by Red Team Engagement Management. The complete topic list is published above; candidates who study the map first rarely get lost later.
CREST Certified Red Team Manager - Scenario Sample Questions:
Background: Your firm is delivering a red team engagement for Corvane Insurance Group, a UK-based insurer, under a standard commercial (non-regulator-mandated) intelligence-led testing contract modelled on STAR-FS. The signed authorisation letter, provided by Corvane's General Counsel and countersigned by the CISO, authorises testing of "all IT systems and infrastructure owned and operated by Corvane Insurance Group plc and its wholly owned UK subsidiaries," with an explicit exclusion list that does not mention any third parties.
During the reconnaissance phase, your team identifies that Corvane's claims-handling portal is built on a white-labelled platform actually owned and hosted by an external SaaS vendor, TrueClaim Systems Ltd, under a long-term licensing arrangement; Corvane customises the front end but has no access to or control over the underlying application server, database, or hosting infrastructure. Separately, your team also discovers that a senior Corvane underwriter has, in violation of company policy, been using a personal Gmail account to receive certain sensitive client documents due to file-size limits on the corporate system - your OSINT work has already surfaced this Gmail address and some metadata about its usage pattern from a data breach aggregation site unrelated to your engagement.
Midway through the engagement, a mid-level Corvane IT manager - not a Control Group member - emails your team directly, asking you to "just go ahead and test the claims portal properly, including the backend, since it's basically part of our system and everyone knows about it," and copies no one else on the email.
Question: Explain, with reasoning, (a) whether your team may proceed to test TrueClaim Systems Ltd's backend infrastructure based on the authorisation held and the IT manager's email, (b) how your team should handle the discovery of the underwriter's personal Gmail usage, and (c) what governance step should follow the IT manager's direct request.
Correct Answer:
See The answer in Explanation part below.
Explanation:
Step 1 - Analyse the authorisation's actual scope. The written authorisation covers systems "owned and operated by Corvane Insurance Group plc and its wholly owned UK subsidiaries." TrueClaim Systems Ltd is a separate legal entity that owns and operates the underlying claims portal infrastructure; Corvane merely licenses and customises the front end. On the facts given, TrueClaim's backend does not fall within the literal or reasonable interpretation of the authorised scope, because Corvane does not own or operate it and therefore has no authority to consent to its testing.
Step 2 - Apply the authorisation-boundary principle. As established throughout the syllabus, a client can only validly authorise testing of systems it owns or controls. Corvane's authorisation letter, however broadly worded, cannot extend legal cover to TrueClaim's infrastructure, because Corvane is not the party with authority to grant that permission. Testing TrueClaim's backend without TrueClaim's own separate, specific consent would risk unauthorised access under legislation such as the Computer Misuse Act 1990, exposing both the individual testers and the firm to potential criminal and civil liability, regardless of Corvane's own instructions.
Step 3 - Assess the IT manager's email. This email does not cure the authorisation gap, for two independent reasons: first, the IT manager is not shown to be a Control Group member or otherwise a person with the requisite authority to expand scope (the earlier syllabus material on authorisation specifically emphasises that authorisation must come from someone genuinely entitled to grant it); second, even full authority within Corvane could not authorise testing of infrastructure Corvane itself does not own, per Step 2. The informal, single-recipient nature of the email (no Control Group visibility) is itself a governance red flag consistent with the change-control principles covered elsewhere in the syllabus.
Step 4 - Correct action on TrueClaim. The team should not test TrueClaim's backend. The correct professional response is to decline politely, explain the authorisation-boundary issue to the IT manager, and escalate the request to the Control Group so it can decide, with TrueClaim's own consent obtainable and documented if genuinely desired, whether and how to pursue an amended, properly authorised scope covering that platform's backend (likely requiring TrueClaim's own testing policy or explicit sign-off).
Step 5 - Handle the personal Gmail discovery. The underwriter's personal Gmail account is not Corvane's system, and Corvane cannot authorise its testing or access - the earlier syllabus material on this exact issue (an employer cannot authorise access to accounts it does not own or control) applies directly. Your team must not attempt to access, further investigate, or exploit that Gmail account. However, the fact that a policy violation is occurring (sensitive client data being routed through an unauthorised personal account) is a genuine, relevant finding about Corvane's data handling practices and control environment. The proportionate, correct action is to report the existence and nature of this control weakness (a policy compliance/data handling gap) to the Control Group through the normal escalation and reporting channel - without extracting, reviewing, or retaining the content of the account itself - so Corvane can address the underlying process failure. This also touches data protection considerations: any personal data about the underwriter or their account incidentally learned should be handled under data minimisation principles and not gratuitously retained or elaborated upon beyond what substantiates the finding.
Step 6 - Address the IT manager's direct-contact governance issue. Beyond declining the specific request, this incident should itself be flagged to the Control Group as a governance/communication issue: it suggests scope and authorisation boundaries may not be well understood by staff outside the Control Group, and it indicates a channel-control gap (a non-Control Group individual attempting to informally direct testing activity). Best practice is to remind the Control Group of the importance of channelling all scope-related requests through the agreed escalation path, and to consider whether wider internal communication about the engagement's boundaries (calibrated so as not to compromise Blue Team blindness) is warranted.
Conclusion: Neither the written authorisation nor the IT manager's informal email extends legal cover to TrueClaim's infrastructure; the Gmail discovery must be reported as a control weakness without accessing the account itself; and both issues should be escalated transparently to the Control Group, with the direct-contact incident treated as a standalone governance concern.
---
Background: You are managing delivery of an intelligence-led engagement for Aldergate Payments Ltd, a payment services firm. The signed Rules of Engagement (RoE) explicitly prohibits any technique likely to cause denial of service, and defines a testing window of 08:00-20:00 UK time on weekdays only, reflecting the client's stated risk appetite. The RoE also names the Head of Technology Risk as the sole point of contact for the stop-testing procedure, with a mobile number and a backup email address.
On the Wednesday of week 6 (of a planned 8-week engagement), at 19:40, your lead tester successfully authenticates to an internal application using credentials obtained through an earlier, authorised phishing simulation. At 19:52, while exploring the application's functionality (within the agreed testing window, which ends at 20:00), the tester notices the application beginning to respond unusually slowly, and error messages referencing database connection timeouts start to appear in the application's own interface. The tester immediately stops all interactive activity with the application at 19:54. At 19:57, the tester attempts to call the Head of Technology Risk's mobile number as specified in the RoE stop procedure; the call goes to voicemail.
The backup email address also fails to send, with an automated "mailbox full" bounce-back message. By 20:
05, the tester has been unable to reach anyone, and has no confirmation of whether the slowdown is related to their activity, a coincidental unrelated issue, or something else.
Question: Explain what your lead tester and you, as Red Team Manager, should each do in the immediate aftermath of this situation (the next 30-60 minutes), and identify the governance and Rules of Engagement weaknesses this incident has exposed that should be addressed before testing resumes.
Correct Answer:
See The answer in Explanation part below.
Explanation:
Step 1 - Confirm the immediate tester-level response was correct. Stopping all interactive activity with the application the moment anomalous behaviour was observed (19:54) was the right first action, consistent with the RoE's implicit expectation that testers exercise caution around any sign of potential service impact, even absent an explicit instruction to halt at that exact moment. This should be affirmed, not criticised, in any post- incident review - the tester exercised appropriate professional judgement.
Step 2 - Recognise the escalation channel has failed, and escalate further immediately. The named stop- testing contact being unreachable by both listed channels is a serious, live risk-management gap: the RoE's single point of contact and single backup channel have both failed simultaneously. The tester (and you, once informed) must not simply wait passively. The correct immediate action is to escalate through any other reasonable, available means: contacting the Control Group chair or other known senior client stakeholders directly (even if not the named RoE contact), using any other documented emergency contact details held by your firm (e.g., from the kickoff meeting contact list, main switchboard, or account management relationship), and internally escalating to your own firm's senior management/Test Director so the incident is being actively managed rather than left with a single tester.
Step 3 - Preserve evidence and document a precise timeline. You and the tester should immediately and precisely document the timeline: exact timestamps of the observed anomaly, the decision to stop, and every attempted escalation contact (including the voicemail and bounce-back), together with exactly what technical activity was being performed in the minutes before the anomaly appeared. This record is essential both for genuinely understanding whether the Red Team's activity contributed to the issue, and as a contemporaneous account protecting the firm and the individual tester if the legality or conduct of the engagement is later questioned.
Step 4 - Do not resume testing on the affected system until contact and clarity are achieved. Testing on the affected application (and arguably more broadly, pending clarification) should remain paused until the Red Team Manager has made actual contact with an appropriate, accountable client stakeholder, confirmed the client's current understanding of the system's status, and received explicit direction on whether and how testing should continue. Resuming activity on the affected system without this confirmation, simply because the scheduled window reopens the next morning, would be an unacceptable risk given the unresolved uncertainty about what caused the slowdown.
Step 5 - Once contact is made, support the client's own investigation. When a client contact is finally reached (whether that evening or the next morning), the Red Team Manager should proactively share the precise timeline and technical detail from Step 3, to help the client's own team determine quickly whether the Red Team's activity was a contributing factor, and offer to pause the wider engagement if needed while this is established, rather than downplaying the incident to keep the schedule on track.
Step 6 - Identify and remediate the governance/RoE weaknesses exposed. Before testing resumes, several weaknesses must be addressed and, where appropriate, formally reflected in an updated RoE through change control: (i) reliance on a single named individual with no genuinely independent backup contact is a single point of failure and should be replaced with at least one alternate/deputy contact with equivalent authority, consistent with the continuity planning principles covered elsewhere in the syllabus; (ii) the backup email channel being allowed to reach a full, non-monitored mailbox indicates the channel was not actually being maintained as a reliable emergency channel - this should be tested/verified periodically, not merely documented on paper; (iii) the incident should prompt a rehearsal or "dry run" check of the stop-procedure contacts going forward, consistent with the syllabus principle that escalation procedures benefit from practical verification, not just written definition; and (iv) the Control Group should be briefed on the incident and the contact/process gaps, so it can decide on any wider corrective action.
Conclusion: The tester's decision to halt activity was correct and should be reinforced; the priority afterward is aggressive, multi-channel escalation and evidence preservation rather than passive waiting or unilateral resumption; and the incident should trigger a formal review and strengthening of the RoE's single-point-of- failure escalation contact structure before testing continues.
---
