Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Windows Ransomware Detection and Protection

You're reading from   Windows Ransomware Detection and Protection Securing Windows endpoints, the cloud, and infrastructure using Microsoft Intune, Sentinel, and Defender

Arrow left icon
Product type Paperback
Published in Mar 2023
Publisher Packt
ISBN-13 9781803246345
Length 290 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Marius Sandbu Marius Sandbu
Author Profile Icon Marius Sandbu
Marius Sandbu
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Part 1:Ransomware Basics
2. Chapter 1: Ransomware Attack Vectors and the Threat Landscape FREE CHAPTER 3. Chapter 2: Building a Secure Foundation 4. Part 2:Protect and Detect
5. Chapter 3: Security Monitoring Using Microsoft Sentinel and Defender 6. Chapter 4: Ransomware Countermeasures – Windows Endpoints, Identity, and SaaS 7. Chapter 5: Ransomware Countermeasures – Microsoft Azure Workloads 8. Chapter 6: Ransomware Countermeasures – Networking and Zero-Trust Access 9. Chapter 7: Protecting Information Using Azure Information Protection and Data Protection 10. Part 3:Assume Breach
11. Chapter 8: Ransomware Forensics 12. Chapter 9: Monitoring the Threat Landscape 13. Chapter 10: Best Practices for Protecting Windows from Ransomware Attacks 14. Index 15. Other Books You May Enjoy

Hub-and-spoke virtual networks

When building a scalable network architecture in Azure, many organizations use a common network topology that relies on virtual network chaining, also known as hub-and-spoke network architecture. This topology uses the concept of a connecting group of networks to a virtual network hub like a chain. In this design, as seen in the following diagram, it is easy to add and remove spokes without affecting the rest of the network. This architecture uses a feature called VNet peering to connect the different spokes to the hub. This ensures that traffic from one spoke to another will need to go through the hub before going to another spoke. Since VNet peering is nontransitive, this ensures that spoke one cannot directly communicate with spoke two without going through the centralized firewall, as seen in the following diagram.

Figure 5.3 – Hub-and-spoke network in Microsoft Azure

Figure 5.3 – Hub-and-spoke network in Microsoft Azure

This topology commonly uses centralized monitoring...

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
Banner background image