Skip to content

Commit 6b50ea6

Browse files
authored
Merge pull request #410 from percona/ps-9512
PS-9512 Add information to AppArmor in 8.4
2 parents ac72384 + 1277ba6 commit 6b50ea6

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/disable-apparmor.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,16 +4,16 @@
44

55
Using AppArmor might seem like an extra step, but if you disable it, your server could face security risks.
66

7-
Do not disable AppArmor in production environments. Instead, use AppArmor's security features and configure it to fit your needs.
8-
9-
## Risks
7+
Do not disable AppArmor in production environments. This action can have the following risks:
108

119
| Risk | Description |
1210
|---|---|
1311
| Increased Attack Surface | Disabling AppArmor removes security restrictions, potentially allowing unauthorized access to Percona Server for MySQL's files and functionalities. This creates an attractive target for attackers seeking to exploit vulnerabilities or gain control of your database. |
1412
| Unforeseen Security Holes | AppArmor can help mitigate even unknown vulnerabilities by restricting unexpected behaviors. Disabling it leaves your system more susceptible to these hidden security holes. |
1513
| Accidental Misconfigurations | Even with good intentions, manual configuration of access controls can be error-prone. AppArmor provides a pre-defined security layer, reducing the risk of human error in managing permissions. |
1614

15+
Instead, use AppArmor's security features and configure it to fit your needs.
16+
1717
## Disable procedure
1818

1919
If AppArmor must be disabled, run the following commands:

0 commit comments

Comments
 (0)