Vulnerability Management: Fast Runtime Event-Driven Inventory (Early Access)
Note
The following update is available only for Early Access (EA) customers. This enhancement will be released for General Availability (GA) at a later date.
Documentation is now available for new body parameters and response properties added to the Tenable Vulnerability Management API to support fast runtime event-driven inventory (FREDI) scanning. Runtime inventory scanning is a scanning method that Tenable Vulnerability Management can perform through linked Tenable Nessus Agents. It provides continuous monitoring and reporting of software inventory changes on your hosts.
Note
Runtime inventory scanning is currently only available for agents installed on Linux hosts. Agents that have NIAP mode enforced cannot perform runtime inventory scanning.
FREDI scanning referred to as "runtime inventory scanning" in the Tenable Vulnerability Management user interface. For more information about runtime inventory scanning, see Runtime Inventory Scanning and Agent Profiles in the Tenable Vulnerability Management Early Access User Guide.
The new body parameters and response properties enable customers to configure FREDI scanning when creating or updating an agent profile and view FREDI scanning configurations when retrieving the details of agent profiles, agent groups, and agents.
The endpoint updates are described in the following table:
| Endpoint | Name | Update |
|---|---|---|
| POST /sensors/profiles/{sensor_type} | Create profile | Added the new com.tenable.fredi_module body parameter.The com.tenable.fredi_module body parameter enables users to add and configure FREDI scanning when creating an agent profile. |
| GET /sensors/profiles/{sensor_type} | List profiles | Added the com.tenable.fredi_module and com.tenable.tua_comm_module modules objects to the response body.com.tenable.fredi_module indicates whether FREDI scanning is enabled for the profile and what the baseline scan frequency is. com.tenable.tua_comm_module is a module that is automatically enabled on the backend, and ensures that FREDI scanning data is properly sent from agents to Tenable Vulnerability Management. |
| GET /sensors/profiles/{sensor_type}/{profile_uuid} | Get profile details | Added the com.tenable.fredi_module and com.tenable.tua_comm_module modules objects to the response body.com.tenable.fredi_module indicates whether FREDI scanning is enabled for the profile and what the baseline scan frequency is. com.tenable.tua_comm_module is a module that is automatically enabled on the backend, and ensures that FREDI scanning data is properly sent from agents to Tenable Vulnerability Management. |
| PUT /sensors/profiles/{sensor_type}/{profile_uuid} | Update profile | Added the new com.tenable.fredi_module body parameter.The com.tenable.fredi_module body parameter enables users to add and configure FREDI scanning when creating an agent profile. |
| GET /scanners/null/agents | List agents | Added the boolean fredi_status response property. fredi_status indicates whether FREDI scanning is enabled for the agent. |
| GET /scanners/null/agent-groups/{agent_group_id}/agents | List agents by group | Added the boolean fredi_status response property. fredi_status indicates whether FREDI scanning is enabled for the agent. |
| GET /scanners/null/agents/{agent_id} | Get agent details | Added the boolean fredi_status response property. fredi_status indicates whether FREDI scanning is enabled for the agent. |
| GET /scanners/null/agent-groups/{group_id} | Get agent group details | Added the boolean fredi_status response property. fredi_status indicates whether FREDI scanning is enabled for the agent. |