Best practices and recommendations

Last updated: October 19, 2026

Adopting the continuous testing model well lets you get the most value from the platform and reduce risk exposure in a sustained way. These are the practices with the most impact.

Initial setup

  • Identify your critical assets and create a Full security for them.

  • Complete the Description and Additional information of each asset with context and documentation.

  • Configure the access the agent needs: credentials, VPN, and authorization of Strike's IPs.

A good setup improves testing quality from the first run. For more details, see Requirements for an effective Threat Emulation.

Ongoing operation

  • Turn on recurrence in your Full security so testing stays up to date.

  • Review vulnerabilities regularly.

  • Prioritize based on real impact.

  • Track the lifecycle of each finding until it is closed.

The value is in continuity, not in one-off reviews.

Team integration

  • Share findings with technical teams.

  • Integrate testing into the development cycle.

  • Use the evidence for each finding to reproduce and fix the issue.

Change management

  • Set up a Change-based Threat Emulation to automatically test changes in your repositories.

  • Use a Focused Threat Emulation to validate a specific feature before a release.

  • Reduce the time between a change and its validation.

Every change can introduce new risks. To see when each type is the best fit, see Focused and Change-based Threat Emulation: how they differ and when to use each one.

Testing optimization

  • Adjust the depth and recurrence of each Full security according to the criticality of its assets.

  • On your most sensitive assets, turn on Human hacking to add manual testing by a specialist.

  • Review coverage periodically.

For more details, see How to complement a Full security: Focused, Change-based, and Human hacking.

What to avoid

  • Treating testing as a one-off activity.

  • Ignoring low-impact vulnerabilities that pile up.

  • Not updating the context of your assets.

  • Prioritizing by severity alone, without considering context.

The model's effectiveness doesn't depend only on technology, but on how it is integrated into your business operations. Good adoption lets you detect earlier, resolve faster, and reduce risk continuously.