Okay, that's it for this course.
The concept of active defense plays a very important role in security.
If you are sitting around waiting for something to happen,
it is already too late.
Practice defense in depth and look for signs of intrusion.
Every breach doesn't have to be a full, all hands on deck,
media front page event.
Using some of the tricks in this course and coming up with more on your own
will go a long way to narrowing the breach detection gap down from 7 months to
7 days to 7 hours to 7 minutes or even 7 seconds.
We started this course talking about setting traps in the form of honeypots.
This could be a token, credential, port,
file, service, or anything else you can think of,
there is no limit to this.
But attackers are on these traps and specifically
look for them in a breach scenario.
They try to stay as quiet as possible and observe.
Maintain the look of live credentials, servers, and services in your traps.
If you allow them to be stale, if you allow them to get stale,
it maybe a dead giveaway to an adversary who will then
have insights into your defenses.
These are not perimeter traps.
You are planting them along the attack pattern,
hoping at some point they slip up.
Even though all this is inside your network,
your desktops and servers are now your borders.
Actively go after and confirm configurations of the endpoints
on your network meet your company standards.
We talk through many tools you can use to pull configs,
update settings, and run scans all with a few lines of code.
Make sure all your systems are adhering to your standard.
I have a few other courses available on Pluralsight on automating
protections in other formats besides PowerShell.
If you are involved with the web applications your organization builds,
check out my penetration testing and OWASP ZAP automation courses.
I have put together a few courses on using Python in security,
also available to you here.
Okay,
hope to see you again over there or on one of my
future courses here at Pluralsight.
Goodbye for now.