A security engineer is hardening existing solutions to reduce application vulnerabilities. Which of the following solutions should the engineer implement FIRST? (Choose two.)
It's A & D. Hardening existing applications will derive no benefits whatsoever, from "Sandboxing."
However, aside enabling Auto-Updates of their applications, they might also want to safeguard 3rd-Party Solutions (CRM, ERP, Web-based solutions, etc) by ensuring they are regularly patched/updated.
Every other options would be "chasing shadows."
Ok so i wasnt the only one thinking this way by how the question is worded. Im not understanding what sandboxing has to do with hardening the vulnerabilities right now when it could be as easy as updating and auto updating. idk maybe im wrong though
B. HTTP headers: Configuring secure HTTP headers can help protect against various web application vulnerabilities, such as cross-site scripting (XSS), clickjacking, and certain types of information leakage.
C. Secure cookies: Ensuring that cookies are secure and properly configured helps prevent various attacks like session hijacking and cookie tampering.
auto-update does not reduce application vulnerabilities, per se. They can actually increase vulnerabilities in many cases. Also, updates can be for new features and, in the enterprise environment, auto-updating can destabilize many systems (making the less secure), why you should test thoroughly before doing so. Sandboxing doesn't actually fix vulnerabilities in apps nor does it harden them, it merely mitigates them (the apps, themselves, are still vulnerable).
A. Auto-update
B. HTTP headers
Auto-update ensures that software remains up-to-date with the latest security patches, addressing known vulnerabilities promptly. Configuring HTTP headers properly enhances web application security by mitigating common web-based attacks. These proactive measures can significantly reduce the attack surface and strengthen the overall security posture of the applications.
Going a bit against the grain and saying A&D. Since it asks what should be done first. Sandboxing or HTTP stuff is nice in certain cases, but if your software isn't patched then that's the number one way it will become vulnerable. Whether it's first party or third party.
AF- Auto-update ensures that all software has the latest security patches, minimizing security risks. Sandboxing is a security mechanism for separating running programs, often used to execute untested codes, preventing software vulnerabilities from spreading across the system
Auto-update is not hardening, so it's out. B & C are application hardening methods (for web apps including intranet apps - which is extremely common today)
D is not hardening, per se - (one bad update can weaken a system - ask Microsoft)
E & G are not application hardening, either (they protect data at rest, not really the application)
F is a hardening technique for an entire system - not really just an application
who told you auto-update is not a hardening technique? I would advise you to read more before posting, unless you are really sure, as this is causing so much confusion.. https://checklist.gg/templates/software-hardening-checklist
sandboxing is used for containment/isolation. for example, a web browser can be run in a sandbox to mitigate attacks through the browser (i.e. malvertising, drive-by downloads, browser zero-days, etc). IOS employ sandboxing for all its running apps. sandboxing can be used for testing but it's not the sole purpose
As usual, we are stuck in uncertainty due to the poor wording of the question and are forced to make an inference. Personally, I like BC over AD.
I think generally, CompTIA teaches us to be wary of auto-update policies in enterprise environments, and instead preaches the use of patch management suites. I think this can be attributed to auto-updates having the potential to cause compatibility, performance, and availability issues. I'm using similar reasoning to be wary of third-party updates -- patch management can help vet/schedule those updates so they are implemented seamlessly.
Therefore, I'm more comfortable making the inference of web application security, resulting in my decision to select BC.
So with this question, all other options are things that are good security measures.
A) A good Security Practice but not hardening.
D) Same as A.
E) a protective measure
F) limits an applications “reach” so it doesn’t access other parts of the system.
G) same as e.
I could be wrong, but just based on the way the question was worded, and it is worded horribly, the only two that I could think would apply in this situation is B and C.
I picked B & C because they are specific to actual application hardening, not mitigating attack surface (sandboxing is not app hardening, but network hardening & risk mitigation)
A. Auto-update
D. Third-party updates
I've done some research on the top system hardening actions to take first.
Multiple sources are saying that these are the most important things.
-- Auto OS updates
-- Keep third party software on the system patched.
Since the question says "existing solutions" it makes me think this is in reference to third party software which could also be accessed via a web application. Based on the "existing solutions" I would use A.) Auto-update.
F.) Sandboxing - I would consider this something I would do "FIRST" to mitigate application related vulnerabilities; especially if there is a third-party application with unpatchable vulnerabilities.
The question seems to lack any meaningful context. What type of application is it? What is the environment?
Some folks here assume a web app, but I would not be so sure.
A. Auto-update: Implementing auto-updates ensures that your applications are always running the most recent and secure versions
C. Secure cookies: Many web applications use cookies to maintain session state and store user-specific information. If these cookies are compromised, it could lead to session hijacking or unauthorized access.
This section is not available anymore. Please use the main Exam Page.SY0-601 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
NetTech
Highly Voted 1 year, 10 months agoYomzie
1 year, 4 months agojkalfo
11 months, 3 weeks agoApplebeesWaiter1122
Highly Voted 1 year, 11 months agosujon_london
1 year, 9 months agoBD69
1 year, 2 months agoccnaexam28
1 year, 11 months agoKelvinYau
Most Recent 7 months, 2 weeks agoSUZII
1 year, 1 month agorussian
1 year, 1 month agops1hacker
1 year, 2 months ago_deleteme_
1 year, 2 months agoBD69
1 year, 2 months agoglenndexter
1 year, 1 month agofrancuza
1 year, 3 months agoxihjr
1 year, 2 months agoBD69
1 year, 2 months agoslapster
1 year, 4 months agoGrahamtb
1 year, 4 months agoBD69
1 year, 2 months agoganymede
1 year, 4 months agoAceVander
1 year, 6 months agofryderyk
1 year, 7 months agoCisco103
1 year, 9 months ago32d799a
1 year, 9 months agoaddcomptia
1 year, 9 months ago