General information

• Provider: senhasegura Cloud powered by Google Cloud (GCP);
• One Virtual Private Cloud¹ per customer;
• Compliance with Safe Harbor and data protection laws;
• SLA 99,5%;
• Support 24x7 or 8x5;
• Support policy

¹Virtual Private Cloud - means that the data of different clients will be 100% segregated within the environment, not at risk of configuration errors, data leakage, or impact from one client to another.

Product

All senhasegura modules² on-premises are also available on private SaaS.

The product offered in both modalities is precisely the same, only changing the means of sale and distribution. So all functionalities and integrations are available.

²Only physical appliances and load balancers are not available.

Administrator Console

Administrators can only access senhasegura throw the web application over an encrypted tunnel. In this area is possible to configure users, groups, access policies, etc.

Unlike the on-premises version, customers neither have access to the Orbit session nor the server.

Data collection

The following information is the only NPI (non-public information) and PII (personally identifiable information) that senhasegura SaaS collects to provide the service:

• Devices: computer name, computer MAC address, usernames and groups, currently logged in user, endpoint IP addresses, IP address from which the endpoint connected to the SaaS, programs installed and applications started (from per policies), screenshot videos of sessions;

• Users: Full name, SaaS username, password, and email address.

info

User data can be anonymized by administrators directly in the senhasegura web interface to guarantee the right to be forgotten.

Backup

Daily snapshot (3h GMT-3)

• Fast recovery (last five days) - maximum 4 hours to restore
• Long term recovery - Optional - maximum 8 hours to restore

info

Retention is based on the contracted package's disk space. It will vary according to application usage.

Performing snapshots, updating, and restoring in case of unavailability is the responsibility of senhasegura. If the customer intends to store the backup, videos, and application credentials locally, it will be their full responsibility regarding security measures, access control, and disk space.

Data extraction

Client credentials are backed up with each password change and saved to your network to ensure the latest version is always available locally. Customers can also perform local backups of session recordings automatically or access senhasegura and extract them individually.

Attention

After extraction, the customer is fully responsible for the security-related data and its lifecycle.

Break Glass

All copies of the credentials file are saved on the customer's network for the "break glass" procedure.

Remote access support

The senhasegura team will only access the application and server through the customer's network. Each access is logged for auditing.

Monitoring

24x7 infrastructure monitoring carried out by the senhasegura team; Customers are responsible for monitoring the VPN connection on their side; - If applicable.

Data security and privacy

The cloud environment in which senhasegura runs is protected by a threat detection service that continuously monitors malicious activity and unauthorized behavior.

Data retention policy

the server will trigger the data delete procedure in one of the following scenarios: Automatically three months after the contract expiration or non-renewal date. Upon request of a specific ticket from a customer to senhasegura for data deletion. For the first scenario, the instance will be retired, and the snapshots will be stored for three months.

Important

If requested by the customer, this deletion process is recorded for later auditing.

Notifications about the deletion procedure:

• Inform that the instance has been deactivated;
• Inform that the data has been completed and deleted.

Deletion timeline

The senhasegura cloud is developed by Google. Therefore it has its exclusion policy. Google Cloud is designed to achieve a high degree of speed, availability, durability, and consistency, and the design of systems that are optimized for these performance requirements must be carefully balanced against the need to achieve data deletion properly. Google Cloud commits to deleting Customer Data within approximately six months (180 days). This commitment incorporates stages of Google's opt-out pipeline, including:

• Once the deletion request is made, the data is usually marked for deletion immediately, and the aim is to complete this step within a maximum period of 24 hours. Once the data is marked for deletion, an internal recovery period of up to 30 days may apply, depending on the service or deletion request.
• The time required to complete garbage collection tasks and achieve logical deletion of active systems. These processes can occur immediately after receiving the delete request, depending on the level of data replication and the timing of garbage collection cycles in progress. From delete requests, it usually takes about two months to delete data from live systems, which is typically enough time to complete two major garbage collection cycles and ensure the logical deletion completes.
• Google's backup cycle is designed to expire deleted data in data center backups within six months of the deletion request. Deletion may occur sooner depending on the level of data replication and the length of Google's ongoing backup cycles. For more details on Google's delete pipeline: Data Deletion on Google Cloud