Connect Non-Azure Resources to Azure Defender

By Ashwin Venugopal -

 



Protect Non Azure Resources

Besides defending your Azure environment, you can also add Azure Defender capabilities to your hybrid environment to: 
  • Protect your non Azure servers.
  • Protect your VMs in other clouds (such as AWS and GCP).
  • Protect SQL databases.
For machines, the Log Analytics Agent is the only required technology while providing more insights for the security alerts, connecting other cloud providers resources to offer cloud security posture management information. 

Add non Azure machines with Azure Arc

Azure Arc enabled servers always preferred the way of adding your non Azure machines to the Azure Security Center while providing enhanced capabilities such as the option to enable the guest configuration policies on the machine, deploy the Log Analytics agent as an extension, simplify deployment with other Azure services, and more.

What are Azure Arc enabled servers?

Azure Arc enabled servers permits you to manage your windows and Linux machines hosted outside of Azure, on your corporate network, or the other cloud providers consistent with how you manage native Azure Virtual Machines. When a hybrid machine is connected to Azure, it becomes a connected machine and is treated as a resource in Azure that has a Resource ID, which is included in a resource group, and benefits from standard Azure constructs such as Azure Policy and applying tags.  

The Azure Connected Machine agent needs to be installed on each machine that you plan on connecting to Azure to get this experience with your hybrid machines hosted outside of Azure. This agent does not deliver any other functionality, or replace the Azure Log Analytics agent. 

Add non-Azure machines from the Azure portal

You can start the process of adding a non-Azure server from two different locations in Security Center:
  1. From Security Center's menu, open the Getting started page. 
  2. Select the Get Started tab. 
  3. Below Add non-Azure servers, select Configure.
  4. From Security Center's menu, open the Inventory page.
  5. Select the Add non-Azure servers button. 
Log Analytics workspaces list is shown which includes (if applicable) the default workspace created for you by the Security Center when automatic provisioning, from which you can select Add Servers for the relevant workspace.  After that the agent management page appears where you can choose the relevant procedure below depending on the type of machines you're onboarding:
  • Onboard your Azure Stack VMs.
  • Onboard your Linux machines.
  • Onboard your Windows machines

Connect AWS Accounts

Onboarding your AWS account into the Security Center, integrates AWS Security Hub and Azure Security Center which provides visibility and protection across both of these cloud environments to provide:
  • Automatic agent provisioning 
  • Policy management
  • Vulnerability management
  • Embedded Endpoint Detection and  Response
  • Detection of security misconfigurations
  • A single view showing Security Center recommendations and AWS Security Hub findings
  • Incorporation of your AWS resources into Security Center's secure score calculations
  • Regulatory compliance assessments of your AWS resources

Connect your GCP accounts

Onboarding your GCP account into Security Center, integrates GCP Security Command an Azure Security Center which provides the visibility and protection across both of these cloud environments to provide:
  • Detection of security misconfigurations
  • A single view showing Security Center recommendations and GCP Security Command Center findings
  • Incorporation of your GCP resources into Security Center's secure score calculations
  • Integration of GCP Security Command Center recommendations based on the CIS standard into the Security Center's regulatory compliance dashboard 












Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more