Merge pull request #225475 from TerryLanfear/sec-230128

Freshness update

Author: American-Dipper

articles/security/fundamentals/database-security-checklist.md

@@ -3,40 +3,39 @@ title: Azure database security checklist| Microsoft Docs
 description: Use the Azure database security checklist to make sure that you address important cloud computing security issues.
 services: security
 documentationcenter: na
-author: unifycloud
-manager: barbkess
-editor: tomsh
+author: terrylanfear
+manager: rkarlin
 
 ms.assetid: 
-ms.service: information-protection
-ms.subservice: aiplabels
+ms.service: security
+ms.subservice: security-fundamentals
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: na
-ms.date: 11/21/2017
-ms.author: tomsh
+ms.date: 01/29/2023
+ms.author: terrylan
 ---
 
 # Azure database security checklist
 
-To help improve security, Azure Database includes a number of built-in security controls that you can use to limit and control access.
+To help improve security, Azure Database includes many built-in security controls that you can use to limit and control access.
 
-These include:
+Security controls include:
 
--    A firewall that enables you to create [firewall rules](/azure/azure-sql/database/firewall-configure) limiting connectivity by IP address,
--    Server-level firewall accessible from the Azure portal
--    Database-level firewall rules accessible from SSMS
--    Secure connectivity to your database using secure connection strings
--    Use access management
--    Data encryption
--    SQL Database auditing
--    SQL Database threat detection
+* A firewall that enables you to create [firewall rules](/azure/azure-sql/database/firewall-configure) limiting connectivity by IP address,
+* Server-level firewall accessible from the Azure portal
+* Database-level firewall rules accessible from SSMS
+* Secure connectivity to your database using secure connection strings
+* Use access management
+* Data encryption
+* SQL Database auditing
+* SQL Database threat detection
 
 ## Introduction
 Cloud computing requires new security paradigms that are unfamiliar to many application users, database administrators, and programmers. As a result, some organizations are hesitant to implement a cloud infrastructure for data management due to perceived security risks. However, much of this concern can be alleviated through a better understanding of the security features built into Microsoft Azure and Microsoft Azure SQL Database.
 
 ## Checklist
-We recommend that you read the [Azure Database Security Best Practices](/azure/azure-sql/database/security-best-practice)  article prior to reviewing this checklist. You will be able to get the most out of this checklist after you understand the best practices. You can then use this checklist to make sure that you've addressed the important issues in Azure database security.
+We recommend that you read the [Azure Database Security Best Practices](/azure/azure-sql/database/security-best-practice)  article prior to reviewing this checklist. You'll be able to get the most out of this checklist after you understand the best practices. You can then use this checklist to make sure that you've addressed the important issues in Azure database security.
 
 
 |Checklist Category| Description|
