As users of our own product, we understand how important the security and privacy of your data is. We are committed to providing our customers with a highly secure and reliable environment for its cloud-based application. We have therefore developed a security model that covers all aspects of cloud-based Dive.Management systems.
The security model and controls are based on international protocols and standards and industry best practices, Security techniques- Code of practice for protection of personally identifiable information in public clouds.
As part of the company’s focus on security issues, the company security team performs on a regular basis:
Our systems is hosted on Blacknight infrastructure. They've devoted an entire portion of their site to explaining their security measures and legal statements, which you can find in the following links:
No one other than our developers can access the data of clients and this is only done if it is necessary to solve client-related issues.
Customer data is stored only in the production environment. Developers only have approval to access user data in order to solve client requests, issues or bugs. All logs of SSH connections to our production environment are saved and archived. Attachments in your account are encrypted and delivered on a per-user-access controlled basis.
We know the data you share in Dive.Management is private and confidential. We have strict controls over our employees' access to internal data and we are committed to ensuring that your data is never seen by anyone who should not see it. With that said, the operation of Dive.Management wouldn't be possible without a few members having access to our databases in order to optimize performance and storage. This team is prohibited from using these permissions to view customer data without explicit, written permission from the user.
Any new feature or code that will be implemented into our system starts with an in-depth analysis of security and privacy risks. All code is saved into a git version control repository and evaluated in a test environment before deploying it into our production environment. All code is reviewed by a second developer to ensure code quality.
Security controls at Blacknight data centers are based on standard technologies and follow the industry’s best security practices. The physical security controls are constructed in such a way as to eliminate the effect of single points of failure and retain the resilience of the computing center.
A variety of environmental controls are implemented at the data center facilities.
Firewalls: Applications in the hosting and cloud have firewalls installed to shield them from attack and prevent the loss of valuable customer data. The firewalls are configured to serve as perimeter firewalls to block ports and protocols.
DDoS mitigation: All application access, including direct application access and API access, are protected by a dedicated DDoS mitigation service to ensure high availability at all times, as well as prevent attacks and malicious activities.
Dive.Management ensures the security and privacy of user information by encrypting data on all servers at rest and in transit.
Our systems are designed to ensure data is protected at all times. Specifically, we're using TLS v1.2 with strong ciphers to protect data in transit, and AES-256 to encrypt data at rest. User passwords are hashed and salted with a modern hash function.
Dive.Management’s cloud-based solution is deployed using Blacknight, enabling us to guarantee high security through utilizing a series of high tech, best in the industry solutions that work to ensure the safety of all user data on the Blacknight network.
We work closely with industry leaders in web app and infrastructure security who perform penetration tests and audits of Dive.Management. We monitor our product for security vulnerabilities automatically as the product grows.
Dive.Management monitors servers to retain and analyze a comprehensive view of the security state of its production infrastructure. Dive.Management collects and stores production servers logs for analysis. Logs are stored and indexed in a separate network.
We consistently backup the data of our customers. Critical data is backed up every 5 minutes, and non-critical data on a daily basis. Backups are encrypted and distributed to various locations, where they are retained for 25 days.
To handle security incidents effectively, Dive.Management has constructed incident response and notification procedures. Dive.Management employs an Incident Handling team that responds to security incidents and mitigates risks. The team uses monitoring and tracking tools and performs real-time analysis. Additionally, the team has clear procedures in place for communicating the incidents to any involved party and for handling escalations. Every incident is forwarded to the security team leader for assessment and analysis.The level of severity is a measure of its impact on, or threat to, the operation or integrity of the institution and its information. It determines the priority for handling the incident, who manages the incident, and the timing and extent of the response.
Dive.Management realizes that the malicious activities of an insider could have an impact on the confidentiality, integrity, and availability of all types of data and has therefore formulated policies and procedures concerning the hiring of IT administrators or others with access to important and crucial systems. Dive.Management has also formulated policies and procedures for the ongoing periodic evaluation of IT administrators or others with system access. User permissions are continuously updated and adjusted so when a user's job no longer involves infrastructure management, the user's console access rights are immediately revoked.
In order to help ensure that Dive.Management employees are aligned with the security practices and aware of their duties, Dive.Management conducts multiple information security awareness campaigns. In addition, the security obligations of users and the entity’s security commitments to users are communicated on an annual basis through the company policy and code of conduct document.
Our engineering and operation teams keep their skills up to date regarding security best practices. We have coded many different online systems and are experienced in infrastructure security and systems security.