Română
Português
EspañolGetting started with Security & Compliance
Security & Compliance is a section of the client portal. It watches your servers, your Cloud Office and your cloud accounts, and turns what it sees into alerts, hardening scores, vulnerability lists and evidence for twelve compliance frameworks.
Where to find it
Sign in to the client portal and choose Security & Compliance in the header. The same sign-in opens Cloud Office and your servers, so there is no second account to manage.
Owners and administrators of your organisation see the security screens. Billing contacts and members do not. Owners and administrators can also add or remove servers and connect cloud accounts.
The screens
| Screen | What it answers |
|---|---|
| Overview | How are we doing right now? Alerts by severity, failed sign-ins, attacking addresses, open vulnerabilities, your NIS2 score and the live alert stream. |
| Threat map | Where do attacks come from? Countries and source addresses over the last day, replayable on a timeline. |
| Topology | What does our estate look like? Zones, machines, what each exposes to the internet, its hardening score, and which machine is under attack. |
| Fleet | Which servers are monitored, and are they all reporting? Add servers with one command. |
| Cloud resources | Which cloud accounts and SaaS services are connected, and are their audit logs arriving? |
| Events | What exactly happened? Every event, searchable and filterable by source, host, severity, framework and MITRE ATT&CK tactic. |
| Compliance | Where do we stand against NIS2, DORA, ISO/IEC 27001 and nine more frameworks, control by control? |
| Vulnerabilities | Which packages have known vulnerabilities, and how hardened is each machine against its CIS benchmark? |
| Reports | What do we hand to management, the auditor or the regulator? |
| Audit trail | Who in our organisation did what in the portal. |
The time range in the header (1 hour, 24 hours, 7 days, 30 days) applies to every screen. The search box in the header searches events: an address, a user, a host or a rule.
Where the data comes from
Servers
A small sensor on each server sends security events, its package inventory and its hardening checks. See Adding servers.
Cloud Office
Sign-ins, two-factor, device passwords, sharing, administration and everyday activity are reported automatically. Message bodies and file contents never are.
Organisational records
Policies, backups, suppliers and training cannot be seen in logs. They show as "No data" until you record them, never as passed.
What the screens never pretend
- A number that cannot be read shows —, never 0: a zero would read as "nothing happened".
- A machine that stops reporting is shown as silent, never as healthy.
- A period before monitoring began shows —, not a perfect score.
- A feature that is drawn but not built yet (signed reports, an on-demand re-scan, recording a significance decision) is shown disabled and says not available yet.
Related
Still stuck?
Write to us with what you tried and what you saw. A person answers, in writing, on business days.