SI-Map: application mapping
Describe your applications, their criticality, their owners and the servers they depend on; spot orphan assets and undocumented flows.
SI-Map keeps the business map of your IT: which applications, for which business lines, on which servers, and how critical they are. It has no agent; it relies on what the other modules already know.
Describing an application
In Applications, click New Application. Fill in the name, code, business domain, owner, environment and criticality, rated 1 to 4 on three criteria: Availability, Integrity, Confidentiality. Add continuity details (RPO and RTO in hours, Backup Site), zones, the data processed, and tick Exposed to Internet if that is the case.
Link asset attaches a server, a device, a monitor or a database instance, with its role and whether it is a Critical component.
Reference data
| Screen | Content |
|---|---|
| Domains | Core business, business, support… |
| Zones | Internal LAN, DMZ, partner, cloud…, with a trust level from 1 to 4 |
| Data Types | Category, sensitivity, GDPR legal basis, retention period (declarative only) |
What SI-Map flags
The dashboard shows Attention Points: applications without an owner, unlinked assets, applications exposed to the Internet.
Orphan Assets lists the assets known to other modules that are not linked to any application. You can Link to an application or create a new application from there.
Flow Detection suggests flows observed over 7 days between application assets, with a confidence score. You Accept or Reject them one by one, or use Accept all (high confidence) for those scoring 80 or more. For this screen to fill up, assets must be linked, equipped with the NetFlow module, and have exchanged at least 1 MB over 7 days.
The SI cartography view shows the whole picture: servers, workstations, network, topology. The application graph shows one application and its dependencies.
Source: · FirstSI Docs · updated 2026-10-10