Evidence for the auditor, the insurer and the ISP
Three people will ask you to prove something this quarter. In most IT departments the answer to all three is a screenshot marathon the week before the deadline.
Key points
- Every configuration change is in an audit log with the administrator's identity; three permission tiers say who could do what.
- SPF, DMARC, DNSSEC, TLS and certificate checks run continuously and alert on regression — the lines on the cyber-insurance form.
- Loss, jitter and latency are measured between probes across the real path, and interface use is shown as a percent of link speed per hour, so the ISP call comes with numbers.
- Scorecard, SLA, capacity and inventory reports are bounded by measured coverage and, in the paid editions, delivered on a schedule.
On this page: The auditor The insurance form The ISP and the app team The budget
The auditor wants to know who changed what, and when. The cyber-insurance form wants to know whether DMARC is enforced and whether any certificate is about to lapse. The ISP, or the application team, wants to know why you think it was their fault. SysPeep was designed so that the evidence is a by-product of doing the job: the log is already written, the checks are already running, and the report already has the date on it.
For the auditor
Every configuration change is written to an audit log with the administrator's identity. Three administrator tiers — junior, mid and senior, enforced at every endpoint that changes anything — mean the helpdesk can acknowledge and investigate without being able to reconfigure, delete or clear, and the audit log shows who did what.
The inventory report answers the first question every audit asks — what is on the network — from the same discovery data the monitor already maintains, which is a great deal fewer spreadsheets than the alternative. The second question, where the device passwords are, has an answer too: encrypted with AES-256-GCM under a key kept in the installation's own data folder, never in the programs or the configuration file, so a copied configuration or a database backup does not hand them over.
On the record
- Audit log with identity, every change
- Junior, mid and senior tiers
- Local or Active Directory / LDAP sign-in
- Scoped, revocable API tokens
- TLS console, mutual TLS to probes, session limits
- Device credentials encrypted under a key that never leaves your server
- Inventory report from live discovery
- A Readings table: proof of every value recorded
For the insurance questionnaire
The protections that quietly break during a migration are checked continuously, and a regression raises an alert instead of waiting for the renewal form to discover it.
- SPF, DMARC and DNSSEC are verified continuously, with an alert when any of them regresses.
- TLS certificate, protocol and cipher sensors catch expiring certificates, legacy TLS versions and weak ciphers, and show the expiry as a date rather than a count.
- Certificate Transparency watching alerts when a certificate is issued for your domain that you did not expect — a phishing precursor caught from the public logs.
- HTTP security-header checks test a web service the way an auditor would.
- Backup checks turn a silently failing backup into a ticket with lead time.
- Windows event log subscriptions route the events that matter to an alert, with the rest kept in the timeline for later.
What this is not: a security product, and SysPeep does not claim to be one. It is the monitoring tool noticing the things the questionnaire asks about, before the questionnaire does.
For the ISP and the application team
A QoS packet train between two probes measures loss, jitter and latency across the real path, so a WAN or VoIP complaint comes with numbers attached. The Flows page (NetFlow, IPFIX and sFlow, included in every edition) names the top talkers and conversations, shows each interface's use as a percent of its link speed hour by hour, the QoS mix, the traffic pattern by hour of the week and the countries the busiest senders are placed in — and every total says how much of the window the collector observed. Interface error rates come from SNMP, and the honest graphs show missed polls as red bands rather than smoothing them into a reassuring line. When a sensor is checked from more than one place, the alert says which place raised it, which settles "is it the server or the WAN" before the call starts.
Because down means unreachable and a slow or failed service is degraded, the record also shows the case where the network was fine and the application was not — which is the half of the argument the network team usually cannot prove.
For the people who sign the budget
An executive scorecard, and health, SLA, alerts, capacity, inventory and traffic reports, export as CSV in every edition and, in the paid editions, also export as PDF and arrive by scheduled email without anyone building them. Every availability figure is bounded by the coverage that was actually measured, so the number on the scorecard can be defended in the meeting where it is read. Capacity reports project dates rather than percentages, which is the form a budget request needs to take.
| Who asks | What they ask | What you hand them |
|---|---|---|
| The auditor | Who changed the alert threshold on the payment server, and when? | The audit log entry, with the administrator's identity |
| The auditor | What is on the network? | The inventory report, from live discovery |
| The insurer | Is DMARC enforced? Are certificates current? | The hygiene sensors' history and the certificate expiry dates |
| The ISP | Prove the circuit was degraded | Loss, jitter and latency from the probe-to-probe packet train, with timestamps |
| The ISP | Was the circuit simply saturated? | The uplink's use as a percent of its speed, per hour, with the hours the collector did not observe hatched rather than drawn as quiet |
| The application team | Prove it was not the network | Reachability intact, interface errors flat, service degraded — on one timeline, with the exact readings a click away |
| The CFO | What was our availability, and what will we run out of first? | The scorecard with measured coverage labelled, and the capacity report with projected dates |
The monitoring tool, in other words, also makes the case for the monitoring tool. That is not the reason to buy one, but it is a pleasant property to discover at renewal time.
Start the audit trail before the audit
Install the free edition, add the domain hygiene and certificate checks for your own domains, and let the audit log run from day one. The 30-day trial unlocks scheduled report delivery and PDF export.
Download Free TrialNext: The first tab you open