Home›Security›Security Assessment›Red Team Assessment

XcellSecure|Red Team Assessment

Can 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.

Powered by VXcellHost Vortex SOC · Mumbai Authorised adversary emulation by the XcellHost red team
Written authorisationrules of engagement signed first
No production impactagreed testing windows
OPERATIONRT-2611 · sample 01 · Objective map
Red · objective—
vs
Blue · detection—
Crown-jewel objectives
Threat-led scenarios
MITRE ATT&CK tactic mapping
Detection & response measured
Replay with your blue team
INR billing with GST
✦Ask AI about Red Team AssessmentChatGPTClaudePerplexityGoogle AICopilot
Works with Microsoft 365Active Directory & Entra IDAWS · Azure · GCPEDR / XDRSIEM & SOCVPN & remote access
ISO 27001 & 20000-1Microsoft Gold Partner10,000+ customersSince 199999.95% uptime SLA24×7 NOC + SOC
Overview

A penetration test finds the holes. A red team finds out whether anyone is watching them.

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.

Objective firstSuccess is reaching an agreed flag, not counting vulnerabilities.
Detection measuredEvery phase is timed against when your team saw it.
Governed end to endWritten authorisation, RoE, NDA and a stop switch.
Ends in learningA replay with your blue team turns findings into detections.
Why it matters in India

Attackers don't stop at the first vulnerability. Your testing shouldn't either.

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.

  • Detection speed is the real control. The gap between an attacker's first step and your first alert decides whether you report a near-miss or a breach.
  • People and process get tested too. Escalation paths, on-call handovers and approval workflows are where real incidents stall.
  • Tools overlap and gaps hide between them. EDR, SIEM, email security and identity protection each see part of the story.
Attacker progress vs first detectionillustrative · sample
Reconnaissance
Initial Access
Privilege Escalation
Lateral Movement
Objective
First detection · day 7 After replay · day 2
Day 0246810
Scope · what we assess

Every route an adversary would try — within the lines you draw.

You choose the surfaces and the objectives. Anything outside the written scope is never touched.

External perimeter

Internet-facing services, remote access gateways and exposed applications, as an outside attacker would find them.

Initial Access

Identity & Microsoft 365

Sign-in policies, MFA coverage, privileged roles and mailbox controls in your cloud identity.

Credential Access

Internal network & AD

Paths from an ordinary workstation to privileged accounts and servers, on agreed test accounts.

Lateral Movement

Cloud workloads

AWS, Azure and Google Cloud roles, keys and network boundaries that could bridge to the objective.

Privilege Escalation

People & process

Consent-based awareness and help-desk verification tests, agreed with HR and leadership in advance.

Optional

Detection & response

Whether your SOC, MDR provider or IT team sees, triages and escalates — and how fast.

Always in scope
MITRE ATT&CK tactics · how each is treatedExercisedSimulated onlyOut of scope by default
ReconnaissanceInitial AccessExecutionPersistencePrivilege EscalationDefense EvasionCredential AccessDiscoveryLateral MovementCollectionCommand and ControlExfiltrationImpact

Collection 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.

Methodology

Six phases, one storyline — from authorisation to replay.

The structure follows established threat-led testing practice: prepare, test, close. Each phase has an owner, an exit gate and a record.

01

Plan & authorise

Objectives, scope, white team, rules of engagement, NDA and signed authorisation letter.

Gate · signed RoE
02

Threat-led scenarios

Who would target a business like yours, and how. Two or three scenarios, each with a flag.

Gate · scenarios signed off
03

Reconnaissance

Open-source footprinting of what is publicly visible about the organisation — outcome-level only.

Tactic · Reconnaissance
04

Initial access

An agreed, realistic entry route — or an assumed-breach starting point you provide.

Tactic · Initial Access
05

Move to objective

Privilege escalation, discovery and lateral movement towards the flag, logged step by step.

Tactic · Lateral Movement
06

Close & replay

Report, executive readout and a replay with your blue team, followed by a retest of the high-severity fixes.

Gate · retest closed
Governance & safety

Realistic for your defenders. Controlled for your business.

A 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.

White team2–4 people · your side · aware of the exercise

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.

Written authorisationA signed letter naming the organisation, systems, dates and people — nothing starts without it.
Rules of engagementIn-scope and out-of-scope systems, allowed and forbidden methods, escalation contacts and stop conditions.
Safe testing windowsSensitive steps only in agreed windows; business-critical periods such as month-end are blocked out.
No production impactNo destructive actions, no service disruption, no changes left behind. Test accounts and artefacts are removed at close.
Data handlingFlags are synthetic. Evidence is encrypted, kept only for the agreed period and then destroyed with a certificate.
NDA & named teamA mutual NDA, and every tester named to the white team before the exercise begins.
Deliverables

What you receive — and what changes after.

Two audiences, one set of evidence: leadership needs the risk and the decisions; engineers need the steps and the fixes.

Executive summary & readout

Objectives reached or not, business impact in plain language, top five decisions. Presented to leadership.

Technical report

The attack narrative phase by phase, each finding with evidence, severity, affected assets and ATT&CK tactic.

Red vs blue timeline

When each step ran against when it was logged, alerted, triaged and escalated — the detection gap, measured.

Remediation plan

Prioritised fixes with owners and target dates, plus detection ideas your SOC can implement.

Replay & retest

A replay workshop with your defenders, and a retest of high and critical findings once fixed.

