top of page

EC4Labs.IO Data Security & Privacy Stance 

Core Security Practices:

A. Access Control:

  • Guideline: Limit access to sensitive data and systems to only those employees who absolutely need it to perform their job duties (Principle of Least Privilege).  

  • Procedure:

    1. Role-Based Access: Define access levels based on job roles (e.g., Consultant A can access client project files X and Y, but not client Z's financial data).  

    2. Unique Accounts: Each employee must have their own unique login credentials for all systems and applications. Sharing accounts is strictly prohibited.

    3. Strong Passwords: Mandate the use of strong, unique passwords (at least 12 characters, including a mix of uppercase and lowercase letters, numbers, and symbols). Avoid using personal information.  

    4. Password Management: Encourage the use of password managers to securely store and manage complex passwords.  

    5. Multi-Factor Authentication (MFA): Enable MFA on all accounts that support it, especially email, cloud storage, and internal systems.

    6. Regular Access Reviews: At least annually (or when an employee leaves or changes roles), review and update access permissions. Revoke access promptly when it's no longer needed.  

B. Device Security:

  • Guideline: Ensure all devices used for company business are secured against unauthorized access and malware.

  • Procedure:

    1. Endpoint Protection: Install and maintain up-to-date antivirus and anti-malware software on all company-issued and personal devices used for work. Enable automatic updates.  

    2. Screen Locks: Require automatic screen locks with a strong password or biometric authentication after a short period of inactivity (e.g., 15 minutes).

    3. Full Disk Encryption: Enable full disk encryption on all laptops and portable storage devices containing company or client data.

    4. Software Updates: Regularly install operating system and application updates and security patches promptly. Designate one person to be responsible for reminding the team about updates.

    5. Secure Wi-Fi: When working remotely, use strong, password-protected Wi-Fi networks. Avoid public, unsecured Wi-Fi for accessing sensitive data. Consider using a VPN.

C. Data Security in Transit and at Rest:

  • Guideline: Protect sensitive data from unauthorized access whether it's being transmitted or stored.  

  • Procedure:

    1. Encryption in Transit: Use secure protocols (HTTPS, SFTP, VPN) for transmitting sensitive data electronically. Avoid sending sensitive information via regular, unencrypted email.

    2. Encryption at Rest: Encrypt sensitive data stored on company servers, cloud storage, and local devices.  

    3. Secure Storage: Store physical documents containing sensitive information in locked cabinets or secure locations when not in use.  

    4. Data Backups: Implement a regular and automated backup process for critical data. Store backups in a separate, secure location (ideally offsite or in the cloud with appropriate security measures). Test backups periodically to ensure they are working.  

II. Data Handling Procedures:

A. Data Collection and Storage:

  • Guideline: Only collect and retain data that is necessary for providing services and as required by legal or contractual obligations.

  • Procedure:

    1. Data Minimization: Before collecting any new data, consider if it's truly needed. Avoid collecting excessive or irrelevant information.

    2. Secure Forms/Methods: Use secure methods for collecting client data (e.g., encrypted online forms, secure file transfer portals).  

    3. Designated Storage: Store client and company data in designated, secure locations (e.g., secure cloud storage, encrypted internal servers). Clearly define where different types of data should be stored.

    4. Access Logs: Maintain logs of who accessed sensitive data and when, where feasible.  

B. Data Usage and Sharing:

  • Guideline: Use client data only for the agreed-upon purposes and share it only with authorized individuals or entities.

  • Procedure:

    1. Purpose Limitation: Only process client data for the specific purposes outlined in the client agreement.

    2. Controlled Sharing: When sharing client data with third parties (e.g., subcontractors), ensure there are appropriate contractual agreements in place regarding data protection. Use secure methods for sharing (e.g., secure file sharing links with passwords and expiration dates).  

    3. "Need to Know" Basis: Only share data with internal team members who have a legitimate "need to know" for their work.

    4. Avoid Personal Email: Prohibit the use of personal email accounts for sending or receiving sensitive company or client data.

C. Data Retention and Disposal:

  • Guideline: Retain data only for as long as necessary for business or legal reasons and dispose of it securely when no longer needed.  

  • Procedure:

    1. Retention Policy: Develop a clear data retention policy that outlines how long different types of data should be kept. Consider legal, regulatory, and business requirements.  

    2. Secure Disposal (Digital): When deleting digital data, ensure it is securely wiped or destroyed, not just moved to the recycle bin. Use data wiping tools for sensitive information.  

    3. Secure Disposal (Physical): Shred physical documents containing sensitive information before disposal.  

III. Incident Response Basics:

  • Guideline: Have a basic plan in place for how to respond if a security incident occurs.

  • Procedure:

    1. Reporting: Establish a clear process for employees to report any suspected security incidents (e.g., suspicious emails, lost devices, potential data breaches) to a designated person (e.g., the owner or a designated point of contact).  

    2. Containment: The designated person will take immediate steps to contain the incident and prevent further damage (e.g., isolating an infected device, changing compromised passwords).

    3. Notification: Determine when and how clients and relevant authorities need to be notified in case of a data breach, as required by law or contract.

    4. Documentation: Document all security incidents, the steps taken to address them, and any lessons learned.  

IV. Training and Awareness:

  • Guideline: Regularly educate employees on these security practices and data handling procedures.

  • Procedure:

    1. Initial Training: Provide security awareness training to all new employees during onboarding.  

    2. Ongoing Reminders: Regularly communicate key security reminders and updates through emails or brief meetings.

    3. Phishing Awareness: Conduct periodic simulated phishing exercises to help employees identify and avoid malicious emails.  

Key Considerations for a Small Firm:

  • Keep it Simple: The procedures should be easy to understand and follow without requiring extensive technical knowledge.

  • Assign Responsibility: Clearly designate who is responsible for implementing and overseeing each aspect of these guidelines.

  • Regular Review: Review and update these guidelines and procedures at least annually or as needed based on changes in technology, threats, or client requirements.  

  • Focus on Culture: Foster a security-conscious culture where everyone understands the importance of protecting data and knows their role in maintaining security.

EC4Labs.io

720-272-5688

1800 Wazee Street
Suite 300 
Denver, CO 80202

  • LinkedIn

©2021 by EC4Labs.io. 

bottom of page