Skip to main content
Axottle captures the actions of administrators and the system in the audit log and allows you to bring nodes to a given security profile with subsequent verification of compliance.
For whom: Administrator, SRE, Security/Compliance Specialist Required rights: Administrator of the panel.

Audit log

An audit log is a secure activity log, and each record contains:

Viewing

  • limit - default 50, maximum 500; offset - offset; q - line filter by action / resource.
  • In the panel there is a separate page Audit-log with the same filter and auto-update.

What’s fixed

Among other things: the life cycle of security checks, assigning and removing security profiles, backup operations, health actions and policies, node life cycle, changes in notification settings, egress policy actions, Axosun Assistant events.
There is no automatic cleaning of the audit log - records are stored indefinitely. If you need a storage policy, manage the database yourself (archiving / deleting old records on the database side).

Journal of Node Operations

Separate from the audit log, each node has a Operations Journal (Node Events: Registration, Task Life Cycle, Security Events) that is contractually free of secrets. The difference between the log and the audit log is Journal and audit.

Node security profiles

The security profile is a named set of hardening modules applied to the node. Groups of modules: SSH amplification, behavioral IDS/IPS, firewall, mail relay blocking and UDP protection, malware/proxyware protection, anti-torrent policy, anomaly detectors, scanning control, and logging control (including short storage, aggregate counters and hashed identifiers). Three profiles are built in: You can create your own profile. The profile is assigned to the node through its settings; the appointment is recorded in the audit.

Conformity assessment

Conformity assessment checks the actual state of the node with the assigned profile - according to three security services of the node (behavioral IDS/IPS, brute force protection, firewall) Verification only reads the state, saves the verdict on the node and writes events to the journal. Possible states (for each service and in general): compliant, partial (works but configuration differs), not_compliant, installed_unmanaged, installed_not_running, not_installed, unknown (no data is offline/failure agent), not_required (profile does not require service).
A node without a designated profile is rated as not_required.

Status of detectors

A single method returns one of the statuses for each detector: active, no_telemetry, unsupported, disabled, failed — with the cause, the required and obtained capabilities and the time of the latest data. The detector without telemetry is no_telemetry, not the green tick.

One-time node check

You can run a one-time security check of the node: the node line immediately shows “executed”, then goes to ok/failed/unknown according to the agent’s report, the result with warnings is displayed in the panel, and the fact of the check is written into the audit.

Preliminary security check

Before the node or domain is put into operation, you can run the pre-check tool from the command line, which checks DNS, TLS, public panel availability, indexing headers, dangerous ports and operator-configured block lists. Results: passed, warning (not fatal), failed (fails report), skipped (no data source; reasons are indicated).

Verification

Administrator actions appear in the audit log; node conformity assessment returns verdict with verification time; nodes without telemetry are shown as “no data” rather than as relevant.

Rollback

  • The purpose of the profile is reversible: assign the previous profile or remove the profile (both actions are recorded in the audit).
  • Compliance assessment and security checks are just reading, there is nothing to roll back.