@@ -52,11 +51,11 @@ We recommend that you read the [Azure Database Security Best Practices](/azure/a
 |<br>Microsoft Defender for Cloud| <ul><li>[Data Monitoring](../../security-center/security-center-remediate-recommendations.md) Use Microsoft Defender for Cloud as a centralized security monitoring solution for SQL and other Azure services.</li></ul>|        
 
 ## Conclusion
-Azure Database is a robust database platform, with a full range of security features that meet many organizational and regulatory compliance requirements. You can easily protect data by controlling the physical access to your data, and using a variety of options for data security at the file-, column-, or row-level with Transparent Data Encryption, Cell-Level Encryption, or Row-Level Security. Always Encrypted also enables operations against encrypted data, simplifying the process of application updates. In turn, access to auditing logs of SQL Database activity provides you with the information you need, allowing you to know how and when data is accessed.
+Azure Database is a robust database platform, with a full range of security features that meet many organizational and regulatory compliance requirements. You can easily protect data by controlling the physical access to your data, and using various options for data security at the file-, column-, or row-level with Transparent Data Encryption, Cell-Level Encryption, or Row-Level Security. Always Encrypted also enables operations against encrypted data, simplifying the process of application updates. In turn, access to auditing logs of SQL Database activity provides you with the information you need, allowing you to know how and when data is accessed.
 
 ## Next steps
 You can improve the protection of your database against malicious users or unauthorized access with just a few simple steps. In this tutorial you learn to:
 
-- Set up [firewall rules](/azure/azure-sql/database/firewall-configure) for your server and or database.
-- Protect your data with [encryption](/sql/relational-databases/security/encryption/sql-server-encryption).
-- Enable [SQL Database auditing](/azure/azure-sql/database/auditing-overview).
+* Set up [firewall rules](/azure/azure-sql/database/firewall-configure) for your server and or database.
+* Protect your data with [encryption](/sql/relational-databases/security/encryption/sql-server-encryption).
+* Enable [SQL Database auditing](/azure/azure-sql/database/auditing-overview).

articles/security/fundamentals/event-support-ticket.md

@@ -1,45 +1,25 @@
 ---
-title: How to Log a Security Event Support Ticket - Azure | Microsoft Docs
+title: How to Log an Azure security issue - Azure | Microsoft Docs
 description: As a seller on the Azure Marketplace, having identified a potential security event, I need to know how to log an appropriate ticket.
 documentationcenter: na
 author: DavidBosland
-manager: lakoch
-editor: v-dabosl
+manager: rkarlin
 
 ms.assetid: f1ffde66-98f0-4c3e-ad94-fee1f97cae03
-ms.service: marketplace
-ms.subservice: partnercenter-marketplace-publisher
+ms.service: security
+ms.subservice: security-fundamentals
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: na
-ms.date: 11/13/2017
+ms.date: 01/29/2023
 ms.author: terrylan
 
 ---
-# How to Log a Security Event Support Ticket
+# Log a security issue
 
-1. Navigate to [Publisher Support](https://support.microsoft.com/en-us/getsupport?wf=0&tenant=ClassicCommercial&oaspworkflow=start_1.0.0.0&locale=en-us&supportregion=en-us&pesid=16230&ccsid=636450758943226673) and sign in with your Microsoft credentials.
-2. Select "Security Event" as the Problem Type and choose between the "Security Incident" and "Vulnerability" categories.
+Visit the [Microsoft Security Response Center](https://msrc.microsoft.com/create-report) (MSRC) to report a security specific issue.
 
-    ![Event type and Definition](./media/event-support-ticket/chart.png)
-
-3. After you select the Problem Type and Category, click the '**Start request**' button. Provide the following information to help us better understand the issue.
-
-    i. What is the problem and/or vulnerability?
-
-    ii. For vulnerabilities, please provide the CVE (mitre.org) or the filled out CVSS3 v3 calculator (https://www.first.org/cvss/calculator/3.0).
-
-    iii. Is there a resolution or mitigation? If yes, then please provide the remediation steps.
-
-    iv. Do you have a message that you want to send to customers? We will work with you to craft an appropriate message if applicable.
-
-4. Submission confirmation - Once you have submitted your issue, we will acknowledge receipt within one business day and assign your issue a priority and severity.
-
-    - If you need to communicate with us about your issue, use the confirmation number in all correspondence.
-    - You can view progress on your issue at any time.
-
-5. What happens next? Depending on the issue and severity, the following steps may be taken:
-
-    - We will communicate the outcome of our assessment to you. Depending on the outcome, we may remove or request that you modify your offering. In this event, we will work with you to ensure that disruption to impacted customers is minimized.
-    - We will work with you to help mitigate the impact of the incident/vulnerability for our mutual customers.
+You can also create a tailored, Azure support request in the Azure portal. Visit the Azure portal [here](https://ms.portal.azure.com/#create/Microsoft.Support). Follow the prompts to receive recommended solutions or to log a support request.
 
+## Next steps
+[MSRC](https://msrc.microsoft.com/create-report) is part of the security community. Learn how MSRC helps to protect customers and the broader ecosystem.