Red team: test a scenario
Use an agreed adversary objective to assess attack paths and defensive response within a controlled engagement.
SPECIALIST SECURITY / IT MOUNTAIN
Explore a realistic security scenario and learn how your controls and people respond. Set a useful objective, agree the rules and turn the exercise into better defensive practice.

THE SERVICE IN PRACTICE
Choose the activities that address your actual risks. Your service schedule confirms the supported estate, deliverables and responsibilities.
Use an agreed adversary objective to assess attack paths and defensive response within a controlled engagement.
Review monitoring, investigation and response practices around the systems and techniques in scope.
Share offensive and defensive observations to improve visibility, detection and response.
Agree oversight, permissions, communications, evaluation and stop conditions for the exercise.
THE RIGHT LEVEL OF KNOWLEDGE
Little prior knowledge is supplied. This can help explore what is visible or accessible to an outsider within agreed targets and time. It is not automatically the deepest assessment.
Provide selected credentials or system knowledge to focus testing on relevant workflows, user roles or an agreed attack scenario.
Provide architecture, configuration, source code or administrative access where appropriate, to enable a more informed review within the agreed scope.

BUILT AROUND YOUR BUSINESS
Start with the concern you want to address. Then agree the systems, people and evidence that belong in scope, including any specialist delivery needed.
Choose a scenario, participants and the business question to answer.
Record authorised targets, techniques, exclusions and safety controls.
Evaluate the scoped attack and response while maintaining agreed oversight.
A PLANNED START
Choose a scenario, participants and the business question to answer.
Record authorised targets, techniques, exclusions and safety controls.
Evaluate the scoped attack and response while maintaining agreed oversight.
Turn observations into detection changes, action owners and follow-up checks.
A CONTRACT YOU CAN UNDERSTAND
IT Mountain coordinates the agreed service. Specialist assessment or security operations may be delivered by an appointed provider. The proposal identifies responsibilities, access and the route to support.
Define supported users, devices and systems, monitoring hours, response commitments and approval points. Licences, testing, major changes and specialist recovery are itemised where separately scoped.
Keep findings, action owners and unresolved risks visible. Agree a review cadence so the service follows changes in your organisation rather than standing still.
Tell us what needs protecting and what a better service would look like.
TECHNOLOGY WITH A PURPOSE
Explore what each capability does and where it could help. We’ll confirm the selected technology, licensing, delivery team and support responsibilities in your proposal.
Get testing evidence and practical support for assurance requirements.
Use specialist testing to understand weaknesses in agreed networks, applications and cloud environments. Assessment scope, report deliverables and any independent certification route are confirmed for the engagement.
Explore weaknesses across the systems your business relies on.
Agree the targets, test perspective and deliverables before technical assessment begins. Findings should help your team understand the weakness, its impact and the route to remediation.
Get an objective view of your critical systems and configurations.
Choose assessments around the applications, infrastructure and cloud settings that matter to your organisation. Confirm the testing specialists, engagement credentials and reporting scope before delivery.
Explore the route an attacker could take and how your defences respond.
Define a realistic business objective, permitted techniques and the defensive response to evaluate. An exercise needs agreed rules, safety boundaries and clear learning outcomes.
Investigate exploitable weaknesses within an authorised scope.
Plan specialist assessment around agreed targets, test windows and business priorities. Reports explain evidence and remediation, with follow-up or retesting defined in the engagement.
Connect recurring assessment with reporting and remediation.
Build a testing rhythm around meaningful changes and the systems you need to assess. Agree engagement coverage, access to findings and how remediation is reviewed over time.
Capabilities are selected and scoped for your environment. Your agreement identifies the appointed technology and delivery providers before the service begins.
YOUR QUESTIONS
A penetration test often focuses on weaknesses in defined systems. An objective-led team exercise can assess attack paths and the response across selected technology and people. The written scope establishes what is being evaluated.
Only where explicitly authorised and carefully scoped. The engagement must define permitted scenarios, participants, data handling, safeguarding and stop conditions.
Those labels are sometimes used for secure design, offensive insight shared with builders and defensive feedback to engineering. Terminology varies. We specify the actual activities and outcomes rather than promising a colour alone.