Which SELinux Feature Meets Email Server Baseline Requirements?
Short answer
A Deploy SELinux to gain its access vector cache for performance while enforcing mandatory access control over the email server baseline.
Question
• Unauthorized reading and modification of data and programs
• Bypassing application security mechanisms
• Privilege escalation
• Interference with other processes
Which of the following is the most appropriate for the engineer to deploy?
Key Takeaways
The phrase 'access vector cache' is a SELinux-specific term, and the four listed threats map directly to the protections SELinux MAC provides in a system baseline.
This question asks which technology delivers an access vector cache, mandatory access control, and protections against data tampering, application security bypass, privilege escalation, and process interference for email servers. The answer is SELinux, whose kernel MAC implementation uses an Access Vector Cache (AVC) to speed policy decisions while enforcing confinement.
Common mistake: Learners often pick privileged access management because it addresses privilege escalation, but PAM tools do not provide an access vector cache or MAC enforcement for processes.
Expert Analysis
Why the Answer Is Correct
SELinux is a Linux kernel security module implementing Mandatory Access Control (MAC) with policy rules covering all subjects and objects. Its Access Vector Cache (AVC) stores recently computed access decisions so the kernel avoids re-evaluating policy on every request, which directly matches the stated performance goal. SELinux documentation explicitly lists protection against unauthorized reading and modification of data and programs, bypassing application security mechanisms, privilege escalation, and interference with other processes — the exact four bullets in the question. Deploying SELinux in enforcing mode as part of a server system baseline therefore satisfies every stated requirement at once.
Why the Other Options Are Wrong
Privileged access management (B) governs administrative credential vaulting and session recording, but it provides no access vector cache and does not confine ordinary processes or block data-file tampering by compromised services. Self-encrypting disks (C) protect data at rest through hardware encryption and say nothing about MAC, process isolation, or application security bypass. A network intrusion prevention system (D) inspects traffic at the network layer; it cannot enforce in-kernel access decisions between local subjects and objects, so it addresses none of the four listed protections in the local baseline sense.
Community Comment Notes
A single comment from jamestkd argues for A, explaining that SELinux "explicitly utilizes an Access Vector Cache (AVC) to improve performance by caching access decisions" and covers the four listed protections. That reasoning matches the official SELinux architecture description, and no dissenting comment was posted, so the community position aligns with the technical analysis.
Official Reference
https://selinuxproject.org/page/SELinux101
This link opens the official vendor documentation in a new tab.
Exam Strategy
On CAS-005 scenario items, treat unique vendor-specific nouns like 'access vector cache' as identifiers — they point unambiguously to one technology and let you eliminate the rest without deep debate.
Frequently Asked Questions
Why does SELinux use an access vector cache?
Why is privileged access management not the right choice here?
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
jamestkd 👍 1 Answered ASecurity-Enhanced Linux (SELinux) is a security module built into the Linux kernel that provides mechanisms supporting access control security policies, including Mandatory Access Control (MAC). It explicitly utilizes an Access Vector Cache (AVC) to improve performance by caching access decisions, and it protects against unauthorized reading/modification, application security bypasses, privilege escalation, and process interference through strict isolation and domain transitions.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All CAS-005 Questions
Access 135 questions with complete answers and detailed explanations.
View Full CAS-005 Practice Test →