Join our Newsletter — 33% off our NHI Course
Home› Guides› IBM AIX Security Hardening Guide: RBAC, Trusted Execution…
Guide Endpoint Security

IBM AIX Security Hardening Guide: RBAC, Trusted Execution and AIXPert

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 8 November 2026 13 min read
On this page

IBM AIX still runs core banking, ERP, insurance and database workloads, and many AIX estates are secured with root passwords shared by a small team and configuration that has not changed in a decade. AIX has strong native security features, including enhanced role-based access control, Trusted Execution for binary integrity, the AIX Security Expert (AIXPert) hardening tool and a kernel audit subsystem, but they are rarely switched on because the platform is managed separately from the Linux and Windows estates. This guide explains how identity and privilege work on AIX, how to replace shared root with roles and named accounts, which settings form a hardening baseline, and how to log and measure the result. It is written for AIX administrators, Unix security engineers and auditors. Commands are given for orientation; confirm syntax against the IBM documentation for your AIX level before use.

This is an independent guide from NHI Mgmt Group, based on IBM's public documentation as of November 2026. It is not sponsored or reviewed by IBM. Product features change, so confirm settings against IBM's current documentation.

Key takeaways

  • Replace shared root with enhanced RBAC. Enhanced RBAC (on by default since AIX 6.1) grants fine-grained aix.* authorizations through roles, so administrators can run privileged commands without the root password.
  • Use Trusted Execution to detect tampering. The Trusted Signature Database holds SHA256 hashes of trusted files, checked at install, on demand and at load time, and can refuse to run files that fail.
  • Apply AIXPert as a baseline engine, not a one-off script. It applies high, medium or low hardening levels, records the applied policy in XML and can check the system against it later.
  • Measure against the CIS IBM AIX 7 benchmark. CIS publishes a current IBM AIX 7 benchmark (version 1.2.0 at the time of writing), which gives auditors a recognised reference.
  • Bring AIX into the same identity and logging programme. Directory-backed accounts, vaulted break-glass root, centrally forwarded audit and syslog records, and the same service account governance as other platforms.

How identity and access work in AIX

AIX users and groups are defined in /etc/passwd and /etc/group, with security attributes in files under /etc/security: /etc/security/passwd holds password hashes, /etc/security/user holds per-user and default login and password policy, and /etc/security/login.cfg holds system-wide authentication settings, including the password hashing algorithm, where SHA-2 based options replace legacy crypt. Accounts can be local or held in LDAP (IBM Security Verify Directory, Microsoft Active Directory and other directories through the AIX LDAP client), selected per user with the SYSTEM and registry attributes.

Attribute (/etc/security/user)ControlsTypical hardened value
loginretriesFailed logins before the account locks3 to 5
maxage / minageMaximum and minimum password age in weeksPer policy; minage 1 to stop immediate reuse
maxexpiredWeeks after expiry the user can still change an expired passwordLow value, such as 1
minlen, minalpha, minotherPassword length and compositionminlen 14 or per corporate policy
histsizePasswords remembered to prevent reusePer policy, often 5 or more
rloginWhether the account may log in remotelyfalse for root and service accounts
loginWhether the account may log in locallyfalse for non-interactive service accounts
su / sugroupsWhether others can su to the account, and which groups mayRoot: su limited to an admin group

The default stanza in /etc/security/user applies to every account without its own value, so baseline it first and override sparingly. lsuser -a and chuser query and change these attributes.

Admin roles and privileged access

Enhanced RBAC

The AIX V6 Advanced Security Features Redbook describes enhanced RBAC as the default mode from AIX 6.1, controlled by the enhanced_RBAC system setting (changing it needs a reboot). Its building blocks are:

  • Authorizations: named rights in a dotted hierarchy beginning with aix, for example aix.system.boot.info. Custom hierarchies must use another top-level name and can be up to nine levels deep. List the system set with lsauth -f -a description ALL_SYS.
  • Roles: containers of authorizations assigned to users (mkrole, chuser roles=). A user activates a role with swrole, which requires re-authentication and starts a new role session.
  • Privileges: process attributes that let a command bypass a specific kernel restriction, granted per command through the privileged command database rather than by running as root.
  • Security databases: authorization, role, privileged command, privileged device and privileged file databases. Changes take effect when loaded into the kernel security tables with setkst.
  • Domain RBAC: added in AIX 7.1, it restricts which objects (devices, file systems, network interfaces) a role can act on, which helps separate duties between teams sharing a host.

Root, su and sudo

