Azure, just as any other industry flagship, spends a lot of time working on upgrading its current features and developing new ones. Privileged Identity Management feature (PIM) that enables you with more efficient resource management and control is one of the most recent releases.
Admittedly, the newly released VMware vSphere 7 Update 2 has brought along a lot of new interesting features. However, while the primary upgrades have been widely discussed, not all improvements have got their fair share of the spotlight, leaving some prominent new additions largely unnoticed.
In Part 1, we talked about the security principle of two-factor authentication and how to prepare your existing Remote Desktop (RD) Gateway for Network Policy Server (NPS) Extension for Azure Multi-Factor Authentication (MFA). Now, it’s time to integrate the solution and look at the logs and tools for troubleshooting in case any issues occur.
Network Policy Server (NPS) Extension for Azure Multi-Factor Authentication (MFA) is a good choice to enhance the security of your Remote Desktop (RD) Gateway. This combination will use two-step verification for client authentication to add another protection layer to your NPS/RADIUS (Remote Authentication Dial-In User Server).
Azure Sentinel is growing in popularity when it comes to Security Orchestration, Automation, and Response (SOAR). Not only does it inform you when an incident becomes true, but it also functions as a response system to address it. The software exists to significantly reduce Mean-Time-to-Response, tightening your security even more.
Azure Kubernetes Service (AKS) is incredibly multifaceted. For example, you can test the connectivity of an SQL server that’s using a private endpoint connection to your AKS cluster using a pod. You can even manage SQL databases without deploying a VM or installing SQL Server Management Studio or other software.
File servers and hosted shares on Microsoft Windows have shares and permissions not necessarily known to everybody in the environment. With cybersecurity in mind, you’ll sooner or later have to share and/or migrate files, folders, and user profiles. There is no one solution, but you can consider several to keep in mind when it comes to migration.
Managing and ensuring the compliance of departments in your tenant is important to cybersecurity and smooth workflow. This is especially relevant for medium and large deployments. Combining Azure resources into groups and using Role-Based Access Management (RBAC) will reduce threats and increase work efficacy. Azure Policy can help enhance those processes further.
In Part 1 we focused on overall information on SMB over QUIC and how to make the necessary preparations for all to function well. Today, we’ll focus on the technicalities. It will be somewhat a tedious process but we’ve laid out everything in minute detail, so you don’t have to break your neck trying to figure it all out 😉