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

## Identify authorized devices

The first step in protecting endpoints is to identify them. One of the most dangerous things on a network is a rogue, unmanaged device with an unknown patch level and security posture. Maintaining an inventory of devices makes it easier to identify those who aren’t authorized or secure enough to be on the network.


Take the time to discover and document all assets properly. These include the following: 

- Servers 

- Workstations 

- Network equipment 

- Mobile devices 

Start with the production network, but don't exclude other test, development, and staging environments. The result is an asset database, also known as a **configuration management database (CMDB)**. A CMDB is a centralized repository of asset information.






# Identify authorized devices

The first step in protecting endpoints is to identify them. One of the most dangerous things on a network is a rogue, unmanaged device with an unknown patch level and security posture. Maintaining an inventory of devices makes it easier to identify those who aren’t authorized or secure enough to be on the network.


Take the time to discover and document all assets properly. These include the following: 

- Servers 

- Workstations 

- Network equipment 

- Mobile devices 

Start with the production network, but don't exclude other test, development, and staging environments. The result is an asset database, also known as a **configuration management database (CMDB)**. A CMDB is a centralized repository of asset information.






Learn to use a configuration management database (CMDB) to manage the assets of an organization.

Introduction

Basics of Security

Detect

Protect

Respond

Conclusion

Configuration Management Database

Identify authorized devices