- play_arrow Bandwidth for Managed Hosts
- play_arrow Installing a JSA Console or Managed Host
- play_arrow Virtual Appliance Installations for JSA and Log Manager
- play_arrow Migrating to Docker Enterprise Edition with FIPS
- play_arrow Updating Cryptographic Modules for FIPS
- play_arrow Installations from the Recovery Partition
- play_arrow Reinstalling JSA from Media
- play_arrow JSA Software only Installations
- play_arrow Setting up a JSA Silent Installation
- play_arrow Configuring Bonded Management Interfaces
- play_arrow Network Settings Management
- play_arrow Troubleshooting Problems
Standard Linux Users
The tables describe the standard Linux user accounts that are created on the JSA Console and on other JSA product components like JSA All-in-One (JSA console), JSA Risk Manager, JSA Network Insights, App Host, and all other managed hosts).
The following tables show standard Linux user accounts for Red Hat and JSA.
User Account | Log in to the Login Shell | Purpose |
|---|---|---|
root (password required) | Yes | Red Hat user |
bin | No | Linux Standard Base |
daemon | No | Linux Standard Base |
adm | No | Linux Standard Base |
lp | No | Linux Standard Base |
sync | No | Linux Standard Base |
shutdown | No | Linux Standard Base |
halt | No | Linux Standard Base |
No | Linux Standard Base | |
operator | No | Linux Standard Base |
games | No | Red Hat user |
ftp | No | Red Hat user |
nobody | No | Linux Standard Base |
systemd-network | No | Red Hat user |
dbus | No | Red Hat user |
polkitd | No | Red Hat user |
sshd | No | Red Hat user |
rpc | No | Red Hat user |
rpcuser | No | Red Hat user |
nfsnobody | No | Red Hat user |
abrt | No | Red Hat user |
ntp | No | Red Hat user |
tcpdump | No | Red Hat user |
tss | No | Red Hat user |
saslauth | No | Red Hat user |
sssd | No | Red Hat user |
User Account | Log in to the Login Shell | Purpose |
|---|---|---|
ziptie | No | Ziptie service used by JSA Risk Manager |
vis | No | JSA VIS service used by JSA to process scan results |
customactionuser | No | JSA Custom Actions used to isolate custom actions into a chroot jail |
mks | No | MKS JSA component for handling secrets |
qradar | No | General user for JSA |
qvmuser | No | Used by JSA Vulnerability Manager |
postgres | No (account locked) | PostgreSQL database used by JSA |
tlsdated | No | Tlsdate legacy time sync tool that was previously used by JSA |
traefik | No | Traefik service proxies Docker Containers for JSA App Framework |
gluster | No | GlusterFS used by JSA HA on event collectors |
openvpn | No | OpenVPN optional VPN tool installed by JSA |
chrony | No | Chronyd service time sync tool used by JSA |
apache | No | Apache Web Server used by JSA |
postfix | No | Mail Service used by JSA to send email |
| nscd | No | Name Service Cache Daemon used by JSA |
| qniconfiguser | No | Deployment configuration used by JSA Network Insights |
| nslcd | No | Used by JSA for LDAP functionality |
| fusionvm | No | Used by JSA Vulnerability Manager |
