Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
A CISO Guide to Cyber Resilience

You're reading from   A CISO Guide to Cyber Resilience A how-to guide for every CISO to build a resilient security program

Arrow left icon
Product type Paperback
Published in Apr 2024
Publisher Packt
ISBN-13 9781835466926
Length 238 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Debra Baker Debra Baker
Author Profile Icon Debra Baker
Debra Baker
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Preface 1. Part 1: Attack on BigCo FREE CHAPTER
2. Chapter 1: The Attack on BigCo 3. Part 2: Security Resilience: Getting the Basics Down
4. Chapter 2: Identity and Access Management 5. Chapter 3: Security Policies 6. Chapter 4: Security and Risk Management 7. Chapter 5: Securing Your Endpoints 8. Chapter 6: Data Safeguarding 9. Chapter 7: Security Awareness Culture 10. Chapter 8: Vulnerability Management 11. Chapter 9: Asset Inventory 12. Chapter 10: Data Protection 13. Part 3: Security Resilience: Taking Your Security Program to the Next Level
14. Chapter 11: Taking Your Endpoint Security to the Next Level 15. Chapter 12: Secure Configuration Baseline 16. Chapter 13: Classify Your Data and Assets 17. Chapter 14: Cyber Resilience in the Age of Artificial Intelligence (AI) 18. Index 19. Other Books You May Enjoy

Change management

Change management is ensuring all changes to your IT environment are managed, approved, and documented throughout the entire process. This ensures orderly software and hardware changes are made in your environment. When I worked at IBM in the 1990s, I was part of the Network Team supporting the IBM Southeast Geoplex. I really learned about the change management process while at IBM. I was mentored by two different people on changes who each had their own way of performing changes. The first person who trained me on doing changes would put in a ticket, get approval, and then we would show up during the change window and figure out and make the change. You don’t want to do this. The second person I worked with had a very different and much better approach. Of course, we would enter a ticket into the ITSM system. We would get approval to do the change during off hours. We would send out an email notification related to the change to potentially affected users...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime