Skip to main content
This page describes how to keep Axottle secure: install updates, respond to vulnerabilities, and collect diagnostics for support without revealing secrets.
For whom: administrator, SRE, security specialist.

Security updates

Keep the dashboard and agents up-to-date is the primary way to close known vulnerabilities.
1

Make a backup.

Before updating the panel, create and verify a backup. see Backup copies of.
2

Update the panel.

The panel detects new versions; the upgrade is performed by the installer with an automatic rollback in case of unsuccessful health check. see Updates.
3

Update agents.

Update agents nodes; the task is considered successful only after confirmation of the target version. See Agent Updates.
4

Check your health.

After updating, make sure the health dashboard is green.See Health.

Disclosure of Vulnerabilities

If you find a vulnerability in Axottle, please report it privately – do not publish details before the patch is released.
Contact for responsible disclosure – support for Axottle in Telegram: @axosupport.In the appeal, specify: the affected version, the description of the problem, the playback steps and the potential impact. N Enclose real secrets, tokens or keys - use impersonal examples.

Collection of diagnostics for support

To escalate, attach a support bundle. It collects diagnostics and automatically masks the secrets of before saving, and the identifiers result in a hashed appearance. Launch it. sudo axottleOpen up. DoctorSelect the period of journals and collect Collect support bundleThe archive can be viewed, stored locally, or sent in support. Service and Axottle Doctor and CLI.
Despite the automatic masking, before sending the archive outside the organization, briefly review it and make sure that it does not contain sensitive data from your environment.

Hygiene of secrets

  • Regularly withdraw unused tokens and credentials. see Secrets.
  • If you suspect a compromise of the master key, plan its change as a serviced operation (after the shift, you will need to re-enter the credentials of the providers).
  • Keep a record of which integration tokens and access providers are issued to whom.

Verification

The dashboard of health is green; the diagnostic archive is formed with disguised secrets; there is a working contact to disclose vulnerabilities.

Responding to a security incident

If you suspect a compromise, act according to the general response scenario: assess the scale, collect diagnostics, change secrets if necessary and complete active sessions. See Response to incidents and Escalation.