Whistle Security Controls & Operational Procedures Master Technical Operations & BYOD Policy Framework

Classification: Internal Use Only

Whistle Security Standard

Target Audience: All Personnel & Contractors

‍

1. Identity & Access Controls

The company relies on strict identity validation mechanisms to guard entry to core digital frameworks. Multi-Factor Authentication (MFA) is mandatory across all business profiles.

Google Workspace Identity Layer: All default staff email environments and productivity platforms require active Google 2FA verification to allow access.

‍
Secondary Platform Constraints: Every connected operational system must enforce secondary, independent 2FA parameters before authenticating users. This strictly governs access to:

‍
 - HubSpot (Customer Relationship Management Data)
 - Claude (Internal AI Development Environments)
 - Instantly (Outbound Communications Engine)
 - Slack (Corporate Communication Network)

‍

2. Outbound Email Verification Infrastructure

To shield corporate identity assets, secure our communication lines, and suppress inbound social engineering vectors, the public domain configuration must actively maintain three structural verification layers:

‍

- SPF (Sender Policy Framework): Hardens the system by hosting an authorized directory of verified network servers allowed to send corporate mail.

‍

- DKIM (DomainKeys Identified Mail): Cryptographically signs outgoing communications, allowing destination environments to prove that the email context has not been altered or intercepted in transit.

‍

- DMARC (Domain-based Message Authentication): Establishes strict rules instructing destination email gateways to reject or quarantine unverified traffic mimicking our official domains.

‍

3. Endpoint Protection & Monitoring (BYOD)

The organization operates a secure Bring Your Own Device (BYOD) framework. Personal systems interacting with company digital properties are strictly subject to centralized software auditing:

‍

- Datto EDR (Endpoint Detection & Response): Installed as the main defense shield on all endpoints. It continuously analyzes system behavior, flagging anomalies and automatically blocking active malware threats.

‍

- Atera RMM (Remote Monitoring & Management): Deployed to track operational health, verify machine inventory, perform security logging, and automatically push operating system and software security updates.

‍

4. Employee Control Procedures

Day-to-day operations rely on proactive behavioral rules to complement our software protections:

- Terminal Security locks: Employees must lock their workstation screens immediately when moving away from their desk or workspace.

‍

- Verification Rules: Unexpected, sudden, or urgent operational requests (such as requests to transfer resources or reveal profile secrets) must be verified through a separate, trusted channel before execution.

‍

- Anomaly Reporting: Any suspicious device behavior or potential phishing links must be flagged immediately to management or the security response desk.

‍

5. Offboarding & Verifiable Data Deletion Protocols

The moment an employee, worker, or external contractor is offboarded, the company executes an immediate, multi-phase cleanup protocol to protect system integrity:

‍

Phase | Required Operations

‍1. Revocation | Immediate deactivation of the central Google Workspace account and absolute profile termination across HubSpot, Claude, Instantly, and Slack.

‍
2. Extraction | Complete removal of all company files, cached properties, local document downloads, and work communication records from the user's hardware.

‍
3. Validation | A thorough check to confirm that no corporate info remains on the personal BYOD storage array, ensuring that deleted cloud items are completely cleared.