Vendors typically ship software applications with security settings disabled by default to ensure a wide range of interoperability with other applications and devices. A security administrator…

The correct answer is C. Application hardening. Application hardening involves configuring software to reduce its attack surface by enabling security settings, disabling unnecessary features, removing default accounts, and applying security benchmarks (e.g., CIS benchmarks) before deployment. Because vendors ship with…

Security operations

Question

Vendors typically ship software applications with security settings disabled by default to ensure a wide range of interoperability with other applications and devices. A security administrator should perform which of the following before deploying new software?

Options

AApplication white listing
BNetwork penetration testing
CApplication hardening
DInput fuzzing testing

How the community answered

(48 responses)

A
2% (1)
B
6% (3)
C
90% (43)
D
2% (1)

Explanation

Application hardening involves configuring software to reduce its attack surface by enabling security settings, disabling unnecessary features, removing default accounts, and applying security benchmarks (e.g., CIS benchmarks) before deployment. Because vendors ship with permissive defaults for compatibility, hardening is the essential pre-deployment step. Application whitelisting (A) controls which apps can run - it doesn't configure the app itself. Network penetration testing (B) is a post-deployment assessment, not a pre-deployment configuration step. Input fuzzing (D) is a testing technique to find bugs, not a deployment preparation activity.

Topics

#application hardening#secure configuration#default settings#deployment security

Community Discussion

No community discussion yet for this question.

Full SY0-301 Practice