docker.tar.gz

network-commands

node

It seems like hardly a week goes by without a high-profile computer breach. Why do these happen? How can you prevent them? This course doesn’t have all the answers, but it does outline practices that make life harder for attackers and that will help tide you over until you get a full-time security team in place.

In this course, you will learn 5 simple, yet effective, techniques for preventing attackers from getting into your system. These techniques are related to: patching, software vulnerabilities, cryptography, windows security, and phishing. Within each chapter you will learn the best practices for preventing vulnerabilities and how to make them more detectable. 

This course is based on the Pragmatic Programmers’ book, Practical Security, and is aimed at developers, admins, team leads, architects, technology generalists, and all others who stand guard against the things that disrupt the network.

Practical Security: Simple Practices for Defending Your Systems

## Quick recap
Cryptography is very difficult to get right. Don’t write your own, and don’t use low-level libraries. Instead, use high-level libraries that have a degree of misuse-resistance. Use [NaCl](https://nacl.cr.yp.to/), [libsodium](https://libsodium.org/), or [Tink](https://github.com/google/tink) for encryption at rest. Use TLS 1.3 (or TLS 1.2 if you have legacy constraints) in a configuration that gets an A from [SSL Labs](https://www.ssllabs.com/) for data in transit. Use [scrypt](https://www.tarsnap.com/scrypt), [bcrypt](https://en.wikipedia.org/wiki/Bcrypt), [PBKDF2](https://en.wikipedia.org/wiki/PBKDF2), or [Argon2](https://password-hashing.net/#argon2) for password hashing.

## Next up
Next up, we’ll take a look at some best practices relating to Windows. In particular, we’ll take a look at the way that Windows handles password hashing.

# Quick recap
Cryptography is very difficult to get right. Don’t write your own, and don’t use low-level libraries. Instead, use high-level libraries that have a degree of misuse-resistance. Use [NaCl](https://nacl.cr.yp.to/), [libsodium](https://libsodium.org/), or [Tink](https://github.com/google/tink) for encryption at rest. Use TLS 1.3 (or TLS 1.2 if you have legacy constraints) in a configuration that gets an A from [SSL Labs](https://www.ssllabs.com/) for data in transit. Use [scrypt](https://www.tarsnap.com/scrypt), [bcrypt](https://en.wikipedia.org/wiki/Bcrypt), [PBKDF2](https://en.wikipedia.org/wiki/PBKDF2), or [Argon2](https://password-hashing.net/#argon2) for password hashing.

# Next up
Next up, we’ll take a look at some best practices relating to Windows. In particular, we’ll take a look at the way that Windows handles password hashing.

Introduction

Patching

Vulnerabilities

Cryptography

Windows

Phishing

What’s Next?

Quick recap

Next up