ApproachAccountabilityGranularityWhen to use
Shared root passwordNone beyond su logsAll or nothingNever for routine work; break-glass only, vaulted
su restricted by sugroupsLogs which user switchedAll or nothing once switchedTransitional step
sudo (from the AIX Toolbox)Per command, loggedCommand levelMixed Unix estates with a common sudoers policy
Enhanced RBAC rolesPer role session, auditableAuthorization and privilege levelNative, kernel-enforced least privilege
PAM tool with session recordingPer session, recordedBrokered access to root or rolesRegulated workloads such as core banking
  • Remove direct root login: set rlogin=false for root and in sshd_config set PermitRootLogin no; administrators log in as themselves and elevate. See the OpenSSH Server Hardening Guide.
  • Vault root: store the root password in a privileged access vault, rotate it after every use and alert on any root login. See the Unix and Linux Privileged Access Guide.
  • Separate security administration: keep the roles that manage users, roles and audit configuration away from day-to-day system administrators, so one person cannot both act and erase the evidence.
  • Management planes are privileged too: the Hardware Management Console and Virtual I/O Server control every LPAR on a frame; treat their accounts as Tier 0 for the AIX estate.

Integrations, API tokens and service accounts

AIX hosts carry many long-lived non-human identities: database instance owners, application server users, batch schedulers, file transfer accounts, backup agents and monitoring users, often with SSH keys copied between LPARs and passwords that never expire. These are the accounts attackers reuse (MITRE ATT&CK T1078.003 Local Accounts) and move with (T1021.004 SSH).

  • Make service accounts non-interactive: set login=false and rlogin=false where the account only runs processes, and give them roles or sudo rules for the specific commands they need, not root.
  • Restrict SSH keys: prefix automation keys in authorized_keys with restrict, from= and command=, keep key files root-owned and inventory them. See the SSH Key Management Guide.
  • Remove credentials from scripts: batch scripts and job definitions frequently embed database and FTP passwords; move them to a secrets manager or the scheduler's credential store. See the Secrets Management Guide.
  • Directory integration: LDAP-backed users simplify joiner and leaver processing, but bind credentials on each host are themselves service account secrets; protect the LDAP client configuration and use TLS. See the LDAP Security Deep Dive Guide.
  • Govern like other platforms: include AIX service accounts in the same owner, review and rotation process as Linux ones. See the Linux Service Accounts and Keytab Management Guide, much of which applies directly.

Logging and detection

AIX audit subsystem

AIX includes a kernel audit subsystem configured in /etc/security/audit/config, with event definitions in /etc/security/audit/events and file objects to watch in /etc/security/audit/objects. It is started with audit start and can write in bin mode (to files, processed with auditpr) or stream mode (to a pipeline that can feed syslog or an agent). AIX 7.1 added role-based auditing and auditing of Trusted Execution events. AIXPert's audit policy enables auditing if it is not running.

What to captureSourceWhy
Logins, failed logins, su and role switchesAudit events for user login and su, /etc/security/failedlogin, syslog authAccount misuse and brute force
Changes to users, roles and authorizationsAudit events for user and role administration; object watches on /etc/security filesPrivilege creation and persistence
Privileged command useRole-based auditingAccountability for root-equivalent actions
Trusted Execution failuresTE audit events and trustchk reportsModified binaries or rootkits (T1543, T1505)
SSH authentication with key fingerprintssshd at LogLevel VERBOSE via syslogWhich key or account logged in (T1021.004)
Changes to audit configurationObject watch on /etc/security/auditDefence impairment
  • Forward off host: configure /etc/syslog.conf (or a log agent) to send auth and audit streams to the SIEM; local logs on a compromised LPAR cannot be trusted. See the Linux Logging and auditd for Defenders Guide for the equivalent Linux design.
  • Size the trail: auditing every system call on a busy database LPAR is costly; audit administrative events and sensitive objects, and test the overhead before production.

Metrics

  • Root logins: number of direct root logins per month (target zero outside break-glass).
  • Benchmark score: percentage of CIS IBM AIX 7 recommendations passing per LPAR, by environment.
  • TE coverage: percentage of LPARs with Trusted Execution enabled and a clean check report.
  • Service account hygiene: percentage of service accounts with login=false, an owner and a rotation date.
  • Audit health: percentage of LPARs with audit running and events arriving in the SIEM within the last 24 hours.

Hardening baseline

AIXPert and File Permission Manager

AIXPert (AIX Security Expert) must be run as root and applies a set of rules at one of several levels: high, medium and low, plus a SOX-COBIT configuration. It writes the applied rules to an XML policy file that can be used later to check the system for drift and can be distributed to other systems or held on an LDAP server for central policy. The Redbook warns that undo is recursive but some settings cannot be undone, so take a system backup (mksysb) and test on a non-production LPAR first. The File Permission Manager, fpm -l high, fpm -l med or fpm -l default, removes setuid and setgid bits from commands that do not need them (medium removes both, low only setgid). See the Linux Privilege Escalation Techniques Guide for why setuid programs matter.

LevelSuitsTrade-off
HighInternet-facing or highly regulated LPARsDisables many network services and legacy protocols; most likely to break applications
MediumMost production application and database LPARsBalanced; still test with the application team
LowIsolated development and testLimited protection
DefaultRolling back to AIX standard settingsNot a hardened state

