Infrastructure security
| CONTROL | STATUS |
|---|---|
Unique production database authentication enforcedWe require access to production datastores to use approved, secure authentication mechanisms, such as individually assigned SSH keys. | |
Encryption key access restrictedWe restrict privileged access to encryption keys to authorized users with a business need. | |
Unique account authentication enforcedWe require users to authenticate to systems and applications with unique usernames and passwords or authorized SSH keys. | |
Production application access restrictedAccess to production applications is restricted to authorized users. | |
Access control procedures establishedOur access control policy documents the requirements for creating user accounts, updating user access, and revoking existing access. | |
Production database access restrictedWe restrict privileged access to production databases to authorized users with a business need. | |
Firewall access restrictedWe restrict privileged access to firewall administration to authorized users with a business need. | |
Production OS access restrictedWe restrict privileged access to production operating systems to authorized users with a business need. | |
Production network access restrictedWe restrict privileged access to the production network to authorized users with a business need. | |
Access revoked upon terminationWe use employee offboarding checklists to ensure access is revoked within the timeframes defined in our service-level agreements (SLAs). |
Organizational security
| CONTROL | STATUS |
|---|---|
Production inventory maintainedWe maintain a formal inventory of production system assets. | |
Anti-malware technology utilizedWe deploy anti-malware technology in environments commonly susceptible to malicious attacks. It is installed on all relevant systems and configured for routine updates and logging. | |
Employee background checks performedWe conduct background checks on new employees. | |
Employee code of conduct acknowledged and enforcedWe require employees to acknowledge our code of conduct when they join. Violations are addressed through disciplinary action in accordance with our disciplinary policy. | |
Employee confidentiality agreements signedWe require employees to sign a confidentiality agreement during onboarding. | |
Performance evaluations conductedWe require managers to complete performance evaluations for their direct reports at least annually. | |
Password policy enforcedWe require passwords for in-scope system components to be configured in accordance with our password policy. | |
Mobile device management implementedWe use a mobile device management (MDM) system to centrally manage mobile devices that support MuseWork services. | |
Security awareness training implementedWe require employees to complete security awareness training within 30 days of joining and at least annually thereafter. | |
Visitor procedures enforcedVisitors accessing data centers or secure areas are required to sign in, wear a visitor badge, and be escorted by an authorized employee. |
Product security
| CONTROL | STATUS |
|---|---|
Security control self-assessments conductedWe assess our security controls at least annually to verify that they are implemented and operating effectively. We take corrective action based on the findings and, where a service-level agreement (SLA) has been committed to for a finding, complete the corrective action within that timeframe. | |
Data transmission encryptedWe use secure transmission protocols to encrypt confidential and sensitive data when it is transmitted over public networks. | |
Vulnerability management and system monitoring procedures establishedOur formal IT and engineering policies define the requirements for vulnerability management and system monitoring. | |
Sensitive customer data encrypted at restWe encrypt datastores that hold sensitive customer data at rest. | |
Penetration testing performedWe conduct penetration testing at least annually, develop remediation plans based on the findings, and implement changes to address vulnerabilities within the timeframes defined in our SLAs. |
Internal security procedures
| CONTROL | STATUS |
|---|---|
Business continuity and disaster recovery plans establishedWe maintain business continuity and disaster recovery plans that include communication procedures to preserve information security continuity when key personnel are unavailable. | |
Business continuity and disaster recovery plans testedWe maintain a documented business continuity and disaster recovery (BC/DR) plan and test it at least annually. | |
Configuration management procedures establishedWe use configuration management procedures to ensure system configurations are deployed consistently across our environment. | |
Change management procedures enforcedWe require changes to service software and infrastructure components to be authorized, formally documented, tested, reviewed, and approved before implementation in production. | |
Production deployment access restrictedOnly authorized personnel may deploy changes to the production environment. | |
Systems development lifecycle establishedWe maintain a formal systems development lifecycle (SDLC) methodology governing the development, acquisition, implementation, modification, and maintenance of information systems and related technology requirements, including emergency changes. | |
Board oversight briefings conductedSenior management briefs the company board of directors or a relevant subcommittee on cybersecurity and privacy risks at least annually. The board provides feedback and direction as needed. | |
Board charter documentedThe company board of directors maintains a documented charter defining its oversight responsibilities for internal controls. | |
Board security expertise maintainedThe company board members have the expertise needed to oversee the design, implementation, and operation of information security controls. The board engages external information security experts and consultants as needed. | |
Board meetings conductedThe company board of directors meets at least annually, maintains formal meeting minutes, and includes directors who are independent of the company. |
Data and privacy
| CONTROL | STATUS |
|---|---|
Data retention and disposal procedures establishedWe maintain formal retention and disposal procedures to guide the secure retention and disposal of company and customer data. | |
Data classification policy establishedOur data classification policy guides the protection of confidential data and restricts access to authorized personnel. | |
Customer data deleted upon leavingWhen customers leave the service, we purge or remove customer data containing confidential information from the application environment in accordance with best practices. |