Security Overview
Purpose: Identity hygiene and administrative accountability across the platform and the directory behind it. Who has accounts, which are stale or over-privileged, which devices are still on default credentials, what changed, and who changed it.
What this section is, and what it is not
This is audit and hygiene reporting, not security monitoring. There is no threat detection, no vulnerability scanning, no intrusion alerting, and no SIEM function. What it does provide is the evidence a compliance review normally asks for and nobody can produce quickly: a current account inventory with privilege and password state, a record of platform access, and a history of configuration change.
The reports in this section
| Report | What it answers |
|---|---|
| Security Dashboard | Who has accounts, which are stale or privileged, which directory conditions need attention, and which devices are still on default credentials |
| Administrative Report | Who logged in, who acknowledged which alert, and what changed at device and user level |
Global controls
- Collection Date. Both screens read a point-in-time snapshot. Account state and default-credential findings are as of the selected collection, not live.
- Change Client. Scopes both screens to one client environment, which matters for service providers reviewing several estates from one login.
- Custom Email. A
Generateaction producing an emailable version of the current view.
When to use it
- Run a quarterly or annual user access review
- Evidence administrative activity for an audit or compliance request
- Find devices still authenticating with vendor default credentials
- Establish whether a reporting anomaly was a collection failure or a real change
Common actions
Use the Security Dashboard to find the problems, meaning stale accounts, non-expiring passwords, unnecessary privilege, and default credentials. Use the Administrative Report to evidence that somebody acted on them. The dashboard is the review; the report is the paper trail.
Tips
Both screens display real account names, email addresses, device identifiers, and hostnames from the connected environment. Treat screenshots and exports from this section as sensitive, and redact before circulating outside the team that already has access.