CompTIA Security+ Exam Notes

CompTIA Security+ Exam Notes
Let Us Help You Pass
Showing posts with label change management. Show all posts
Showing posts with label change management. Show all posts

Saturday, November 2, 2024

The Role of Change Management in Organizational Security

 Change Management

Change management processes are crucial for maintaining security within an organization. They ensure that any system or configuration modifications are carefully planned, documented, reviewed, and implemented in a controlled manner, minimizing the risk of unauthorized changes and potential security vulnerabilities that could arise from poorly managed updates or alterations.

Key benefits of change management for security:

Reduced risk of unauthorized changes:

By defining clear approval processes and documenting all changes, change management prevents unauthorized individuals from making alterations to critical systems, mitigating the risk of malicious activity or accidental errors.

Early identification of security vulnerabilities:

A structured change management process allows for security reviews during the planning phase, enabling the identification and mitigation of potential security risks before changes are implemented.

Improved accountability:

By tracking who initiated, approved, and implemented changes, change management enhances accountability and allows for easier investigation of any security incidents.

Consistent application of security policies:

Change management ensures that all changes are implemented in line with established security policies and standards, maintaining a consistent security posture across the organization.

Minimized disruption to operations:

By carefully planning and testing changes before deployment, change management helps to minimize system downtime and operational disruptions caused by poorly managed updates.

Employee awareness and training:

Effective change management involves communicating changes to employees and providing necessary training to ensure they understand the impact of changes on security practices.

How change management impacts security:

Access control:

By managing user access and permissions during changes, change management helps to prevent unauthorized access to sensitive data.

Patch management:

When applying software updates or security patches, change management ensures that the process is properly controlled and monitored to avoid introducing new vulnerabilities.

Configuration management:

By documenting and managing system configurations, change management helps to maintain a consistent security baseline across the environment.

Incident response:

When security incidents occur, detailed change logs can be used to identify the root cause and potential points of compromise.

In summary, a robust change management process is critical for maintaining a secure IT environment by ensuring that all modifications to systems and configurations are carefully evaluated, approved, and implemented in a controlled manner, reducing the risk of unintended security breaches and maintaining compliance with security standards.

Friday, October 12, 2018

Security Controls - Preventive

Preventive

What you are trying to do is prevent some form of security breach/incident.

Change management: Making sure that there or no outages that were not planned. Being as I work as an IT administrator, it's easy to want to make changes on the fly. The first step in this process is to submit the change plan and get approval. These changes can be network configuration changes or changing to a more current operating system. We need to plan, test, and practice before attempting the changes to reduce the chances of downtime on a production network.

Security awareness and training: Make users aware of social engineering attacks, email, and social network best practices. Once the users are aware of the tactics a social engineer might use, the less chance of them being fooled into revealing the passwords. For example, Microsoft is not going to call you and ask for your password, which is a threat actor attempting to social engineer you.


Disabling Accounts: Having an account disablement policy when an employee leaves the organization can help prevent the former employee from access their old account and possibly causing a security breach. 

In 2008 a contractor working for Fannie Mae was told during the day that he was being fired for a scripting error he made earlier in the month. He was allowed to work through the end of the day. He then loaded a logic bomb set to launch a few months later. Luckily for the company, the logic bomb was discovered, otherwise, it would have crashed 4000 servers crippling Fannie Mae.

Disabling his account as soon as he was notified would have prevented the contractor from installing the logic bomb.


Hardening systems: This best practice includes systems, applications, and operating systems. Disabling unnecessary services, and protocols. Applying security patches and updating firmware. Changing default usernames and passwords. Disabling unnecessary accounts. Disabling unused ports on switches.