nerdexam
CompTIA

CAS-003 · Question #42

A company is developing requirements for a customized OS build that will be used in an embedded environment. The company procured hardware that is capable of reducing the likelihood of successful…

The correct answer is B. NX/XN bit. The hardware described - capable of reducing the likelihood of successful buffer overruns - refers to processors that implement the NX (No-Execute) or XN (Execute Never) bit. This hardware feature marks specific memory regions (such as the stack and heap) as non-executable, so…

Technical Integration of Enterprise Security

Question

A company is developing requirements for a customized OS build that will be used in an embedded environment. The company procured hardware that is capable of reducing the likelihood of successful buffer overruns while executables are processing. Which of the following capabilities must be included for the OS to take advantage of this critical hardware-based countermeasure?

Options

  • AApplication whitelisting
  • BNX/XN bit
  • CASLR
  • DTrustZone
  • ESCP

How the community answered

(36 responses)
  • A
    17% (6)
  • B
    72% (26)
  • C
    3% (1)
  • D
    6% (2)
  • E
    3% (1)

Explanation

The hardware described - capable of reducing the likelihood of successful buffer overruns - refers to processors that implement the NX (No-Execute) or XN (Execute Never) bit. This hardware feature marks specific memory regions (such as the stack and heap) as non-executable, so that even if an attacker successfully writes shellcode into a buffer, the processor will refuse to execute it. For the OS to leverage this hardware capability, it must explicitly support and enable the NX/XN bit. Application whitelisting (A) is a software control that restricts which programs can run, unrelated to hardware buffer overflow protection. ASLR (C) randomizes memory addresses in software and is complementary but not the hardware mechanism described. TrustZone (D) is an ARM security extension for isolated execution environments. SCP (E) is a file transfer protocol and entirely unrelated.

Topics

#NX/XN bit#buffer overflow prevention#embedded systems#hardware security

Community Discussion

No community discussion yet for this question.

Full CAS-003 Practice