Security Overview
Last Updated: September 10, 2021
1. Scope
- (a) Attributy's Terms of Service; or
- (b) a similar written agreement between Attributy and Customer for Customer's use of the Services (each, the 'Agreement').
'Services' and 'Attributy Services' will each have the meaning given to it in the Data Protection Addendum ('Data Protection Addendum'). Any capitalized term used but not defined in this Security Overview will have the meaning given to it in either the Agreement or the Data Protection Addendum.
2. Purpose
This Security Overview describes Attributy's:
- security program,
- security certifications, and
- technical and organizational security controls
to protect:
- (a) Customer Data from unauthorized use, access, disclosure, or theft; and
- (b) the Services.
In addition to this Security Overview, Attributy's technical security documentation for the Attributy APIs is available at https://Attributy.com/security-overview.
As security threats shift and evolve, Attributy continues to update its security program and strategy to help protect Customer Data and Services. Attributy reserves the right to update this Security Overview from time to time; however, any update will not materially reduce the overall protections outlined in this Security Overview.
The then-current terms of this Security Overview are available at https://attributy.com/security-overview.
This Security Overview does not apply to any Beta Offerings or communications services provided by telecommunications providers.
3. Security Organization and Program
Attributy maintains a risk-based assessment security program. The framework for Attributy's security program includes administrative, organizational, technical, and physical safeguards reasonably designed to protect the Services and confidentiality, integrity, and availability of Customer Data.
Attributy's security program is intended to be appropriate to the nature of the Services and the size and complexity of Attributy's business operations.
Attributy’s Information Security team manages Attributy's security program. They facilitate and support independent audits and assessments performed by third parties.
It includes programs covering:
- Policies and Procedures
- Asset Management
- Access Management
- Cryptography
- Physical Security
- Operations Security
- Communications Security
- Business Continuity Security
- People Security
- Product Security
- Cloud and Network Infrastructure Security
- Security Compliance
- Third-Party Security
- Vulnerability Management
- Security Monitoring and Incident Response
Security is managed at the highest levels of the company, with Attributy's Chief Trust and Security Officer meeting with executive management regularly to discuss issues and coordinate company-wide security initiatives.
Information security policies and standards are reviewed and approved by Management at least annually and are made available to all Attributy employees for their reference.
4. Confidentiality
Attributy has controls in place to maintain the confidentiality of Customer Data in accordance with the Agreement. All Attributy employees and contract personnel are bound by Attributy's internal policies regarding maintaining the confidentiality of Customer Data and are contractually obligated to comply with these obligations.
5. People Security
5.2 Employee Training
6. Third-Party Vendor Management
6.2 Vendor Agreements. Attributy enters into written agreements with all of its vendors, including confidentiality, privacy, and security obligations that provide an appropriate level of protection for Customer Data that these vendors may process.
7. Architecture and Data Segregation
7.2 Attributy Services IBM. The attribution for the cloud communication platform for the Attributy Services is calculated in a Machine Learning Server by IBM Cloud ("IBM"). The IBM data center infrastructure used in providing the Attributy Services is located in the United States. Additional information about the security provided by IBM is available at IBM Cloud Security. Attributy's production environment within IBM, where Customer Data and the Attributy Services are calculated, is a logically isolated Virtual Private Cloud (VPC).
7.3 Services. All network access between production hosts is restricted for the Services, using firewalls to allow only authorized services to interact in the production network. Firewalls are in use to manage network segregation between different security zones in the production and corporate environments. Firewall rules are reviewed regularly. Attributy separates Customer Data using logical identifiers, which tag Customer Data with a unique customer identifier that is assigned to Customer to identify ownership. The Attributy APIs are designed and built to identify and allow access only to and from these tags. These controls prevent other customers from having access to Customer Data.
8. Physical Security
In addition, Attributy headquarters and office spaces have a physical security program that manages visitors, building entrances, CCTVs (closed-circuit televisions), and overall office security. All employees, contractors, and visitors are required to wear identification badges.
9. Security by Design
(a) internal security reviews before new Services are deployed;
(b) penetration tests performed on new Services by independent third parties; and
(c) threat models for new Services to detect any potential security threats and vulnerabilities.
10. Access Controls
In order to access the production environment, an authorized user must have a unique username and password, multifactor authentication, or be connected to Attributy's Virtual Private Network (VPN). Before an engineer is granted access to the production environment, access must be approved by Management, and the engineer is required to complete internal training for such access, including training on the relevant team's systems.
Attributy logs high-risk actions and changes in the production environment. Attributy leverages automation to identify any deviation from internal technical standards that could indicate anomalous/unauthorized activity.
11. Change Management
All changes, including evaluating the changes in a test environment, are documented using a formal, auditable record system. A rigorous assessment is carried out for all high-risk changes to evaluate their impact on the overall security of the Services. Deployment approval for high-risk changes is required from the correct organizational stakeholders. Plans and procedures are also implemented if a deployed change needs to be rolled back to preserve the security of the Services.
13. Vulnerability Management
14. Penetration Testing
16. Security Incident Management
17. Discovery, Investigation, and Notification of a Security Incident
18. Resilience and Service Continuity
19. Backups and Recovery
CircleCI Security and AWS Security Incident Response Guide.