Planning for security in Microsoft Dynamics GP
This document is designed to make you aware of actions that you can complete to
help make your Microsoft Dynamics GP data as secure as possible.
As the foundation for Microsoft Dynamics GP, Windows provides
sophisticated standards-based network security. In the broadest sense, security
involves planning and considering tradeoffs. For example, a computer can be
locked in a vault and only accessible to one system administrator. This computer
may be secure, but it is not very usable because it is not connected to any other
computer. You need to consider how to make the network as secure as possible
without sacrificing usability.
Most organizations plan for external attacks and construct firewalls, but many
companies do not consider how to mitigate a security breach if a malicious user
gets inside the firewall. Security measures in your organization’s environment will
work well if users are not required to perform too many procedures and steps to
conduct business in a secure manner. Implementing security policies should be as
easy as possible for users, or they will tend to find less secure ways of doing things.
Because the size of Microsoft Dynamics GP implementations can vary a great deal, it is
important to carefully consider the needs of a smaller business and to weigh the
effectiveness of security against the costs that may be involved. Use your best
judgment to recommend a policy that helps to meet security needs.
This document discusses the following topics:
| • | Basic security recommendations |
| • | Securing the server operating system |
| • | Network security |
| • | Virus protection |
| • | Microsoft Dynamics GP security |
| • | The Microsoft Dynamics GP database security model |
| • | Core application security tasks |
| • | Frequently asked questions about security in Microsoft Dynamics GP |
