11:00 AM
Dark Reading
Dark Reading
Products and Releases

Domo BYOK Gives Organizations Full Data Control to Accelerate Cloud Adoption

SILICON SLOPES, Utah ­ September 12, 2017 -- ­ Domo today announced Domo BYOK, the first Bring Your Own Key (BYOK) enterprise software solution for cloud analytics and business intelligence. With Domo BYOK, organizations of all sizes can benefit from the agility of cloud computing with robust enterprise security, and trust programs and protocols in place. Domo BYOK builds on Domo¹s existing security, compliance and privacy protocols to meet the security needs of its customers, particularly those in highly regulated industries, providing customers with full control of their data encryption.

Domo BYOK embraces a security partnership model, which puts customers in the co-pilot chair as the data controller of their own unique instance while Domo acts as the data processor. Through this customer-controlled encryption, organizations can revoke the encryption key at any time, nullifying all data in the Domo Business Cloud and making it so that no one will have access to sensitive data.

³For highly regulated industries like financial services, health care and government, secure, real-time access to data is crucial. It¹s been one of the biggest deterrents in migrating data to the cloud for regulated industries,² said Niall Browne, CISO, senior vice president of security and trust at Domo. ³With Domo BYOK, we¹re significantly reducing the concern of companies in these industries by giving them full transparency and complete access to their encryption keys. Domo is opening up the possibilities for companies to truly harness the power of their own data.²

Enterprise companies¹ No. 1 security request is to manage their own encryption keys. Domo BYOK is designed for each customer to manage its own cloud instance in accordance with internal security and compliance requirements, so Domo becomes a secure extension of the customer¹s internal network. Domo BYOK breaks new ground for BYOK solutions by assigning a unique key, which can currently be rotated every hour and also allowing customers to remotely delete any residual data in memory. Important capabilities of Domo BYOK include:

  • Key Management ­ Domo¹s key management service creates keys based on a per time model. For example, a new key can be automatically generated every hour. Therefore, if any one key is compromised, an intruder will not have widespread data access. In this model, thousands of keys can be created annually, making data more secure.
  • Kill Switch ­ Domo has built a kill switch directly into the customer¹s interface, so when time is of the essence, there is no need to contact Domo to execute the kill switch. Two authorized administrators can execute the kill switch by logging into their instance separately, activating the kill switch, and rendering data in caches and indexes unusable in seconds. Instantly, the data is dropped and the customer¹s activity logs record the event.
  • Event Logging ­ Domo automatically logs and records all activity within a customer¹s instance, giving admins the ability to see how their data is being accessed at all times. If a customer chooses to revoke its encryption keys and execute the kill switch, this event is also logged so the organization has immediate confirmation that its data is no longer accessible.

Domo BYOK offers customers extensive, self-service security features that allow them to stay in control and have full transparency into their data at all times. Additional security features of the platform include SAML-based SSO, multi-factor authentication, security profiles, ability to set policy permissions on individual datasets and full encryption key management authority.

³Our reports clearly show that migration into the cloud is accelerating. In a few years, a corporate Œno-cloud¹ policy will be as rare as a Œno-internet¹ policy,² said David Monahan, managing research director at Enterprise Management Associates. ³Domo¹s BYOK [Bring Your Own Key] is its latest innovation to tear down one of the last barriers deterring companies from adopting the cloud: robust, flexible customer-owned encryption key management. Domo BYOK facilitates highly regulated industries adopting Domo Cloud by providing the customer full control of data encryption and access. The customer decides what needs to be encrypted and who has access at any given time. For many of them, it offers a first opportunity to use sensitive data in the cloud to improve business results and drive data-driven insights.²

For more information about Domo BYOK, visit:

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
'Hidden Tunnels' Help Hackers Launch Financial Services Attacks
Kelly Sheridan, Staff Editor, Dark Reading,  6/20/2018
Inside a SamSam Ransomware Attack
Ajit Sancheti, CEO and Co-Founder, Preempt,  6/20/2018
Tesla Employee Steals, Sabotages Company Data
Jai Vijayan, Freelance writer,  6/19/2018
Register for Dark Reading Newsletters
White Papers
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2018-06-25
The API service on Google Home and Chromecast devices before mid-July 2018 does not prevent DNS rebinding attacks from reading the scan_results JSON data, which allows remote attackers to determine the physical location of most web browsers by leveraging the presence of one of these devices on its l...
PUBLISHED: 2018-06-24
DIGISOL DG-BR4000NG devices have XSS via the SSID (it is validated only on the client side).
PUBLISHED: 2018-06-24
DIGISOL DG-BR4000NG devices have a Buffer Overflow via a long Authorization HTTP header.
PUBLISHED: 2018-06-24
An issue was discovered in the Linux kernel through 4.17.2. The filter parsing in kernel/trace/trace_events_filter.c could be called with no filter, which is an N=0 case when it expected at least one line to have been read, thus making the N-1 index invalid. This allows attackers to cause a denial o...
PUBLISHED: 2018-06-24
GIMP through 2.10.2 makes g_get_tmp_dir calls to establish temporary filenames, which may result in a filename that already exists, as demonstrated by the gimp_write_and_read_file function in app/tests/test-xcf.c. This might be leveraged by attackers to overwrite files or read file content that was ...