Test recurrence and depth

The Strike platform lets you configure testing around two key variables: depth and recurrence.

These two dimensions define the level of coverage, how often assessments run, and how well risks can be detected over time.

Testing depth

Depth defines the level of analysis applied to each asset, shaping how much time, context, and complexity go into its evaluation.

There are three levels:

Deep

Exhaustive testing with maximum coverage and accuracy.

Technical features:

• Extended reconnaissance with attack path discovery

• Advanced exploit chaining, combining lower-severity findings into high-impact scenarios

• In-depth evaluation of business logic and complex multi-step attacks

• Longer execution time per target, prioritizing thoroughness over speed

👉 Ideal for critical assets, pre-launch reviews, and high-value targets.

Medium

Balanced analysis focused on the most exposed attack surface.

Technical features:

• Targeted reconnaissance on the main entry points

• Validation of known vulnerabilities and common attack patterns

• Coverage of critical flows (authentication, sensitive endpoints, etc.)

• Tuned for faster response times without losing depth on key areas

👉 Ideal for regular security checks and relevant assets.

Superficial

Automated assessment to validate the overall security posture.

Technical features:

• Automated scan based on detection of known vulnerabilities

• Identification of insecure configurations and common exposures (CVEs, misconfigurations)

• Broad coverage focused on catalogued risks

• Fast, scalable execution across multiple assets

👉 Ideal for low-criticality assets and continuous monitoring.

Testing recurrence

Recurrence defines how often an asset is evaluated.

Typical options:

• Monthly

• Quarterly

• Bi-annual

• Annual

👉 The recommended frequency depends on:

• The asset's criticality

• How often it changes

• Its level of exposure

💡 FAQ

Can recurrence be turned on or off?

Yes. Recurrence can be turned off at any time.

Doing so stops future executions on the asset. However, this doesn't free up the assigned capacity — it simply pauses the next execution until recurrence is turned back on.

👉 When you turn it back on, testing resumes according to the defined setup.

How they work together

Final coverage comes from how depth and recurrence are combined.

For example:

• Critical asset → Deep + high recurrence

• Stable asset → Medium + lower frequency

👉 This lets you adapt testing to the real context of the business.

Why recurrence matters

In dynamic environments, systems are constantly changing.

That means:

• New vulnerabilities can surface at any moment

• A one-off test quickly loses relevance

👉 Continuous validation helps detect risks as they emerge.

Business impact

Configuring depth and recurrence well lets you:

• Detect vulnerabilities earlier

• Shorten the exposure window

• Prioritize security resources

• Keep up with the pace of change

👉 It's not about testing more — it's about bringing risk down over time.

Combining depth and recurrence is how you build a testing strategy that's aligned with the business, ensuring continuous coverage and early risk detection.