Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Eccouncil Exam 312-38 Topic 4 Question 97 Discussion

Actual exam question for Eccouncil's 312-38 exam
Question #: 97
Topic #: 4
[All 312-38 Questions]

John is a senior network security administrator working at a multinational company. He wants to block specific syscalls from being used by container binaries. Which Linux kernel feature restricts actions

within the container?

Show Suggested Answer Hide Answer
Suggested Answer: A

The topology that the network designer will propose is known as a screened subnet. This topology involves the use of two or more firewalls to create a network segment referred to as a demilitarized zone (DMZ). The DMZ acts as a buffer zone between the public internet and the internal network. It contains the public-facing servers, such as the web portal mentioned, which is isolated from the internal network for added security. The screened subnet topology typically includes a firewall at the network's edge connected to the internet, another firewall separating the DMZ from the internal network, and the DMZ itself. This setup allows for strict control of traffic between the internet, the DMZ, and the internal network, providing an additional layer of security.


Contribute your Thoughts:

Anthony
16 days ago
I heard Seccomp is like a force field for your container. It's the Chuck Norris of Linux kernel features!
upvoted 0 times
...
Lavera
18 days ago
Seccomp all the way! It's like a bouncer for your container, keeping the troublemakers out. John's going to have a secure container party with this one.
upvoted 0 times
...
Shantay
1 months ago
Userns? Nah, that's for user namespaces, not restricting syscalls. I'm going with LSMs - they can do some pretty advanced security stuff, right?
upvoted 0 times
...
Kristine
1 months ago
Hmm, Cgroups are great for resource management, but I don't think they're the right tool for blocking specific syscalls. I'd go with Seccomp on this one.
upvoted 0 times
Carin
18 hours ago
LSMs and Userns are not typically used for blocking syscalls like Seccomp.
upvoted 0 times
...
Lajuana
3 days ago
Seccomp filters system calls at the kernel level, making it a good choice.
upvoted 0 times
...
Carli
4 days ago
Cgroups are more for resource management, not syscall blocking.
upvoted 0 times
...
Herminia
8 days ago
I agree, Seccomp is the way to go for blocking specific syscalls.
upvoted 0 times
...
...
Nicolette
2 months ago
Seccomp sounds like the way to go here. I remember reading about how it can restrict system calls in a container. Seems like the best choice for John's needs.
upvoted 0 times
Rosalind
16 days ago
I agree, Seccomp is a powerful feature for restricting actions within containers.
upvoted 0 times
...
Clay
1 months ago
Seccomp is definitely the way to go for blocking specific syscalls in containers.
upvoted 0 times
...
...
Mona
2 months ago
I'm not sure, but I think Cgroups could also be a possible answer.
upvoted 0 times
...
Francoise
2 months ago
I agree with Olene, Seccomp restricts actions within the container.
upvoted 0 times
...
Olene
2 months ago
I think the answer is C) Seccomp.
upvoted 0 times
...

Save Cancel