LogicBounce Research

Detection Engineering

Behavioral Detections for Modern Enterprise Threats

A detection that doesn’t fire when it should is worse than no detection at all — it creates false confidence. Our Detection Engineering team builds, validates, and continuously maintains high-fidelity behavioral detections across identity, cloud, endpoint, SaaS, network, and AI systems. Every detection ships to Nexus customers automatically.

500+
Production detections
<2%
False positive rate target
Weekly
New detection releases

Detection Coverage Domains

  • Identity & Credential Detections
  • Cloud Infrastructure Detections
  • Endpoint Behavioral Detections
  • SaaS Activity Detections
  • AI Agent Behavioral Detections
  • Network Anomaly Detections
The Detection Engineering Process

From Threat Research to Production Detection

Detection engineering at LogicBounce is a continuous, research-driven process — not a periodic project. New detections are developed, validated against real attack data, and shipped to Nexus customers every week.

01

Threat Research Input

Every detection starts with intelligence from the Threat Defense Unit, Identity Threat Research team, and AI & Agent Security Research team. We don’t build detections speculatively — we build them against documented, real-world attack techniques that have been observed in the wild or discovered through original research. This ensures every detection has validated attacker behavior behind it, not theoretical assumptions.

02

Telemetry Mapping & Data Modeling

Once a technique is documented, we map the observable artifacts it leaves across telemetry sources — identity logs, cloud audit events, endpoint telemetry, SaaS activity logs, network flows, and AI agent behavioral data. We identify which data sources are required, which combinations of signals create high-confidence indicators, and how to normalize data from heterogeneous sources into a consistent detection model.

03

Behavioral Logic Development

Detection logic is written as behavioral rules rather than signature-based patterns — detecting the actions, sequences, and anomalies that characterize attacker behavior rather than specific IOCs that change with every campaign. Detections are developed using graph analytics, time-series analysis, statistical baselining, and contextual enrichment from Atlas’s Security Graph to reduce false positives.

04

Adversary Emulation Validation

Every detection is validated against real attack simulation before shipping. We run adversary emulation exercises using the actual TTP being detected — confirming the detection fires correctly, measuring detection latency, testing edge cases, and tuning thresholds to hit our false positive target of less than 2%. Detections that fail validation go back to development, not into production.

05

Continuous Maintenance & Drift Management

Adversaries adapt. A detection that works today may degrade as attackers modify their techniques to evade it. Our detection maintenance program continuously monitors production detection performance, tracks adversary technique evolution, and updates detection logic when drift is detected — ensuring Nexus customers always have current, high-fidelity coverage.

Detection Domains

What We Detect Across the Enterprise

Our detection library spans every major enterprise attack surface — with particular depth in the areas where modern attackers concentrate their efforts.

Identity & Credential

AiTM phishing, credential stuffing, token theft and replay, MFA bypass techniques, OAuth abuse, privilege escalation via identity systems, account takeover behavioral patterns, and impossible travel anomalies.

Cloud Infrastructure

IAM privilege escalation, unusual resource provisioning, cloud storage exfiltration patterns, cross-account role assumption abuse, serverless function exploitation, and anomalous API call sequences.

Endpoint & Process

Living-off-the-land binary abuse, process injection techniques, credential dumping from memory, lateral movement tool execution, defense evasion patterns, and ransomware pre-deployment behavioral indicators.

SaaS & Application

Abnormal data export patterns, OAuth application abuse, sharing permission escalation, mass download events, cross-SaaS lateral movement indicators, and third-party integration anomalies.

AI Agent Behavior

Prompt injection execution indicators, anomalous tool invocation patterns, agent behavioral drift, MCP permission abuse, unexpected API call sequences from agent processes, and agent-to-agent trust exploitation.

Network & Traffic

Command-and-control communication patterns, DNS tunneling, beaconing behavior, lateral movement via network protocols, data exfiltration volume anomalies, and unusual outbound connection patterns.

Sample Detections

From the Nexus Detection Library

A sample of recently shipped detections. The full library of 500+ production detections is available to Nexus platform customers via the detection catalogue.

DE-IDENT-0247

OAuth Refresh Token Persistence After Password Reset

Detects cases where OAuth refresh tokens issued to third-party applications remain valid and active following a user password reset event — a common persistence mechanism used by attackers after initial credential compromise.

High Severity Identity Persistence OAuth
DE-CLOUD-0183

AWS IAM Role Chaining for Cross-Account Privilege Escalation

Behavioral detection identifying multi-hop IAM role assumption sequences that traverse organizational account boundaries in patterns consistent with privilege escalation rather than legitimate cross-account operations.

High Severity Cloud Privilege Escalation AWS
DE-AGENT-0041

AI Agent Anomalous Tool Invocation Sequence

Detects AI agent tool call sequences that deviate significantly from established behavioral baselines — flagging patterns consistent with prompt injection execution where an agent performs atypical actions outside its normal operational scope.

High Severity AI Agent Prompt Injection Behavioral
DE-IDENT-0318

Entra ID Conditional Access Policy Bypass via Legacy Authentication

Identifies authentication attempts against Entra ID-protected resources using legacy protocols (Basic Auth, NTLM) that bypass modern conditional access policies — commonly used to circumvent MFA requirements on accounts with legacy protocol access enabled.

High Severity Identity MFA Bypass Entra ID
DE-SAAS-0094

Mass Download Followed by Sharing Permission Escalation

Correlates large-volume file download events with subsequent sharing permission escalation within SaaS platforms — a behavioral pattern observed in both data exfiltration pre-departure scenarios and active insider threat cases.

Medium Severity SaaS Exfiltration Insider Threat
DE-ENDPT-0156

LSASS Memory Access via Indirect Syscall Pattern

Detects credential dumping attempts targeting LSASS using indirect syscall techniques designed to evade userland API hooking — a technique increasingly used by modern ransomware groups and nation-state actors to bypass EDR credential theft protections.

High Severity Endpoint Credential Dumping EDR Evasion
Research Areas

Detection Engineering Connects All Research

Detection Engineering translates output from every research area — Autonomous Defense Research and Threat Intelligence — into production detections that ship to every Nexus customer.

Detection Coverage That Actually Works.

Our Detection Engineering team can assess your current detection coverage, identify gaps against the threats targeting your industry, and show you exactly how Nexus fills them.