Skip to content

Commit caadf39

Browse files
venkateshjayagopalkakabisht
authored andcommitted
Update 07.filerules.md
Updated file access introduction
1 parent 46a3d55 commit caadf39

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

versioned_docs/version-5.4/05.policy/07.filerules/07.filerules.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,6 @@ slug: /policy/filerules
77

88
### Policy: File Access Rules
99

10-
There are two types of Process/File protections in NeuVector. One is Zero-drift, where allowed process and file activity are automatically determined based on the container image, and second is a behavioral learning based. Each can be customized (rules added manually) if desired.
11-
1210
NeuVector has built-in detection of suspicious file system activity. Sensitive files in containers normally do not change at run-time. By modifying the content of the sensitive files, an attacker can gain unauthorized privileges, such as in the Dirty-Cow linux kernel attack, or damage the system’s integrity, for example by manipulating the /etc/hosts file. Most containers don't run in read-only mode. Any suspicious activity in containers, hosts, or the NeuVector Enforcer container itself will be detected and logged into Notifications -> Security Events.
1311

1412
#### Basic File Protections

0 commit comments

Comments
 (0)