Updating rule name and links

Author: limwainstein

articles/sentinel/whats-new.md

@@ -30,9 +30,9 @@ See these [important announcements](#announcements) about recent changes to feat
 
 You can now [work with the Microsoft Sentinel solution for SAP® applications across multiple workspaces](sap/cross-workspace.md) in different scenarios. This feature allows improved flexibility for managed security service providers (MSSPs) or a global or federated SOC, data residency requirements, organizational hierarchy/IT design, and insufficient role-based access control (RBAC) in a single workspace. One common use case is the need for collaboration between the security operations center (SOC) and SAP teams in your organization. Read about [the scenarios that address this use case](sap/cross-workspace.md).
 
-### Protection against risky configuration of SAP security parameters
+### Monitoring the configuration of static SAP security parameters
 
-To secure the SAP system, SAP has identified security-related parameters that need to be monitored for changes. With the ["Risky Configuration" analytics rule](sap/sap-solution-security-content.md#risky-configuration-of-security-parameters), the Microsoft Sentinel solution for SAP® applications tracks [over 52 security-related parameters](sap-risky-configuration-parameters.md) in the SAP system, and triggers an alert once these parameters are changed not according to the policy.
+To secure the SAP system, SAP has identified security-related parameters that need to be monitored for changes. With the ["SAP - (Preview) Sensitive Static Parameter has Changed" analytics rule](sap/sap-solution-security-content.md#monitoring-the-configuration-of-static-sap-security-parameters), the Microsoft Sentinel solution for SAP® applications tracks [over 52 security-related parameters](sap-suspicious-configuration-security-parameters.md) in the SAP system, and triggers an alert once these parameters are changed not according to the policy.
 
 For the Microsoft Sentinel solution for SAP® applications to successfully monitor the SAP security parameters, the solution needs to successfully monitor the SAP PAHI table at regular intervals. [Verify that the solution can successfully monitor the PAHI table](sap/preparing-sap.md#verify-that-the-pahi-table-history-of-system-database-and-sap-parameters-is-updated-at-regular-intervals).