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 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Canonical Ubuntu 22.04 LTS Security Technical Implementation Guide

V-260557

CAT II (Medium)

Ubuntu 22.04 LTS must be configured to use AppArmor.

Rule ID

SV-260557r958804_rule

STIG

Canonical Ubuntu 22.04 LTS Security Technical Implementation Guide

Version

V2R8

CCIs

CCI-001764CCI-001774CCI-002235

Discussion

Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system level. Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline. Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). Satisfies: SRG-OS-000368-GPOS-00154, SRG-OS-000370-GPOS-00155, SRG-OS-000324-GPOS-00125

Check Content

Verify Ubuntu 22.04 LTS AppArmor is active by using the following commands:  
 
     $ systemctl is-enabled apparmor.service 
     enabled  
 
     $ systemctl is-active apparmor.service 
     active   
 
If "apparmor.service" is not enabled and active, this is a finding. 
 
Check if AppArmor profiles are loaded and enforced by using the following command: 
 
     $ sudo apparmor_status | grep -i profile 
     32 profiles are loaded. 
     32 profiles are in enforce mode. 
     0 profiles are in complain mode. 
     0 profiles are in kill mode. 
     0 profiles are in unconfined mode. 
     2 processes have profiles defined. 
     0 processes are unconfined but have a profile defined. 
 
If no profiles are loaded and enforced, this is a finding.

Fix Text

Enable and start "apparmor.service" by using the following command: 
  
     $ sudo systemctl enable apparmor.service --now 
  
Note: AppArmor must have properly configured profiles for applications and home directories. All configurations will be based on the actual system setup and organization and normally are on a per role basis. See the AppArmor documentation for more information on configuring profiles.