External perimeter
Internet-facing services, remote access gateways and exposed applications, as an outside attacker would find them.
Initial AccessCan a determined attacker reach what matters most — and would anyone notice?
XcellHost's red team runs an authorised, objective-based exercise against your people, process and technology. We agree the crown jewels, emulate a realistic adversary within written rules of engagement, and measure how far we got against how quickly your team detected and responded.
Most organisations have scanned and pen-tested their systems. Far fewer have checked what happens when someone patient, quiet and goal-driven tries to reach the one system that would really hurt — the payments platform, the customer database, the plant historian, the board's files. That is the question a red team answers.
XcellHost Red Team Assessment is an authorised, objective-based exercise. Together with a small white team on your side, we agree the objectives, the rules of engagement and the testing windows. Our red team then emulates a realistic adversary across people, process and technology, mapped to MITRE ATT&CK tactics — while your SOC defends as it would on any normal day. At the end we put both timelines side by side and replay the key moments with your defenders.
Indian organisations now have a six-hour window to report serious incidents to CERT-In, a duty under the DPDP Act 2023 to protect personal data with reasonable safeguards, and sector regulators asking for evidence that defences are tested, not just bought. A red team is the closest you can get to a real incident without having one.
You choose the surfaces and the objectives. Anything outside the written scope is never touched.
Internet-facing services, remote access gateways and exposed applications, as an outside attacker would find them.
Initial AccessSign-in policies, MFA coverage, privileged roles and mailbox controls in your cloud identity.
Credential AccessPaths from an ordinary workstation to privileged accounts and servers, on agreed test accounts.
Lateral MovementAWS, Azure and Google Cloud roles, keys and network boundaries that could bridge to the objective.
Privilege EscalationConsent-based awareness and help-desk verification tests, agreed with HR and leadership in advance.
OptionalWhether your SOC, MDR provider or IT team sees, triages and escalates — and how fast.
Always in scopeCollection and exfiltration use synthetic marker files only — no real business or personal data leaves your environment. Destructive actions (the Impact tactic) are never performed; the objective is proven with a harmless flag.
The structure follows established threat-led testing practice: prepare, test, close. Each phase has an owner, an exit gate and a record.
Objectives, scope, white team, rules of engagement, NDA and signed authorisation letter.
Gate · signed RoEWho would target a business like yours, and how. Two or three scenarios, each with a flag.
Gate · scenarios signed offOpen-source footprinting of what is publicly visible about the organisation — outcome-level only.
Tactic · ReconnaissanceAn agreed, realistic entry route — or an assumed-breach starting point you provide.
Tactic · Initial AccessPrivilege escalation, discovery and lateral movement towards the flag, logged step by step.
Tactic · Lateral MovementReport, executive readout and a replay with your blue team, followed by a retest of the high-severity fixes.
Gate · retest closedA red team only works if leadership trusts it. Every exercise runs under a written framework that a small white team on your side controls from start to finish.
Usually the CISO, an IT lead and a legal or risk owner. They approve each phase, take deconfliction calls if your SOC escalates, and can pause or stop the exercise at any moment.
Two audiences, one set of evidence: leadership needs the risk and the decisions; engineers need the steps and the fixes.
Objectives reached or not, business impact in plain language, top five decisions. Presented to leadership.
The attack narrative phase by phase, each finding with evidence, severity, affected assets and ATT&CK tactic.
When each step ran against when it was logged, alerted, triaged and escalated — the detection gap, measured.
Prioritised fixes with owners and target dates, plus detection ideas your SOC can implement.
A replay workshop with your defenders, and a retest of high and critical findings once fixed.
A red team does not make you compliant on its own. It produces dated, independent evidence that helps you meet these expectations.
Tests whether you would spot and escalate an incident in time for the 6-hour reporting window, and whether the 180 days of logs you must keep actually reconstruct what the red team did.
Checks the reasonable security safeguards that protect personal data. Our flags are synthetic, so the exercise itself creates no personal-data exposure.
Sector frameworks expect periodic, independent testing of defences and response — for some regulated entities including red-team exercises. We map the evidence to your category.
Supports government-sector security expectations and the ISO 27001 controls for technical vulnerability management and incident response testing.
Typical objectives we agree with clients. Yours are set in the scoping workshop.
Regulators expect tested defences, and attackers target payment and approval workflows. Exercises often run assumed-breach from a branch workstation.
Cloud-native estates where identity and CI/CD access are the real perimeter.
Shared workstations, many vendors and sensitive health data under the DPDP Act.
The IT/OT boundary is the objective — OT systems themselves are observed, never touched. Pair with an OT assessment.
Customer trust depends on tenant isolation and source code protection.
Large store and warehouse footprints, seasonal peaks and payment data.
The two-week exercise covers most mid-sized organisations. Larger estates, more objectives or physical testing are scoped and quoted.
Not ready for a red team yet? Start with a purple team exercise to build detections, or breach & attack simulation to keep them working.
*Indicative placeholder price · excl. 18% GST · confirm with XcellHost before purchase.
Buying online reserves a slot. Nothing runs until scope, rules of engagement and the authorisation letter are signed.
Both run in your browser. Nothing is sent unless you ask for a quotation.
Fits the 2-week objective-based exercise.
Most mature programmes use all three, at different frequencies.
| Vulnerability scan | Penetration test | XcellHost Red Team | |
|---|---|---|---|
| Question answered | What is known-vulnerable? | How deep do the holes go? | Can an adversary reach our crown jewels unseen? |
| Scope | Every host, automated | One application or network | People, process and technology together |
| Your SOC's role | Not involved | Usually told in advance | Defends as normal — detection is measured |
| Stealth | None — noisy by design | Low | High, like a real adversary |
| Typical duration | Hours | 3–10 days | 2–8 weeks |
| Main output | List of CVEs | List of exploitable findings | Attack narrative + red vs blue timeline |
| Recommended frequency | Monthly | Yearly or after major change | Yearly, once basics are in place |
Typical timings for the 2-week exercise. Extended campaigns stretch the middle.
Objectives, surfaces, constraints and who sits on the white team.
NDA, rules of engagement and the authorisation letter.
Threat-led scenarios and flags signed off by the white team.
Within agreed windows, with daily white-team check-ins.
Executive readout, technical report and blue-team replay.
High and critical fixes verified; closure note issued.