In aFortiSIEM deployment,device discoveryis handled by theSupervisor, even when aCollectoris present.

● TheSupervisor initiates active scansusing protocols such asSNMP, WMI, SSH, and API queriesto discover devices in the network.

●Collectors do not perform discovery; they primarilycollect and forward logsfrom designated devices to the Supervisor.

●Workers handle event processing, not discovery.

InFortiSIEM,SQLite databasesused forbaseliningare stored in the/opt/phoenix/cachedirectory. This location is used fortemporary storage and caching of profile datathat is essential for anomaly detection and trend analysis.

●Baselininginvolves analyzing historical data to determine expected behavior patterns.

●SQLite databasesstore aggregated statistics, which are referenced during rule evaluations.

● Thecache directoryallows quick access to these values without querying the main database repeatedly.

FortiSIEM enforces a device limit based on licensing and system-wide constraintsto ensure proper resource allocation and performance management.

The device limit is determined by the purchased license.

● FortiSIEM licensing includes limits on thenumber of devicesthat can be monitored.

● Thelicense type(e.g.,Enterprise vs. Service Provider) defines themaximum number of devicessupported.

For Service Provider editions, the device limit applies system-wide and is shared across all customers.

● In anMSSP (Managed Security Service Provider) setup, the totaldevice limit applies across all customers, rather than being allocated individually.

● This allowsflexible resource allocationbased on customer needs.