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

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more