Gain insights into cyber security fundamentals, explore common threats, discover protection mechanisms like firewalls, learn monitoring and response strategies, and develop secure systems as a developer.

Modern computer systems are almost universally connected, which creates wider attack surfaces well beyond code to users, hardware, and more. Securing systems is thus a fundamental skill for modern software engineers.

This course is a comprehensive introduction to cyber security best practices. You’ll start with an overview of common threats and vulnerabilities, as well as high-level concepts like privilege, integrity, logging, and mediation. With these concepts in mind, you’ll then learn common protection mechanisms and defense strategies from endpoint protection to firewalls, gateways, and proxy servers. Next, you’ll learn monitoring and detection techniques, alerts, and event management. Finally, when you detect a threat, you’ll know how to respond with support tickets, data preservation, and change management.

By the end of this course, you’ll have a better understanding of modern cyber security practices and a clear roadmap to implementing these as a developer.

Cyber Security Best Practices for Developers

## Why change is necessary? 

Change is inevitable. This is especially true of software and IT systems. Changes are necessary for a variety of reasons, including:

- Adding features

- Removing functionality

- Fixing bugs

- Installing patches

- Applying updates

- Mitigating vulnerabilities

Something that can’t be changed shouldn’t be on the production network. This is because there’s always a chance of finding a security vulnerability or other problem. When it’s found, it needs to be updated as quickly as possible, ideally before it’s exploited.


## Frameworks to perform changes

When a change is performed, it should be done in a controlled manner that minimizes the chance that something else will break. Software patches that are intended to fix something often end up breaking them instead.


To minimize the risk of something going wrong, and to quickly recover if it does, a formal change management process should be followed. There are several frameworks available, such as:


- Capability Maturity Model Integration (CMMI)

- National Institute of Standards and Technology (NIST)

- Information Technology Infrastructure Library (ITIL)




# Why change is necessary? 

Change is inevitable. This is especially true of software and IT systems. Changes are necessary for a variety of reasons, including:

- Adding features

- Removing functionality

- Fixing bugs

- Installing patches

- Applying updates

- Mitigating vulnerabilities

Something that can’t be changed shouldn’t be on the production network. This is because there’s always a chance of finding a security vulnerability or other problem. When it’s found, it needs to be updated as quickly as possible, ideally before it’s exploited.


# Frameworks to perform changes

When a change is performed, it should be done in a controlled manner that minimizes the chance that something else will break. Software patches that are intended to fix something often end up breaking them instead.


To minimize the risk of something going wrong, and to quickly recover if it does, a formal change management process should be followed. There are several frameworks available, such as:


- Capability Maturity Model Integration (CMMI)

- National Institute of Standards and Technology (NIST)

- Information Technology Infrastructure Library (ITIL)




Learn the importance of changing an IT organization.

Introduction

Basics of Security

Detect

Protect

Respond

Conclusion

Change Management

Why change is necessary?