STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 4 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Axonius Federal Systems Ax-OS Security Technical Implementation Guide

V-276009

CAT I (High)

Ax-OS must use multifactor authentication for network access to the customer account.

Rule ID

SV-276009r1122677_rule

STIG

Axonius Federal Systems Ax-OS Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-000765

Discussion

Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. Multifactor authentication requires using two or more factors to achieve authentication. Factors include: (i) something a user knows (e.g., password/PIN); (ii) something a user has (e.g., cryptographic identification device, token); or (iii) something a user is (e.g., biometric). A privileged account is defined as an information system account with authorizations of a privileged user. Network access is defined as access to an information system by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, or the internet).

Check Content

Have the system administrator (SA) demonstrate accessing the Axonius Toolbox (accessed via Secure Shell [SSH]).

Verify the SA is using a password-protected SSH key to log in to the system. 

If the SA is not using a password-protected SSH key to log in to the system, this is a finding.

Fix Text

From the Axonius Toolbox (accessed via SSH) Main Actions Menu, select the following options:

System Actions >> Update customer account SSH key

Follow the on-screen prompts to configure key-based authentication.