This document addresses the security implications of a Blink hybrid deployment where the Runner is self-hosted (on-premises), but other aspects of the platform are preformed by the SaaS controller. This document shows how the Blink platform may be incorporated into any cloud environment, while keeping customer’s cloud environment secured.

​
Security principles

Minimal trust methodology Blink has adopted a minimal trust methodology to keep customers as independent as possible from Blink when it comes to their security posture. Blink is designed to serve as an abstraction & automation level over existing SaaS services that are being used by the customers, and by that prevents granting power/trust to Blink to take actions on customer’s behalf. Data security To create a secure environment for users, data security measures in all aspects are taken. Security of data in transit, stored data, secured backups, strict data access principles, cloud security posture etc. have been taken into account during the creation and maintenance of the Blink platform. Role-based access control (RBAC) Blink allows granular RBAC permission management, using roles, permissions, workspaces, groups, and resources. Using Blink’s RBAC, customers are able to import existing permissions of users from their existing SaaS permissions, as well as utilizing different authorization approaches under RBAC within the account.

​
Data security

Blink SaaS data flow diagram
Data in rest Data stored at rest on Blink premise, will always be stored at an encrypted state. When using Blink’s hybrid model, the following data types are stored in Blink SaaS premise:
  • Account metadata
  • User details
  • Automation content
  • Resources names & types
  • Logs of Automation executions
Blink does not store the customers secrets when using hybrid deployment. Credentials are stored using Hashicorp’s vault. Data in transit All in-transit data on the Blink platform and external dependencies, is sent over TLS encrypted networking / industry-standard encryption methodologies. In addition to the data kept at rest on the Blink platform, additional data is forwarded using Blink SaaS to the customer’s utilization through the UI. This data includes:
  • User credentials
  • Users Automations
  • Step outputs

​
Main security measures

Customer identity Any action performed by Blink users is signed by a JWT token. The identity token is generated by an external authentication provider and is validated through the customer’s request. By enforcing the performed action signature, Blink mitigates the risk of Man In Middle and Request forgery attack vectors. Credentials Security (Credentials Jail)
  1. Blink is relying on external credentials in order to allow users to integrate and interact with external SaaS services. To avoid dangers related to credentials, Blink on-prem solution allows the user to keep all credentials usage on-premise. Blink will integrate to the customer’s secret manager. Currently supported secret managers include Hashicorp Vault and AWS Secret Manager.
  2. Usage of credentials on a runner-based system where running code is allowed, imposes the risk of credentials leaking - either by accident or by adversary action. Blink mitigates this risk by applying a Credentials jail - credentials are exposed only to pre-built and acknowledged system actions, rather than being directly exposed to arbitrary usage.
RBAC permissions management Blink allows granular RBAC permission management, using roles, permissions, workspaces, groups, and resources. Using Blink’s RBAC, customers are able to import existing permissions of users from their existing SaaS permissions, as well as utilizing different authorization approaches under RBAC within the account.

​
Additional security measures

Environment Isolation Blink offers two run modes in terms of isolation:
  1. Shared environment - Use the main Blink cloud service, which is shared across multiple accounts. Data is separated by per-tenant separation.
  2. Dedicated SaaS namespace - Network, data flow, data storage and all business logic is completely separated at this mode. Data is separated on a DB per customer basis.
High availability and DDOS protection The entire stack of Blink service is served on a highly available Kubernetes service. All components shown in the data flow diagram are protected by high availability measures, including crash-recovery. Additionally, all services are protected against OWASP and DDOS Backups Data stored on Blink premise is backed up multiple times every day at an encrypted state. Customers may request for their backup data to be deleted, according to GDPR regulations. Audits and logs All metadata for actions performed on an account is kept for a minimal duration of 6 months, and is accessible by customers request.

​
Security & Privacy policies and standards

In addition to the security measures detailed in this document, Blink acts upon the highest industry standards on security topics. Blink can provide documentation related to these topics at the customer’s request. These topics include the following:
  1. Compliance
  2. Password management
  3. Permission access management
  4. Privacy policy
  5. Risk assessment
  6. Third-party vendor management
  7. Key management and information security
  8. Incident response
  9. Auditing
  10. Environment security
  11. Data retention and erasure
  12. Backup policy
  13. Endpoint security