Syncing Security Groups with team membership
In this post, I present a PowerShell script to synchronize the membership between security groups and Office 365 groups, a long-standing request from Microsoft Teams admins and team owners. Source code on GitHub at https://github.com/danspot/Danspot-Scripts-and-Samples-Emporium.Protecting your information and staying compliant with Microsoft Teams
We want Microsoft Teams to contribute to your security and compliance requirements and you probably have a lot of questions on how this happens. You may be used to protecting email and files in Microsoft 365 and on your mobile devices, but how should you approach security and compliance as you add Teams to the mix? As we enter the new year, we’ll help you answer these top-of-mind questions starting with the latest episode in our Microsoft Teams for IT series on Microsoft Mechanics, dedicated to security and compliance.Office 365 Advanced Threat Protection for SharePoint, OneDrive and Microsoft Teams now available
When moving your organization to cloud services, security concerns add another layer of consideration; one of trust. Security and compliance is an ongoing process, not a steady state. It is constantly maintained, enhanced, and verified by highly-skilled, experienced and trained personnel. We strive to keep software and hardware technologies up to date through robust processes. To help keep Office 365 security at the top of the industry, we use processes such as the Security Development Lifecycle; we also employ techniques that throttle traffic and prevent, detect, and mitigate breaches.The latest security enhancements for Azure Stack Hub
Security has always been at the heart of Azure. As we strive to deliver the latest security innovations to our customers, our team has improved the end-to-end experience from user workloads through the underlying infrastructure. With today’ security news and announcements, we’re sharing enhanced tools from Azure, from our partners, and Azure Stack Hub that enable you to improve your security posture. Azure Security tools: Azure Sentinel and Azure Security Center https://azure.microsoft.com/en-us/services/azure-sentinel/ recently added support for workloads running on Azure Stack Hub. Azure Sentinel enables you to detect threats and respond smarter and faster though Azure powered artificial intelligence. To learn more about this integration, click https://docs.microsoft.com/en-us/azure/sentinel/connect-azure-stack. We’re also bringing our ongoing investment in cloud security with Azure Security Center to Azure Stack Hub. https://azure.microsoft.com/en-us/services/security-center/ is a unified infrastructure security management system that strengthens the security posture of your data centers and provides advanced threat protection (including server Endpoint Detection and Response - EDR) across your hybrid workloads. With Azure Security Center, you can receive actionable, prioritized security recommendations, powered by https://docs.microsoft.com/azure/security-center/security-center-secure-score, in order to assess the security of your Windows and Linux VMs running on top of Azure Stack Hub and improve your compliance with regulatory standards. To learn more about this integration, click https://docs.microsoft.com/en-us/azure/security-center/quick-onboard-azure-stack. How Partners are Adding Security Expertise to Azure Stack Hub Many of our customers operate Azure Stack Hub in regulated or classified environments, where hardware protection and generation of keys and secrets are required. We https://azure.microsoft.com/en-us/blog/azure-stack-iaas-part-3/ our work with Thales to bring the https://www.thalesesecurity.com/products/key-management/ciphertrust-cloud-key-manager solution to the Azure Stack Hub marketplace. CCKM enables customers to upload, manage, and revoke keys to and from Azure Key Vaults running in either Azure Stack Hub or Azure, all from a single pane of glass. Thales CCKM works with Azure and Azure Stack Hub “Bring Your Own Key” (BYOK) APIs to enable such key control. CCKM creates Azure-compatible keys from a FIPS 140-2 source, like the https://www.thalesesecurity.com/products/data-encryption/vormetric-data-security-manager that can achieve FIPS 140-2 Level 3 compliancy. CCKM supports both Azure Active Directory (AAD) and Active Directory Federation Services (ADFS) deployments, hence it can run in air-gapped or disconnected environments. For customers interested in obtaining vulnerability reports and DISA STIG assessments of the Azure Stack Hub infrastructure, we’re happy to announce that Qualys has made them generally available from the https://www.qualys.com/azure-stack/. With each Azure Stack Hub update release, Microsoft will provide to Qualys a new vulnerability report generated with the Qualys Cloud Platform, enabling our customers to have the latest report available to meet their compliance requirements. Customers can also use Qualys Virtual Scanner Appliances, Qualys Cloud Agents or Qualys Container Sensors to assess their Azure Stack Hub workloads, including Kubernetes-based containers. Splunk recently released a dashboard for the Azure Stack Hub infrastructure. The dashboard uses Azure Stack Hub domain-specific knowledge to enable Azure Stack Hub operators to closely monitor important security events, such as code integrity violations, privileged endpoint access or suspicious activity via Windows Defender. This will allow organizations to have greater visibility into their Azure Stack Hub environment and reduce time to remediate. The https://splunkbase.splunk.com/app/4559/ and the https://splunkbase.splunk.com/app/4558/ are available for download on Splunkbase. Infrastructure Updates Further Enhance Azure Stack Hub Security At the Azure Stack Hub infrastructure level, with the 1910 release, Azure Stack Hub now uses 4096 bit RSA keys for the internal certificates, supports AES256 for data at rest encryption and Kerberos authentication, SHA384 for VPN encryption and it complies with the Committee on National Security Systems - Policy 15 (CNSSP-15) which provides best practices for the use of public encryption standards for secure information sharing. Beginning with the 1908 release, Azure Stack Hub runs in FIPS mode and the data at rest encryption secrets are persisted in the Trusted Platform Module (TPM) 2.0 chips. The 1906 release brought the capability of Azure Stack Hub operators to enforce the https://docs.microsoft.com/en-us/azure-stack/operator/azure-stack-security-configuration on the external endpoints. This new capability helps Azure Stack Hub operators to secure their communications by using the more secure TLS 1.2 as the only TLS version allowed. In preparation for this new capability, we also validated TLS 1.2 for the virtual machines extensions in the Azure Stack Hub marketplace so that you can secure your end-to-end communications with Azure Stack Hub and the workloads running on top of it. Starting with the 1906 release, we have been adding improvements to the internal secret rotation engine as we work through making it fully autonomous. We also added a safeguard to prevent the expiration of internal secrets by forcing internal secrets rotation in case a critical alert on expiring secrets is ignored. As we continue to work on security features for Azure Stack Hub, let us know if there are first or third party features that you would like to see in Azure Stack Hub by leaving a comment below.