Trusted Execution

  • Trusted Signature Database: a stanza file of SHA256 hashes and attributes for trusted files, populated at installation for AIX filesets; add your own binaries with trustchk -a.
  • Checks: verify on demand or from cron (offline mode), and enable runtime checking so the loader compares hashes when trusted files load and refuses those that do not match.
  • Policies: CHKEXEC, CHKSCRIPTS and CHKKERNEXT extend checking to executables, scripts and kernel extensions; a stricter policy allows only programs in the database to run, and once the database is locked down, a reboot is needed to unlock it.
  • Rollout: run offline checks first, review and fix mismatches from in-house software, then enable runtime checking in report mode before any stop-on-failure policy.

Other baseline items

  • Network services: disable telnet, rlogin, rsh, rexec, tftp and unauthenticated FTP in /etc/inetd.conf, and remove unused NFS exports; use OpenSSH and SFTP.
  • Password hashing: move the password hashing algorithm in /etc/security/login.cfg to a SHA-2 option (check the exact attribute and values for your AIX level) and force password changes so existing hashes are regenerated.
  • Encrypted File System: where data-at-rest encryption is needed on JFS2, EFS (enabled with efsenable, managed with efskeymgr and efsmgr) encrypts per file with AES keys protected by users' RSA keys.
  • Patching: keep AIX on supported technology levels and service packs, and apply security fixes through a tested schedule; legacy LPARs on unsupported levels should be isolated.

Phased rollout

  1. Assess: scan representative LPARs against the CIS IBM AIX 7 benchmark and record shared accounts, root logins, setuid files and service accounts.
  2. Back up: take a mksysb image and save /etc/security before any change.
  3. Identity first: create named admin accounts, roles or sudo rules, restrict root login and vault the root password.
  4. Pilot AIXPert medium on a test LPAR with the application team, then non-production, then production in waves.
  5. Enable audit and forwarding, then Trusted Execution in check mode.
  6. Roll back: use AIXPert undo where supported, restore saved /etc/security files, or restore from mksysb for settings that cannot be undone.

Framework mapping

FrameworkReferenceAIX control
NIST SP 800-53 Rev. 5AC-6, AC-6(5), IA-2, IA-5(1), AU-2, AU-9, SI-7, SI-7(1), CM-6RBAC, vaulted root, named accounts, password policy, audit subsystem, Trusted Execution, AIXPert baseline
NIST CSF 2.0PR.AA-05, PR.PS-01, PR.PS-04Reviewed privileges, configuration management, logging
CISCIS IBM AIX 7 Benchmark; CIS Controls v8.1 4.1, 5.4, 8.2Configuration baseline, admin privileges, audit logs
MITRE ATT&CKT1078.003, T1021.004, T1548, T1548.003, T1543Local account misuse, SSH movement, elevation abuse, persistence

Common misconfigurations

  • Shared root as the operating model: several administrators know the root password, root can log in over SSH and nobody can tell who did what.
  • Enhanced RBAC enabled but unused: roles are never assigned, so everyone still works as root. Equally, roles built by copying all authorizations recreate root under another name.
  • AIXPert applied once and forgotten: the policy is never rechecked, drift accumulates, and nobody knows which rules were applied or why an application broke.
  • Service accounts with interactive logins and old keys: database and batch users accept SSH logins from anywhere, with keys copied across every LPAR and passwords set to never expire.
  • Legacy protocols left on: telnet, rsh and FTP remain enabled for one old integration, exposing credentials in clear text.
  • Audit off or local only: the audit subsystem is not started, or its trail stays on the host where an intruder with root can remove it.

Practitioner checklist

  • Benchmark every LPAR against the CIS IBM AIX 7 benchmark and track the score per environment.
  • Set the default stanza in /etc/security/user to your password and lockout policy and move the password hashing algorithm to a SHA-2 option.
  • Disable direct root login, vault and rotate the root password, and give administrators named accounts with roles or sudo.
  • Design enhanced RBAC roles for real duties, separating security administration from system administration.
  • Apply AIXPert at medium or high after testing, keep the applied policy and check for drift regularly.
  • Run fpm to strip unneeded setuid and setgid bits and review what remains.
  • Enable Trusted Execution checks, starting with offline reports, then runtime checking.
  • Start the audit subsystem, watch /etc/security and forward audit and auth logs to the SIEM.
  • Make service accounts non-interactive, restrict their SSH keys and remove passwords from scripts.
  • Treat HMC and VIOS administration as Tier 0 for the AIX estate.

Standards and references

Related NHI Mgmt Group resources: Unix and Linux Privileged Access Guide · CIS Benchmarks Guide · OpenSSH Server Hardening Guide · IBM i Security Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 8 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.