Open findings after the reportillustrative · sample
HighFinding #12 · public storage bucketfixed in 48 h · retest passed (sample)
India compliance mapping

Evidence your auditors and regulators recognise — without overclaiming.

A red team does not make you compliant on its own. It produces dated, independent evidence that helps you meet these expectations.

CERT-In directions (April 2022)

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.

DPDP Act 2023

Checks the reasonable security safeguards that protect personal data. Our flags are synthetic, so the exercise itself creates no personal-data exposure.

RBI · SEBI CSCRF · IRDAI

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.

MeitY & ISO 27001

Supports government-sector security expectations and the ISO 27001 controls for technical vulnerability management and incident response testing.

6 hCERT-In incident reporting window
180 dayslog retention under CERT-In directions
1 timelinered vs blue, dated, for your audit file
Use cases by industry

Different businesses, different crown jewels.

Typical objectives we agree with clients. Yours are set in the scoping workshop.

Banks, NBFCs and insurers

Regulators expect tested defences, and attackers target payment and approval workflows. Exercises often run assumed-breach from a branch workstation.

  • Approve a payment in the test approval workflow
  • Reach the core-banking jump host
  • Read a synthetic file on the treasury share

Fintech and payment companies

Cloud-native estates where identity and CI/CD access are the real perimeter.

  • Obtain a privileged cloud role in a non-production account
  • Reach the build pipeline's deployment secrets store
  • Read a synthetic record from the merchant database

Hospitals and diagnostics

Shared workstations, many vendors and sensitive health data under the DPDP Act.

  • Reach the patient-records application with a test identity
  • Move from the guest network to the clinical VLAN
  • Prove access to imaging storage with a marker file

Manufacturers and plants

The IT/OT boundary is the objective — OT systems themselves are observed, never touched. Pair with an OT assessment.

  • Reach the IT/OT boundary jump server
  • Read the plant historian's read-only replica
  • Obtain a vendor remote-access account

IT services and SaaS

Customer trust depends on tenant isolation and source code protection.

  • Reach a synthetic customer tenant from a staff laptop
  • Gain write access to a source repository
  • Obtain a support-desk administrator session

Retail and e-commerce

Large store and warehouse footprints, seasonal peaks and payment data.

  • Reach the order-management back office
  • Move from a store network to head-office servers
  • Read a synthetic customer list from the CRM
Packages

One fixed-scope exercise. Longer campaigns on quote.

The two-week exercise covers most mid-sized organisations. Larger estates, more objectives or physical testing are scoped and quoted.

Fixed scopeObjective-based Red Team2-week exercise · one-time
from₹4,99,999*
Indicative — confirm with XcellHost · excl. 18% GST
  • Scoping workshop, RoE & authorisation
  • Up to 2 threat-led scenarios & flags
  • External, identity & internal surfaces
  • Red vs blue detection timeline
  • Report, executive readout & replay
  • Retest of high & critical findings
Configure & add to cart
Extended Red Team Campaign3–8 weeks · multiple objectives
On quote
sized on objectives, sites & surfaces
  • Everything in the 2-week exercise
  • 3 or more scenarios and flags
  • Multi-cloud and group companies
  • Consent-based people testing
  • Physical access testing (optional)
  • Unannounced test of your SOC or MDR
Scope my campaign

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.

Configurator

Build your order — see GST and the total before you commit.

Buying online reserves a slot. Nothing runs until scope, rules of engagement and the authorisation letter are signed.

Package 2-week exercise
Starting point Full scope
Exercises in the next 12 months 1
Detection test
Included in every exerciseRoE & white teamRed vs blue timelineReplay workshopHigh/critical retest
Your order
Objective-based Red Team · 2 weeks
Full scope · unannounced detection test
Indicative — confirm with XcellHost. Prices in INR excl. 18% GST; cart total = price × quantity × 1.18.
Tools

Two quick checks before you book.

Both run in your browser. Nothing is sent unless you ask for a quotation.

Red team readiness check8 questions · 1 minute
Engagement scoperestimate duration and package fit
Objectives (flags) 2
Surfaces
Starting point
Estimated duration2 weeks

Fits the 2-week objective-based exercise.

    Compared

    Scan, pen test or red team — each answers a different question.

    Most mature programmes use all three, at different frequencies.

    Vulnerability scanPenetration testXcellHost Red Team
    Question answeredWhat is known-vulnerable?How deep do the holes go?Can an adversary reach our crown jewels unseen?
    ScopeEvery host, automatedOne application or networkPeople, process and technology together
    Your SOC's roleNot involvedUsually told in advanceDefends as normal — detection is measured
    StealthNone — noisy by designLowHigh, like a real adversary
    Typical durationHours3–10 days2–8 weeks
    Main outputList of CVEsList of exploitable findingsAttack narrative + red vs blue timeline
    Recommended frequencyMonthlyYearly or after major changeYearly, once basics are in place
    Engagement steps

    From first call to retest in about six weeks.

    Typical timings for the 2-week exercise. Extended campaigns stretch the middle.

    1. Week 0Scoping call

      Objectives, surfaces, constraints and who sits on the white team.

    2. Week 0–1Paperwork signed

      NDA, rules of engagement and the authorisation letter.

    3. Week 1Scenarios agreed

      Threat-led scenarios and flags signed off by the white team.

    4. Week 2–3Exercise runs

      Within agreed windows, with daily white-team check-ins.

    5. Week 4Report & replay

      Executive readout, technical report and blue-team replay.

    6. Week 5–6Retest

      High and critical fixes verified; closure note issued.