Assess which device or application risks zDefend turns into which responses in each workflow. Alert visibility and actual restriction of a critical operation are different outcomes.
Evaluation approach
Examine how the application receives device, network and environmental risk information and which responses it can apply. Verify current capabilities per platform.
Application example
Use a sample application to test how a high-risk environment event feeds session and transaction policies.
Limits and considerations
Risk detection does not establish that all code is obfuscated or every API protected.
From an event to a business decision
A runtime-risk product's value depends on how results reach the application as well as what it detects. Define event timing, freshness and response options. The same risk may require different policies for different operations.
Include ordinary network changes, supported devices and lifecycle transitions in the trial. If risks must reach the server, assess transfer failures too. SDK event generation and stopping a sensitive operation are separate acceptance criteria.
Checks and decisions
- Review event types
- Test response paths
- Document data transfers
Evaluate which business outcome the product's event changes.
Sources
The primary references above provide the technical basis. Example workflows and evaluation suggestions are this publication’s explanations, not independent test results for a particular product.