custom strategies.md

For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to page URLs; this page is available as Markdown.

Custom Strategies

Overview

Custom Strategies in Dropzone AI enhance outcome decision-making by allowing teams to inject targeted, organization-specific judgment into investigations. These strategies apply during the Report phase and guide the AI SOC Analyst toward more accurate conclusions—Malicious, Suspicious, or Benign—based on institutional policy, patterns, and operational context.

Custom Strategies extend Dropzone’s flexibility by enabling teams to override default interpretations of investigative findings and to encode clear, reusable guidance for recurring or high-volume alert patterns.


Purpose and Role in Investigations

Custom Strategies are Dropzone’s mechanism for defining conditional logic and interpretive guidance that goes beyond raw investigative facts. They are used to scope judgment to specific situations and ensure consistent outcomes across similar alerts.

Custom Strategies allow teams to:

For example, some organizations classify Attack Simulation alerts as benign by policy, while others treat them as malicious. A Custom Strategy can enforce the appropriate outcome consistently whenever these simulations are detected.


Best Practices

Write Like an Analyst, Think Like a Rule Engine

Custom Strategies function like if–then rules, but they should reflect the nuanced judgment of experienced SOC analysts—not raw detection logic.

Each Custom Strategy consists of two parts:

Alert Filters

Alert Filters define when a strategy applies. Filters can match on:

An investigation must match all configured filters for the strategy to apply. If no filters are defined, the strategy applies to all investigations.

Analysis Guidance

Analysis Guidance defines what outcome to recommend once filters match. Guidance is expressed using one of two guidance types:

Analysis Guidance should express reasoning about investigative evidence, not simply restate detection logic.

Example Scenario Descriptions:


Design for Clarity and Reusability

Well-designed strategies are easy to understand, audit, and reuse.


Use Custom Strategies to Reduce Noise — Not Replace Investigation

Custom Strategies are not a substitute for investigation logic.


Operational Behavior

Understanding how Custom Strategies are evaluated helps avoid surprises.

Match Evaluation

During the outcome phase, Dropzone retrieves all enabled Custom Strategies that match the investigation’s:

Within a strategy:

Across strategies:

If multiple strategies match, the final conclusion is chosen by severity priority:

Malicious → Suspicious → Benign


Outcome Tip Collation and Prompt Enrichment

When multiple strategies apply:

Insight Tag Overrides

Custom Strategies can override default insight tag behavior.

For example:

When conflicts arise, Custom Strategy guidance takes precedence.


Limitations and Considerations

Strategy Conflicts

If multiple strategies apply with conflicting recommendations, the AI weighs all guidance during prompt construction. This can reduce clarity, so regular audits are recommended.

Visibility and Traceability

Outcome tips influence final conclusions, but the strategies themselves are not directly visible to end users. Ensure outcome tips are clear and self-explanatory.

Maintenance Burden

Over time, unused or overlapping strategies can accumulate. Regular review and pruning helps prevent stale logic and unintended outcomes.


Conclusion

Custom Strategies give SOC teams a powerful way to embed institutional judgment into automated investigations. When carefully designed and maintained, they reduce noise, improve accuracy, and enforce consistent interpretations of common scenarios—without relying on playbooks or manual intervention.

When well-structured, Custom Strategies become an extension of your team’s best judgment, scaling experience and policy across every investigation.