The leadership team wants to track reputational risk, so I've set up automated factors to monitor CSAT scores. A bad customer experience can affect business. There's one application that consistently stays high risk for reputational scores (bad CSAT scores), even though the other controls are compliant and there are no audit issues. Upon investigation, it looks like this application has had several outages. I'm going to need to bring together the development team and customer service manager to discuss a remediation plan Use approved IP ranges in config files. Tech Tip: Many organizations house their policies on a SharePoint site or other application. Consider Figure 7: Complying with policies doesn9t need to slow down development moving your policies into ServiceNow so that The DevOps team has been working hard and releasing code quickly. The you can easily outages are often a result of small data fixes and a few bad coding practices. We associate policies with need to add policies and controls for the DevOps team alongside the other controls and risks and policies and controls for the application. report on compliance. The application happens to be updated during the next dev cycle. We can see You can also request that the policy we put in place to ensure that developers have access to and are policy exceptions. using the right IP ranges in the config files identified a violation. Addressing these issues before customers are affected helps improve customer satisfaction scores. Integration with O365 A single platform that allows application managers, development teams, and risk and Word make it easy teams to share data and work together can help reduce the impact of business to collaborate, keep application development issues and application sprawl. policies current, and track versions. 10
Integrated Risk and Compliance Page 9 Page 11