A junior developer is informed about the impact of new malware on an Advanced RISC Machine (ARM) CPU, and the code must be fixed accordingly. Based on the debug, the malware is able to insert itself in another process memory location.
Which of the following technologies can the developer enable on the ARM architecture to prevent this type of malware?
The technology that the developer can enable on the ARM architecture to prevent malware from executing in another process's memory location is Execute Never. Execute Never (XN) is a security feature specifically designed for ARM CPUs. It prevents code from executing in marked memory regions, making it an appropriate solution for mitigating the risk of malware inserting itself into another process's memory location.
keyword "ARM" - EN - Execute never = ARM CPU's NX - No -Execute = AMD CPU's XD - Execute Disble = Intel CPU's XI - Execute Inhibit = MIPS Architecture https://en.wikipedia.org/wiki/NX_bit Source: Verifying each answer against Chat GPT, my experience, other test banks, a written book, and weighing in the discussion from all users to create a 100% accurate guide for myself before I take the exam. (It isn't easy because of the time needed, but it is doing my diligence) XD
EVP = AMD CPU
The ARM architecture refers to the feature, which was introduced in ARMv6, as XN (execute never)
XN is a security feature that is designed to prevent certain types of malware from executing in memory. When XN is enabled, the CPU will not execute code that is stored in memory regions that have been marked as XN. This can help to prevent malware from inserting itself into another process's memory location and executing from there. No-execute (NX) is a similar security feature that is used to prevent certain types of malware from executing in memory. NX works by marking certain memory regions as non-executable, so that the CPU will not execute code from those regions.
"Finally, for CPUs built on the ARM architecture, the feature is called XN (execute never). -CompTIA CASP+ Study Guide, Exam CAS=004, Fourth Edition, Chapter 2, Pg 47
Answer is A
I know Wiki is no the most reliable source but it seems that XN (execute never) is a future developed for ARM cpu that comes from NX (no-execute). Since question mentions two key works new technology and only ARM i will say XN or execute never is the answer. Virtual Memory encryption can be an option but it says in the ARM manual that for memory security to turn off Memory Management Unit (MMU) which is what controls the VMe
Sorry answer is A.
No-execute (NX) is for 64 bit AMD CPUs and execute never (XN) is for 64 bit Intel CPUs. Source: Mark Birch--ComTIA CASP+ CAS-004 Certification Guide, p357
ARM RISC processors chips support the XN bit. For more information see the following URL: https://tinyurl.com/nxdep
NX/XN Bit Use NX (No-eXecute) is a bit in CPUs that greatly enhances the security of that CPU as it operates. The purpose of NX is to segregate memory areas used for processor instruction and data storage. This feature used to be found only on CPUs with the Harvard architecture (with storage and instruction memory areas separated)
The ARM architecture refers to the feature, which was introduced in ARMv6, as XN (execute never). The term NX bit itself is sometimes used to describe similar technologies in other processors. The question asks in regards to ARM architecture. no-execute for ARM is execute never. Ref: https://crucialexams.com/study/questions/220-901/what-is-the-purpose-of-the-no-execute-nx-bit-technology-used-in-intel/
This question is asking for a resolution for the malware to not "insert itself in another process memory location." wouldn't you want to segmentate the memory then with virtual memory ?
Answer is A. Think of a buffer flow attack as BiteSize provided https://en.wikipedia.org/wiki/NX_bit - explains the situation in here
For ARMv8-A, VMSAv8-64 block and page descriptors, and VMSAv8-32 long-descriptor block and page descriptors, for stage 1 translations have "execute never" bits for both privileged and unprivileged modes, and block and page descriptors for stage 2 translations have a single "execute never" bit
Virtual memory protection is a technology that isolates different processes from each other and prevents them from accessing each other's memory space. By enabling virtual memory protection, the junior developer can ensure that the malware is unable to insert itself into another process memory location, thereby protecting the system from the malware.
No-execute
The documentation provided indicates that no-execute should be the answer. https://developer.arm.com/documentation/102433/0100/Stack-smashing-and-execution-permissions. A
D correct in this context