Introduction
Security is an essential part of any implementation. Failure to plan security aspects, or addressing security requirements too late, might lead to project delays and implementation issues such as audit failures and unplanned extra effort. Retrofitting security solutions into the architecture at a late point in time can potentially conflict with other feature designs and native capabilities and even introduce technical issues.
Considerations for a successful security strategy that are covered in this module are:
Strategy overview and workstream
Regulation, compliance, and other requirements
Implementation beyond Microsoft Dynamics 365
Implementation within Dynamics 365
Testing
Management, monitoring, auditing
The security workstream isn't purely functional or technical, and knowledge of business processes, audit requirements, and technical aspects of Dynamics 365 are all required. A successful security strategy requires collaboration across business, IT, and project management personas from the customer and partner.
The following units depict security scenarios with patterns (recommended practices) and anti-patterns (pitfalls) to provide scenario-based guidance on how to manage these challenges. While these scenarios aren't exhaustive, they provide a perspective on how to handle common scenarios and challenges.