3-minute product tour Urgent incident email
Assessment · validation

Find gaps in detection and response
and verify the improvements

The red and blue teams check how defenses perform against an agreed scenario.
We compare execution records with detection results to prioritize remediation. After the changes are in place, we retest with the same scenario.

#RedTeam#BlueTeam#PurpleTeam#AttackSimulation

In operationWe combine hands-on security validation by human testers with automated checks based on published criteria. Service standards

Service scope and process

Red and blue teams work together

The red and blue teams review the same exercise together and compare what each team observed as it happens.

Retest after remediation

After updating the rules, we rerun the same scenario and record whether the expected alerts fired.

Validation schedule tailored to the environment

We incorporate configuration changes and newly documented attack techniques into the scenario before running it again.

Direct integration with the Genox engine

Missed activity informs new detection rules for Threat Correlator. Vulnerabilities found during testing are added to the Vulnerability Scanner checklist.

Proactive security validation

We use simulated scenarios
to verify detection and response

The red team runs the agreed scenario and the blue team checks what was detected or blocked. Once the gaps are addressed, we retest under the same conditions. The scenario below is fictional.

The next validation incorporates configuration changes and new threats.

We run scenarios within the approved scope

We validate the agreed scope across externally exposed assets, internal networks, cloud environments, and AI services.

  • Use attack sequences described in recent threat reports as scenarios
  • The exercise preserves data and keeps services running.
  • Includes attack tests for AI chatbots and agents
Run the agreed scenarioExample screen
ExecutionInitial access · phishing attachment09:00
ExecutionPrivilege escalation09:12
ExecutionLateral movement on the internal network09:25
ExecutionAttempted external data transfer09:40
Validation safeguards

Approval and stop criteria
for your operating environment

Before testing, we agree in writing on the systems, time window, permitted actions, and conditions for stopping if operations are affected.

Limited to the approved scope

We agree in writing on the target assets, test window, and permitted techniques. Testing stays within that scope.

Final review before execution

A second analyst reviews test commands before execution. Actions with potentially significant impact require approval from the customer's representative.

Agree on stop criteria and who can halt the exercise

We agree on how the customer's representative can ask us to stop. We halt testing when an agreed condition is met, such as a delay in system response.

The simulation leaves data intact

The exercise excludes file deletion, encryption, and service shutdowns. We document the results in screenshots or test records within the agreed scope.

Attach execution logs

The report includes a chronological record of who ran each command, when they ran it, and what happened.

Clean up exercise artifacts afterward

We keep an inventory of accounts, files, and scheduled tasks created during testing. After the exercise, we confirm with you that all were removed.

We document each decision and its rationale for every issue we find

Some findings take time to address. Record whether you chose to patch, mitigate, monitor, or accept each issue and why. Recheck it using the same controlled scenario in the next cycle.

Example screen
ResultsProblemDecisionEvidenceOwnerRevalidation
MissedLateral movement on the internal network (SMB)Patch unavailable · detection rule addedThe older server cannot be replaced right away. We monitor it with detection rules and plan when to replace it.Monitoring teamDetected on retest
DetectionPrivilege escalation vulnerabilityPatchingA security update is available. We will apply it during the next scheduled maintenance check.Infrastructure teamBlocked on retest
DetectionAttempted data exfiltrationMitigationLower the threshold for data exfiltration alerts and add a DLP blocking policy.Security teamBlocked on retest
BlockedPhishing attachmentsMaintenanceEmail security blocked this attempt. We will check the same scenario again in the next cycle.--
Defense coverage

See how far your defenses hold
on a coverage map

We organize the results by MITRE ATT&CK tactic.
Select a cell to see the result for each technique and compare what changed after the retest.

BlockedDetected onlyMissed
Blocked 4Detection 15Missed 15Example screens using fictional data
Initial accessTA0001
ExecutionTA0002
PersistenceTA0003
Privilege escalationTA0004
Defense evasionTA0005
Credential accessTA0006
DiscoveryTA0007
Lateral movementTA0008
CollectionTA0009
Command and controlTA0011
DisclosureTA0010
ImpactTA0040
Select a cell to see the result for that technique.
Compare validation methods

Which type of validation do you need?

Finding known vulnerabilities and checking whether your monitoring team detects and responds to threats require different scopes.
Compare the objectives and deliverables in the table below.

MethodWhat you learnFrequencyDetection and response validationBest suited to
Vulnerability ScannerWhere known vulnerabilities areContinuous · automatedNot checkedWhen you need a quick, low-cost scan for known vulnerabilities across many assets
Penetration TestingVulnerabilities and exposure paths at a specific point in timeAligned with releases, changes, and auditsDepends on the assessment scopeBefore a new service launches or when you need assessment evidence for a certification audit.
Attack simulation (BAS)Whether security tools block known attacksFrequent · automatedAt the security tool levelWhen your monitoring program is established and you want to retest the same scenario frequently and automatically
Red team exerciseDefense coverage against the agreed objectivesAligned with the exercise planIncludes the team's responseWhen you need an end-to-end assessment of detection and response
Proactive validation by GenoxBlocked, detected, and missed activity before and after remediationAgreed to suit your environmentImprove detection rules and retestTo confirm that fixes close the gaps
Safety rules for industrial control equipment

When equipment is running,
here’s how we run checks

