Opens in a new tab

Security Policy

1. Introduction & Scope

This document describes the security policies of Bright Mountain Technologies, Inc. (“Bright Mountain”) (OTCQB: BMTM) and its operating brands — Big Village, Deep Focus, Brightstream, and Bright Mountain Media — pertaining to our cloud-based, SaaS (Software as a Service) platforms, our client services, and the corporate environment supporting them. Services are hosted by Microsoft Azure and a third-party managed data center providing internally managed infrastructure. Software is licensed on a subscription basis and accessed through a web browser.

We store data on behalf of and for the benefit of our clients, along with a limited amount of account data (names and work email addresses of client users) required to provide access. Bright Mountain employs state-of-the-art security technologies to facilitate confidentiality, application uptime, and business continuity. This policy covers all employees and contractors (“Personnel”) with access to Non-Public Company Information, Customer Confidential Information, or Personally Identifiable Information (PII) on the Services, infrastructure, or any system or facility controlled by Bright Mountain Media. Bright Mountain does not accept Personally Identifiable Information (PII) within customer datasets for use in artificial intelligence (AI) services, to process or train data, or for any other function.

2. Roles & Responsibilities

Security Officer. Bright Mountain’s Global IT Director owns this policy and the Information Security Management System (ISMS), with executive oversight through leadership review.

Security Team. All Personnel are responsible for security commensurate with their role. All Personnel receive security training at onboarding and recurring refresher training. Bright Mountain makes use of third-party managed services partners to supply Managed Detection and Response (MDR).

Our security practices substantially conform to recognized industry standards, including the NIST Cybersecurity Framework, the ISO/IEC 27000 series, and OWASP guidance for application security.

3. Infrastructure & Hosting

Services are hosted by Microsoft Azure and a third-party managed data center providing internally managed infrastructure. Physical and environmental security — access control, surveillance, fire suppression, redundant power and cooling — is provided by Microsoft and our data center provider (Servers.com). Both providers are independently certified (ISO 27001, ISO 27017/27018, SOC 1/2/3).

Production Architecture

Environment isolation. Production is logically isolated from development and test environments using separate subscriptions, virtual networks, and security groups. Deployments to production occur only through the controlled release process (Section 8). No client or production data is used in any development environment.

Network controls. Public exposure is limited to secured service endpoints using modern encryption standards. Network security groups and firewalls restrict traffic to necessary hosts and services. Administrative access requires MFA and occurs through managed identity, not shared credentials.

Monitoring. Continuous (24×7) automated monitoring of infrastructure and applications includes alerting the security, infrastructure, and development teams on anomalies, resource thresholds, and suspected malicious activity.

Patching. Operating system and platform patches are applied on a defined schedule; critical- and high-severity patches within 30 days of vendor release.

4. Application Security

Authentication. Authentication uses single sign-on via SAML 2.0 / OpenID Connect (Microsoft Entra ID, Auth0) across all supported systems. Built-in authentication enforces password complexity, account lockout after repeated failed attempts, session timeout on inactivity, and unique user IDs — no shared accounts.

Passwords. User passwords are based on the NIST 800-63B standard and are not shared. Modern Multifactor Authentication (MFA) is required for all logins.

Authorization. Role-based access control follows a “least privileged access” model. Privileged access requires a separate, dedicated account with additional controls and extended monitoring and alerting on use.

Encryption in transit. All public traffic uses TLS 1.2 or later with certificates issued by a public certification authority.

Encryption at rest. Customer data, including backups, is encrypted at rest using AES-256.

Key management. Encryption keys are managed in Azure Key Vault, stored separately from the systems they protect, rotated on a defined schedule, with all access logged.

Logging. All access to production systems is logged into a centralized, immutable service managed by Microsoft. Logs are retained for a minimum of ninety (90) days and up to one (1) year for critical, sensitive, and privileged access.

Testing. Annual third-party testing is performed on all publicly facing services and internally developed services. Clients may perform application vulnerability scans or penetration tests against a non-production instance with prior coordination. We remediate Critical findings as soon as technically feasible, not to exceed 7 days, and High findings within 30 days.

5. AI Systems Security & Governance

Bright Mountain and its operating brands incorporate AI capabilities into several of our products and services, including our Brightstream platform, Dexter agent, and corporate operations. Controls specific to AI are outlined below:

No training on customer data. Customer data is processed solely at the customer’s direction for the purpose of delivering requested services or outputs. Customer data is not loaded into an AI service without prior written agreement or authorization. Customer data is not used to train, fine-tune, or improve AI models — ours or any third party’s.

AI sub-processor restrictions. All AI providers operate under enterprise agreements that prohibit training on customer data, limit processing to service delivery, and require zero or minimal retention. Public or non-contracted AI providers are not used to deliver services.

Isolation. Customer data submitted to AI features remains logically separated by customer; outputs generated for one customer are never exposed to other customers.

Memory. Customer data may be used to build and enhance customer-specific AI delivery through the use of AI “memory” or predictive data analytics. All memory functions are subject to the same AI controls, are logically separated by customer, and are not used for model training.

Lifecycle governance. Potential new AI capabilities must pass a security and responsible AI review before release. This review covers data flows, sub-processor involvement, and human oversight requirements. The governance structure aligns with ISO/IEC 42001, which Bright Mountain Media is pursuing alongside ISO 27001.

6. Corporate IT Security

Devices. All company laptops enforce full-disk encryption, screen lock, endpoint protection with real-time scanning, and remote wipe. Bring Your Own (BYO) devices accessing company data are subject to the same controls and enforcement as corporate devices before access is granted.

Storage restrictions. Only approved removable media devices are allowed to connect to devices. Personal removable media devices are not allowed. Approved media devices must include modern encryption standards such as AES-256 and are logged in our device management system.

Offices. Bright Mountain is a fully remote company. All access is logically controlled according to this document and our corporate ISMS, and managed by approved third-party hosting providers (Microsoft Azure and Servers.com).

7. Business Continuity & Disaster Recovery

Redundancy. Production services are deployed across Azure availability zones, with no single point of failure by design. Data center hosted services employ geo-located backups and replication according to their tier of service and our BCP Policy and Plans.

Backups. Production data is backed up on a defined schedule according to our data protection policy, is encrypted according to modern standards, and is geographically separated from the production services. Restoration is tested regularly.

Disaster recovery. Bright Mountain’s documented BCP/DR plan defines recovery objectives (Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO)) based on the tier and criticality of the services. DR is tested at least annually using table-top or simulated testing.

8. Secure Development Lifecycle

  • Version-controlled source (Git); all production code passes peer review before merging.
  • Automated static analysis and dependency scanning on the codebase; continuous integration with automated testing.
  • Deployments to production are performed only by authorized release personnel following a documented checklist; all deployed code traces to reviewed source.
  • Production data is not used in development or test environments.

9. Personnel Security

  • All employees and contractors are subject to background checks (subject to local law) and signed confidentiality agreements.
  • Security training is mandatory at onboarding, and recurring refresher training is provided for all Personnel.
  • On termination, access to all systems is disabled immediately, not to exceed twenty-four (24) hours.

10. Third-Party Risk

All vendors with access to Non-Public Company Information or Customer Confidential Information are assessed before onboarding, re-assessed as needed, and must maintain security controls no less protective than our own. AI sub-processors carry additional restrictions (Section 5).

11. Certifications & Attestations

  • SOC 2 Type II: Audited annually by an independent assessor. Platform Services are incorporated into the scope of the 2027 report. Available in the Trust Center under confidentiality acknowledgment.
  • SOC 3: Published for open distribution.
  • ISO 27001 and ISO 42001: Certification programs in progress.
  • Hosting: Microsoft Azure maintains ISO 27001, ISO 20000, ISO 22301, ISO 27017/27018, SOC 1/2/3, PCI DSS, and related certifications, as applicable.

12. Incident Handling & Notification

Security incidents are logged, triaged, and managed under a documented incident response plan with defined roles and escalation paths. “Security Incident” means the loss, destruction, theft, or unauthorized access, use, or disclosure of Customer Confidential Information. We will notify affected customers of a Security Incident within 72 hours of detection, take appropriate corrective action promptly, and reasonably cooperate with customers in remediation.

13. Policy Control

This policy is reviewed and updated at least annually. Bright Mountain may update it as needed to reflect technological change and evolving best practice.

Contact

sirt@brightmountain.ai