SOC 2 Compliance
Logz.io – The only SOC II Compliant ELK Platform
Data security is more important now than ever before
Leveraging a multi-layered approach, Logz.io has a SOC team that handles security matters as well as security architects who define and implement security protocols, procedures, team education and enforcement
SOC 2 Compliance Certifications
Logz.io is SOC 2-compliant. According to the American Institute of CPAs (AICPA), a SOC 2 report is ideal for SaaS and cloud service organizations that want to assure customers that their information is secure and will be available whenever needed. A SOC 2 report also helps organizations to establish the effectiveness of any controls that may be required by their governance process.
How Logz.io Secures Customer Log Data
Confidence is needed when relying on third-party vendors to manage and handle online data and log files securely. Therefore, the need exists for a solution that protects the integrity of your data, in its entirety, around the clock.
Built by enterprise security veterans hailing from firewall innovator Check Point Software, Logz.io goes above and beyond to support and protect its customers’ secure environments with log management and analysis. This white paper delves into how the company developed an innovative microservices architecture to integrate best-of-breed technology with meticulous organizational processes and a human touch for online service security.
First, Logz.io’s culture and internal development, operations, and DevOps processes themselves have been constructed to provide maximum data security. Second, from network and cloud instance logical security to physical data center security, the company is able to secure services, data, and access. Finally, they have instilled five key underlying features in their architecture from the very beginning.
Logz.io successfully completed the Service Organization Controls (SOC 2) certification audited by E&Y, making the company the only cloud enterprise ELK provider to reach that compliance standard.
“Dyn is a fast-growing company that puts the highest priority on security and compliance. We chose Logz.io because of its dedication to security, as demonstrated by their SOC 2 compliance. The Logz.io log analytics solution enables us to scale our business effortlessly, and we leverage it today for multiple uses ranging from compliance to development to operations.”
The company has taken ELK, the world’s most popular open source log analytics platform, and for the first time enables enterprises to leverage it in a strategic way by offering enterprise-grade features and completing the necessary compliance certifications. Until now, enterprises had only limited use of ELK due to functionality and security considerations.
A SOC 2 report, which was also completed by other established companies including Amazon Web Services and Rackspace, certifies the controls that a SaaS provider has in place in terms of security, availability, processing integrity, confidentiality, and privacy. SOC 2 is the standard for securing information in the cloud. For the first time, enterprise IT organizations can now analyze their infrastructures using open source ELK as a cloud service with a SOC 2 level of compliance through the Logz.io platform.
Logz.io’s Security Measures
1. Internal R&D Processes
Security-oriented environments start with high coding standards that guard against attempted security breaches and are accompanied by rigorous code reviews and tests (such as code coverage testing). Logz.io employs the strictest development processes and coding standards to ensure that both adhere to the best security practices. In addition, the company’s testing platform performs a set of various black box and white box tests for quality assurance (including ongoing penetration tests). R&D processes are implemented and supported with security as a top priority across all system layers, from the physical layers up to the application layer.
2. Physical Data Center Security
Logz.io relies on the Amazon cloud’s exceptionally flexible and secure cloud infrastructure to store data logically across multiple AWS cloud regions and availability zones. AWS makes abiding by industry and government requirements simple and ensures the utmost in data security and protection. For example, AWS infrastructure aligns with IT security best practices and follows a number of compliance standards such as:
- SOC 1/SSAE
- 16/ISAE 3402 (formerly SAS 70 Type II)
- SOC 2
- SOC 3
All data centers that run Logz.io’s platform are secured and monitored 24/7, and physical access to AWS facilities is strictly limited to select AWS cloud staff. (For more information about AWS’ secure architecture and compliance certifications, visit: http://aws.amazon.com/security.)
3. Instance and Network Security
Every microservice runs inside a well-defined Docker container that allows specific levels of access to select controllers. Logz.io uses Docker to avoid erroneous instance-configuration changes, upgrades, and corruption that are common sources of security breaches. Additionally, the company hardens operating systems within containers to enable various network access controls (such as iptables).
Logz.io takes all necessary precautions to ensure that every layer involved in data transfer is secured by best-of-breed technologies. The company’s network is segmented using AWS security groups, VPCs, ACLs, and additional custom measures. In addition, their threat-control center is kept up to date with security alerts that are analyzed and addressed in real-time. Through in-depth network monitoring, Logz.io is able to detect anomalies and take a proactive approach to eliminating potential breaches.
4. Customer Data Security
Logz.io secures each and every step of the data funnel by provisioning dedicated data stores for each individual customer, ensuring full data-segregation. Data is tagged, segregated, and tunneled through the company’s data-ingestion system. They mark each specific piece of given customer data according to its associated organization, which is associated with that data throughout its life cycle. When data is in transit in Logz.io’s ingestion pipeline, it is marked with specific information, including its associated customer, so that it can only be accessed by that customer. The company supports SSL encryption for data in transit, so customers can securely upload their data to the Logz.io cloud and securely browse through their own Logz.io console. Cold data is encrypted and hosted in separate Simple Storage Service (S3) buckets, which are secured via durable AES 256-bit encryption.
In addition, Logz.io continuously tracks and maintains the location and state of their customers’ data. That way, when the company retires an operating system, for example, and decommissions the related machine, Logz.io is sure to wipe clean any informational residue that may have been left behind before returning the machine to AWS. Disks are specially formatted to ensure that data recovery is not possible at a later point in time.
5. Access Management
Logz.io supports role-based access through their interface, allowing end users to be defined as admins or users as well as suspended or deleted. Customers’ account administrators manage and control user access, including provisioning new end users with a defined access level.
To verify adherence with compliance policies, Logz.io uses 3rd-party auditing services. E&Y, one of the “Big Four” auditing firms, performs periodic and comprehensive auditing to audit and validate processes.
To further emphasize the points mentioned above, data security is more important now than ever before. Logz.io is able to achieve higher privacy and security levels than most organizations. As a result of understanding the sensitivity of their customers’ log data, the company has built and continues to maintain their system with enterprise-grade security in mind. Leveraging a multi-layered approach, Logz.io has a SOC team that handles security matters as well as security architects who define and implement security protocols, procedures, team education and enforcement. Logz.io puts application and data security first.
Please feel free to contact the security team at Logz.io with any questions, suggestions or concerns about any of the points outlined above at: email@example.com.
Turn machine data into actionable insights with ELK as a Service
Join us at our next Boston ELK (Elasticsearch) meetup to learn how to create your perfect Kibana dashboard!