Netskope conditional access
Posture-gated Netskope access for devices and AI agents
Turn live endpoint and AI-agent evidence into a Netskope device tag. Your Device Classification and Real-time Policy keep the enforcement decision.
Identity
Verified Developer
SSO-bound, trusted user
Device
Secure Endpoint
Patches, EDR, encryption
Policy
EDAMAME Trust
Continuous access decisions
Platform
Netskope
Device tag + policy
Labels compliant devices
Customer Real-time Policy enforces
No rip-and-replace
For teams already using Netskope that need host and AI-agent truth behind network policy.
The Risk
A trusted Netskope session can still start on an unsafe host.
Netskope sees network and cloud activity. The host sees which AI agent spawned a shell, read credentials, opened a file, or diverged from its declared task. Access needs both planes.
Authenticated devices can still be unsafe (posture drift).
Malware turns an enrolled laptop into an attacker workstation.
AI agents can touch credentials and local files before traffic reaches the proxy.
Network controls see traffic, not the agent's declared task or parent process.
SECURITY GAP
The Device Trust Gap
A device can remain authenticated while its posture drifts, its AI agent escapes a harness, or a package starts harvesting credentials.
Without host evidence, a customer policy cannot distinguish expected agent work from local attack behavior.
The Solution
EDAMAME labels. Netskope enforces.
EDAMAME evaluates endpoint posture, AI Agent Posture, intent divergence, and attack-pattern findings. It applies or removes a device tag; your Netskope policy decides access.
Identity: Netskope device identity mapped to the EDAMAME endpoint.
Posture: OS protections plus observed, fenced, in-policy AI agents.
Runtime: intent divergence and unreviewed attack-pattern findings.
When policy passes, EDAMAME ensures the tag is present. When it fails, EDAMAME removes it. Netskope makes the allow/block decision.
ARCHITECTURE
A Netskope Device Classification matches the EDAMAME tag. Your customer-authored Real-time Policy references that classification and owns enforcement.
Host evidence → EDAMAME policy → device tag → Netskope policy
No proxy replacement. No new enforcement plane. Host truth feeds the Netskope stack you already operate.
Core Capabilities
One policy chain, from host evidence to Netskope enforcement.
EDAMAME contributes endpoint and AI-agent truth. Netskope continues to own network, cloud, DLP, AI Gateway, Device Classification, and Real-time Policy.
Netskope device identity
Map the Netskope Client identity to the EDAMAME endpoint. Install the helper or run elevated posture where the provisioning store requires it.
Endpoint + AI Agent Posture
Combine encryption, patching, protections, agent observation, harness coverage, intent divergence, and attack-pattern findings in one EDAMAME policy.
Native Netskope enforcement
EDAMAME applies or removes an existing device tag. Your Device Classification and Real-time Policy decide what that tag permits.
Per-device updates
Only the device whose compliance changed is touched. Recovery re-applies the tag automatically; there is no tenant-wide reconciliation sweep.
Safe tag coexistence
Read-modify-write preserves tags from Netskope Cloud Exchange and other tools. If all five tag slots are occupied, EDAMAME fails visibly.
Explicit failure behavior
Allow-on-tag denies untagged devices. An expired token freezes existing tag state, and a device without usable Netskope identity is skipped.
Comparison
This is a complementary plane: Netskope sees and controls network/cloud activity; EDAMAME supplies host and AI-agent evidence that the network cannot observe.
Add host truth to network policy.
Alternative
Netskope without host evidence
The network sees destination, category, volume, and policy context — not which local agent read a credential or spawned a shell.
With EDAMAME
EDAMAME adds process lineage, file access, agent identity, declared intent, and attack-pattern findings.
Alternative
Inline network controls
SSE, DLP, and AI Gateway controls inspect transactions that cross their plane. Local process behavior can happen before or outside that path.
With EDAMAME
A host finding becomes a tag change, then the customer's Netskope policy enforces the result.
Alternative
Static device state
Encryption and patch posture do not show whether an AI agent escaped a harness, diverged from intent, or touched credentials.
With EDAMAME
EDAMAME policy combines device posture with live AI-agent evidence before maintaining the Netskope tag.
Rollout
Five-minute rollout.
Connect your Netskope tenant, choose an existing device tag, define the EDAMAME policy, then wire that tag into your own Device Classification and Real-time Policy.
Step 01
Install EDAMAME
Install EDAMAME Security or run EDAMAME Posture elevated so Netskope device identity and host evidence are available.
Step 02
Connect Netskope
Enter the tenant hostname, REST API v2 token, and an existing device-tag name. Hub validates all three together.
Step 03
Define EDAMAME policy
Combine endpoint posture, AI Agent Posture, intent divergence, and unreviewed attack-pattern findings.
Step 04
Wire Netskope policy
Match the tag in Device Classification and reference it from a customer-authored allow-on-tag Real-time Policy.
Step 05
Monitor tag state
Watch token expiry, skipped device identities, and the five-tag limit. The trigger is per-device, not a fleet reconciliation service.
Threat Scenarios
Three ways host truth changes access.
The same EDAMAME policy can react to credential access, intent divergence, and supply-chain attack patterns by changing the device tag Netskope consumes.
Scenario
Credential-harvest finding
Without EDAMAME
A local process reads several credential stores and starts an outbound session.
With EDAMAME
The finding fails policy → EDAMAME removes the tag → the customer's Netskope policy denies.
Scenario
Intent divergence
Without EDAMAME
An AI agent's observed process, file, and network behavior no longer matches its declared task.
With EDAMAME
The divergence fails policy → tag removed → Device Classification stops matching.
Scenario
Supply-chain attack pattern
Without EDAMAME
A package post-install process reaches credential stores, writes outside the workspace, or opens suspicious egress.
With EDAMAME
An unreviewed critical finding fails policy; tag recovery is automatic only after the endpoint returns to compliance.
Trust & Impact
Extend Netskope policy to the host and AI-agent boundary.
Keep the network and cloud controls you already operate. Add independent endpoint evidence and a precise device tag for your policy to consume.
Use host evidence that network telemetry cannot reconstruct.
Map agent findings to OWASP GenAI and the runtime-observable MITRE ATLAS subset.
Keep Device Classification and Real-time Policy ownership in the customer's Netskope tenant.
A VPN gives you network isolation, but it doesn’t tell you whether the device itself should be trusted. With EDAMAME all endpoints accessing the code and secrets are truly within the perimeter.
CTO
Global Telecom Company
