Gain insights into effective security techniques including patching, cryptography, and phishing prevention. Explore practices to make systems resistant and vulnerabilities more detectable, enhancing defense against attacks.

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

# Windows software update services
Since Windows is so prevalent, let’s look at Microsoft’s patching solution. Microsoft has a service called the [Windows Software Update Services](https://docs.microsoft.com/en-us/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus), or WSUS for short, that helps administrators manage the patching process for all the computers in a domain. With WSUS, you can push updates for Microsoft software to all the workstations in your domain. 

The details of WSUS are beyond the scope of this chapter, but here are the main things you’ll want to have:

# Automatic deployment
You should have an automatic deployment of patches enforced at the Windows domain level.
# Testing
You’ll want some level of testing of patches. Ideally, this would take the form of an automated test environment, where Windows computers go through the motions of simulating commonly performed actions. More realistically, this would take the form of delaying most patches a week or two in the hopes that this will give Microsoft more time to shake out any problems in the patching. Then, patches would be deployed in waves so that even if a patch breaks something, it will only impact a portion of your fleet, instead of every Windows computer in your organization.



 <font size="6">  &nbsp; &nbsp;  &nbsp; &nbsp;&nbsp;  &nbsp; &nbsp;   &nbsp;  &nbsp;   &nbsp;   &nbsp; &nbsp; &nbsp; &nbsp;       &nbsp;  &nbsp;  &nbsp; &nbsp;&nbsp;   &nbsp; &nbsp; &nbsp;   &nbsp; &nbsp; &nbsp;&nbsp;  **Q U I Z**  &nbsp;   </font> 

In this lesson, we'll study some Windows-related patching.

Introduction

Patching

Vulnerabilities

Cryptography

Windows

Phishing

Patching Windows

Windows software update services