Pricing

Find vulnerabilities that could be exploited and items that do not meet security requirements. Review severity, exploitability, patch availability and the evidence behind each assessment, alongside affected assets, to identify what to address first.

Compare devices discovered on the network with managed assets to find equipment that may be missed in assessments. Review open ports, services and vulnerability information together to identify assets that need management or investigation.

Review fixed versions for vulnerabilities and remediation steps for security requirements to prepare patches and configuration changes. After remediation, reassess security requirements and retain assessment results and action history for future reviews and reporting.

Check which assets have been assessed and where information collection has stopped or assessments are delayed. Distinguish assets with no findings from assets that have not yet been checked to identify where further assessment is needed.

Connect external exposure, vulnerabilities and access relationships between systems to analyze potential attack paths to critical systems. Distinguish observed connections from connections based on configuration or inference, and review the evidence behind each path.

Analyze potential impact on critical assets, external exposure and exploitation evidence together to prioritize paths for response. Identify assets shared by multiple attack paths to show where access restrictions or permission changes should be considered first.

Detect activity during operation, including privilege escalation, suspicious communications and configuration changes. Review the activity, related assets and detection evidence together to identify what needs investigation.

Review externally accessible assets alongside internal connections. Check whether unmanaged devices are part of a path and where vulnerabilities overlap with opportunities for privilege escalation.

Review service communications and dependencies to understand how a problem could affect other systems. Track new and terminated connections and configuration changes over time to understand how risk paths have changed.

Compare information collected from your environment with known threat indicators. Identify matches and provide reference information for investigating related assets and activity.

In supported environments, confirm the target and execution conditions before terminating processes, blocking traffic or isolating assets. Distinguish whether a requested command was delivered, whether it actually executed and, if it failed, why.

Manage request, review and approval procedures based on action targets and evidence of potential impact. Record who approved each action and on what grounds, and recheck target status and execution conditions after approval.

Distinguish a successful command record from the actual effect of an action. Use supported observations to check whether blocking or isolation remains in effect, whether a process terminated and whether the same behavior recurs, informing follow-up response.

Review failure causes and target status to prepare a retry and request release of blocking or isolation when needed. Link the history of initial actions and follow-up commands to trace the response process.

Compare error rates and response latency before and after an action to assess its impact on services. Review the security effect and service recovery status separately to determine whether additional response is needed.

Bundle point-in-time assessment results and assessment, action and exception records with supporting evidence. Check material versions and integrity, and manage submission records and requests for additional information for audit review.