​2​ Policy Management Policy

EA implements policies and procedures to maintain compliance and integrity of data. The Security Officer and Privacy Officer are responsible for maintaining policies and procedures and ensuring all EA workforce members, customers, and partners are adherent to all applicable policies. Previous versions of policies are retained to assure ease of finding policies at specific historic dates in time.

​2.1​ Maintenance of Policies

1. All policies are stored and up to date to maintain EA compliance with PIPEDA, and other relevant standards. Updates and version control are done similar to source code control.
2. Policy update requests can be made by any workforce member at any time. Furthermore, all policies are reviewed annually by both the Security and Privacy Officer to assure they are accurate and up-to-date.
3. EA employees may request changes to policies using the following process:
   1. The EA employee initiates a policy change request by creating an Issue in the Asana Compliance Review Activity (CRA) project. The change request may optionally include a GitHub pull request from a separate branch or repository containing the desired changes.
   2. The Security Officer or the Privacy Officer is assigned to review the policy change request.
   3. Once the review is completed, the Security Officer approves or rejects the Issue. If the Issue is rejected, it goes back for further review and documentation.
   4. If the review is approved, the Security Officer then marks the Issue as Done, adding any pertinent notes required.
   5. If the policy change requires technical modifications to production systems, those changes are carried out by authorized personnel using EA’s change management process.
4. All policies are made accessible to all EA workforce members. The current master policies are published at https://effortlessdev.github.io/policies/.
   1. Changes are automatically communicated to all EA team members through integrations between GitHub and Slack that log all GitHub policy channels to a dedicated EA Slack Channel.
   2. The Security Officer also communicates policy changes to all employees via email. These emails include a high-level description of the policy change using terminology appropriate for the target audience.
5. All policies, and associated documentation, are retained for 6 years from the date of its creation or the date when it last was in effect, whichever is later
   1. Version history of all EA policies is done via GitHub.
   2. Backup storage of all policies is done with Google Drive.
6. The policies and information security policies are reviewed and audited annually, or after significant changes occur to EA’s organizational environment. Issues that come up as part of this process are reviewed by EA management to assure all risks and potential gaps are mitigated and/or fully addressed. The process for reviewing policies is outlined below:
   1. The Security Officer initiates the policy review by creating an Issue in the Asana Compliance Review Activity (CRA) project.
   2. The Security Officer or the Privacy Officer is assigned to review the current EA policies (https://effortlessdev.github.io/policies/).
   3. If changes are made, the above process is used. All changes are documented in the Issue.
   4. Once the review is completed, the Security Officer approves or rejects the Issue. If the Issue is rejected, it goes back for further review and documentation.
   5. If the review is approved, the Security Officer then marks the Issue as Done, adding any pertinent notes required.
7. Policy review is monitored on a quarterly basis using Asana reporting to assess compliance with above policy.