Database Security (part 3 of 4)

By Ashwin Venugopal -

 



To read part 1 please click here
To read part 2 please click here
To read part 4 please click here


Vulnerability Assessment

SQL Vulnerability Assessment is an easy-to-configure service that can discover, track, as well as help you remediate potential database vulnerabilities and provides visibility into your security state. It can help you:

  • Meet compliance requirements that require database scan reports.
  • Meet data privacy standards.
  • Monitor a dynamic database environment where changes are difficult to track.

Vulnerability assessment is a scanning service built into Azure SQL Database and its rules are based on the Microsoft's best practices and focus on the security issues that present the biggest risks to your database and its valuable data. The results of the scan includes actionable steps to resolve each issue and provide customized remediation scripts wherever applicable. 

View the report

When your scan is finished, your scan report is automatically displayed in the Azure portal which presents an overview of your security state. The results includes warnings on deviations from the best practices and a snapshot of your security-related settings, such as database principles and roles as well as their associated permissions while the report also provides a map of sensitive data discovered in your database including recommendations to classify that data by using data discovery and classification.

Scan results are shown below:


  Set your baseline

As you review your assessment results, you can mark specific results as being an acceptable baseline in your environment and the results that match the baseline are considered as passing in subsequent scan. After you have established your baseline security state, Vulnerability Assessment only reports on deviations from the baseline which helps you to focus your attention on the relevant issues.

Advanced Threat Protection

Advanced Threat Protection (ATP) for single and pooled databases detects anomalous activities indicating unusual and potentially harmful attempts to access or exploit databases while easily identifying the Potential SQL injection, Access from unusual location or data center, Access from unfamiliar principle or potentially harmful application, and Brute force SQL credentials. 

ATP provides a new layer of security, which enables customers to detect and respond to potential threats as they occur by providing security alerts on anomalous activities. 

Advanced threat protection alerts

ATP for Azure SQL Database detects anomalous activities indicating unusual and potentially harmful attempts to access or exploit databases and it can trigger the following alerts:

  • Vulnerability to SQL injection- This alert is triggered when an application generates a faulty SQL statement in the database. There are two possible reasons for the generation of a faulty statement, either it is a defect in application code that constructs the faulty SQL statement, or, the application codes or stored procedures don't sanitize user inputs when constructing the faulty SQL statement, which may be exploited for SQL injection.

  • Potential SQL injection- This alert is triggered when an active exploit happens against an identified application vulnerability to SQL injection. This means the attacker is trying to inject malicious SQL statements using the vulnerable application code or stored procedures.

  • Access from unusual location- This alert is triggered when there is a change in the access pattern to SQL server, where someone has logged on to the SQL server from an unusual geographical location. 

  • Access from unusual Azure data center- This alert is triggered when there is a change in the access pattern to SQL server, where someone has logged on to the SQL server from an unusual Azure data center that was seen on this server during the recent period. 

  • Access from unfamiliar principle- This alert is triggered when there is a change in the access pattern to SQL server, where someone has logged on to the SQL server using an unusual principle (SQL user). 

  • Access from a potentially harmful application- This alert is triggered when a potentially harmful application is used to access the database. 

  • Brute force SQL credentials- This alert is triggered when there is an abnormal high number of failed logins with different credentials.       

ATP is integrated with Azure Security Center to detect and respond to the potential threats as they occur. 


To read part 1 please click here
To read part 2 please click here
To read part 4 please click here







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