Legit 712-50 Exam Download

 Explanation:

Version/source control ensures that all code changes are tracked, and previously remediated flaws do not reappear.

Without robust source control practices, outdated or insecure code can inadvertently be reintroduced.

 Why Other Options Are Less Likely:

A. Ineffective configuration management controls: This pertains to system configurations, not application code.

B. Lack of change management controls: Change management addresses overall process but does not specifically prevent code reintroduction.

D. High turnover in the development department: While turnover may contribute to the issue, the root cause is inadequate version/source control.

 EC-Council CISO Reference:

Effective development practices, including version control, are emphasized as critical to maintaining application security.

 Firewall Ruleset Review:

Reviewing and maintaining firewall rules is a technical control because it directly involves managing and configuring security technologies.

 Purpose:

Regular reviews ensure firewalls are updated and properly configured to prevent unauthorized access.

 Supporting Reference:

CCISO defines technical controls as safeguards implemented through technology, such as firewalls and their associated configurations.

 Evaluating Awareness Effectiveness

Controlled spear phishing campaigns test the real-world application of security awareness training by simulating attacks. They measure users' susceptibility to phishing and provide insights into areas needing improvement.

 Comparison of Options

B. Password changes: A routine IT practice, not an indicator of awareness program effectiveness.

C. Baselining computer systems: Focuses on system performance, not user awareness.

D. Scanning for viruses: Targets system vulnerabilities, not user behavior.

 EC-Council References

EC-Council promotes simulation exercises to measure awareness program effectiveness and ensure preparedness against social engineering.

A system dynamically blocking offending IP addresses is an example of a corrective security control because it takes action to fix or neutralize an issue after detecting a potential threat.

Classification of Security Controls:

Preventive Controls: Aim to stop incidents before they occur (e.g., firewalls, access controls).

Detective Controls: Identify and alert on security incidents (e.g., IDS, monitoring tools).

Corrective Controls: Take action to remediate or mitigate the impact of an incident (e.g., dynamic blocking systems).

Dynamic Blocking Control is not a standard category.

Dynamic Blocking:

The described system actively blocks IP addresses after identifying malicious behavior, making it corrective in nature.

Zero-Day Attack Mitigation:

This refers to dealing with unknown vulnerabilities, which is not the primary functionality of dynamic IP blocking.

Incident Response and Mitigation: Emphasizes corrective controls as key measures for neutralizing threats after detection.

Dynamic Protection Mechanisms: Highlights systems like dynamic blocking under the umbrella of corrective controls.