Even a brief halt in factory operations can cause significant losses. OT validation therefore follows a different sequence and different stop criteria from IT validation. We use the operational guidance in NIST SP 800-82 and IEC 62443 as our baseline.

Step 1

We monitor passively

We use mirrored network traffic to identify assets and communication paths without sending packets to the equipment.

Step 2

We validate in a test environment first

We first validate each scenario on a testbed or spare equipment. If we need to check live equipment directly, we agree on the scope and stop criteria with the equipment owner.

Step 3

We run checks during maintenance

We perform essential checks on operational equipment during scheduled maintenance or planned downtime, with the equipment owner present.

Principles

We don’t send write commands

We keep write commands, including PLC configuration changes and stop or start commands, off production equipment. We stop the checks immediately if we detect network delays.

After the site survey, we document the stop criteria, participants, and protocols and equipment models in scope. Work begins once the plan is signed.

Service configuration

Proactive security validation services

Continuous attack simulation

New vulnerabilities and configuration changes can allow an attack that your defenses previously blocked.
We regularly repeat the exercise in the operating environment and manage the test tools in Research Lab.

Key capabilities

Based on real-world attack techniques

We build scenarios from MITRE ATT&CK techniques and attack patterns documented in recent threat reports.

Designed to protect ongoing operations

We reproduce the evidence your defenses should detect while preserving data and keeping services running.

Separate blocked, detected, and missed activity

For each stage, we show whether your defenses blocked the action, raised an alert, or recorded no trace.

Add missed activity to the detection rule backlog

Missed detections go straight onto the list of Threat Correlator rules to update.

Services offered

  • Endpoint attack simulationMalware execution, privilege escalation, and attempted credential theft
  • Network attack simulationLateral movement, communication with an external command-and-control server, and attempted data exfiltration
  • Email and web attack simulationPhishing attachments, malicious links, web attack patterns
  • AI agent attack simulationPrompt injection, tool call manipulation

Process

Agree on scope and frequency

Agree on the target assets, test frequency, and prohibited actions

  • Execution plan

Scenario execution

Run validated scenarios on the agreed schedule

  • Execution records

Cross-check detection results

Compare what was blocked with what was missed

  • Defense status summary

Remediate and rerun

We retest with the same scenario after remediation

  • Remediation details

Frequently asked questions

Could the checks put a live system at risk?

We agree on the targets and timing in advance and simulate the traces your defenses should pick up. The exercise excludes damaging actions. For older equipment that may be sensitive to load, we recommend running the first few exercises outside business hours.

How does attack simulation differ from penetration testing?

Penetration testing looks for vulnerabilities in depth at a point in time. Attack simulation repeats the same scenario at intervals to check whether defenses still work. Use penetration testing for a new service and simulations to recheck defenses you have already assessed.

View all FAQs

Red team exercise

We validate defenses against the agreed objectives and record blocked, detected, and missed activity on a timeline.
We schedule preparation and results sharing around the targets and scope of the exercise.

Key capabilities

Goal-based scenarios

We define realistic attacker objectives based on your industry and organization.

Record detection times

At each stage, we record whether the security team detected the activity and when.

Executive reporting

Alongside the technical report, we provide a brief summary of what was breached in the exercise and what to address first.

Controlled execution

We keep exercise tools and outputs in the Research Lab and clean up exercise artifacts afterward.

Process

Agree on objectives and rules of engagement

Agree on the objective, scope, and prohibited actions

  • Rules of engagement

Reconnaissance and initial access

We test the scenario from external reconnaissance through initial access

  • Intrusion records

Lateral movement and access to the target

Test whether lateral movement and privilege escalation could reach the objective

  • Incident timeline

Share results

We revisit the attack timeline with the blue team

  • Findings report
  • Executive summary

Frequently asked questions

Should the security team be informed in advance?

Usually, only a few designated leads know about the exercise in advance, since advance notice can change how the team responds. We can brief the security team beforehand if you prefer. In that case, treat the recorded detection times as indicative.

View all FAQs

Blue team detection validation · Purple teaming

We replay the red team's scenario one stage at a time and review the logs alongside your security team.
For each missed detection, we update the rules and log collection settings, then retest on the spot.

Key capabilities

Find detection gaps

We identify the attack techniques that left no trace in the logs.

Improve detection rules

We review detection rules in SIEM, EDR, and Threat Correlator. Any updates require customer approval.

Retest now

We rerun the same scenario to see whether the updated rules detect it.

Defense coverage map

We map which MITRE ATT&CK techniques your defenses detect and where coverage is missing.

Services offered

  • Improve detection rulesWrite and tune detection rules for SIEM, EDR, and Genox
  • Improve log collectionAdd missing log events needed for detection
  • Review response proceduresPractice who does what after detection
  • Periodic retestingRepeat the same scenario at agreed intervals

Process

Replay simulation

Replay the red team's scenario one stage at a time

  • Execution records by stage

Review logs

Review which logs recorded each stage

  • List of detection gaps

Refine rules and settings

We update detection rules and log collection settings

  • Updated rules

Revalidation

Use the same scenario to verify the remediation

  • Defense coverage map

Frequently asked questions

Can a small security team handle this?

We can run the exercise with a small team. Your designated representative approves rule changes before they go live.

View all FAQs

Deployment inquiries

Discuss your security needs

Tell us about your operating environment and the security scope you need, and we’ll walk you through applicable configurations.

Talk to Genox
about scope and timing.

Talk to us