asset-monitor

To monitor attack surface risks, you can integrate MCP-based discovery to enumerate subdomains and detect vulnerabilities across target domains. This workflow automatically saves asset attributes and generates baseline risk reports for SOC audits.

Yes, you can automate asset discovery and port scanning using MCP-based integration. The workflow supports automated target creation, continuous monitoring, and risk tiering to identify high-risk assets without manual intervention.

You can track asset changes and generate baseline reports by running continuous asset monitoring. The system automatically creates change histories and applies risk tiering to validate JSON asset attributes for SOC audits.

Yes, you need duckdb and jq installed because they are required dependencies for processing and validating JSON asset attributes. These tools handle data validation and risk tiering within the monitoring workflow.

The best way to centralize attack surface management is to use a unified workflow that integrates MCP-based asset discovery, change alerts, and vulnerability checks. This approach maintains visible, manageable assets with automatic risk tiering.

Discovered assets may not show risk levels if data validation fails during the vulnerability checks. Ensure your JSON asset attributes are correctly parsed and that the risk tiering process runs successfully after asset discovery.