Download PDF
Data Theorem
Overview
HQ Location
United States
Year Founded
2013
Company Type
Private
Revenue
< $10m
Employees
201 - 1,000
Website
Twitter Handle
Company Description
Data Theorem prevents AppSec data breaches. We provide SAST, DAST, & RASP for API Security, Web Security, Mobile Security, and Cloud Security.
Our products provide Inventory (Discovery), Security Testing (SAST/DAST), and Active Protection (RASP) for APIs (RESTful, GraphQL, gRPC, and SOAP), mobile apps (iOS, Android, React Native, Flutter), Web Apps (Web 2.0 & Single Page Apps), & Cloud Apps + CSPM (Serverless Lambda, Google Cloud Functions, Azure Functions).
Data Theorem is headquartered in Palo Alto, CA., with offices in New York, Chicago, Boston, Paris, and London.
IoT Snapshot
Data Theorem is a provider of Industrial IoT application infrastructure and middleware, cybersecurity and privacy, robots, and analytics and modeling technologies, and also active in the equipment and machinery, finance and insurance, national security and defense, and telecommunications industries.
Technologies
Use Cases
Functional Areas
Industries
Services
Technology Stack
Data Theorem’s Technology Stack maps Data Theorem’s participation in the application infrastructure and middleware, cybersecurity and privacy, robots, and analytics and modeling IoT Technology stack.
-
Devices Layer
-
Edge Layer
-
Cloud Layer
-
Application Layer
-
Supporting Technologies
Technological Capability:
None
Minor
Moderate
Strong
Case Studies.
Case Study
Enhancing Security Through Automated Code Checking: A Case Study on Cisco Duo Security
Duo Security, a part of Cisco, is a leading provider of unified access security and multi-factor authentication delivered through the cloud. Despite being a successful security company, Duo was interested in innovative security solutions that could provide an additional layer of protection to their code. They were particularly intrigued by a technology that could automatically double-check their code and common code libraries quickly and seamlessly. While they had never had a major problem, this “sanity check” sounded like a great idea. However, they insisted on a solution that was well-designed, technically advanced, lightweight, efficient, and did not consume a lot of resources or slow them down. Before Data Theorem, Duo used key materials, checked how things were communicating over the network, and ensured users followed best security practices. They confirmed their code through automated tests, manual checks, etc. but were intrigued by the idea of a third-party 'sanity check', providing an extra layer of protection to ensure nothing is ever missed.
Case Study
Enhancing Mobile Healthcare App Security: A Case Study on Eko Health and Data Theorem
Eko Health, a developer of FDA-approved, AI-powered heart sound and EKG sensors for heart disease monitoring, was in need of a robust, 'always-on' solution to prevent application security data breaches. The company was seeking a vendor to work with on mobile security, as they recognized that current mobile defenses were not keeping pace with new threats. Eko Health was not only looking to get ahead of threats, but also find a solution that is easy to integrate, provides quick results, and is constantly innovating. The team had spent time building their own solutions and exploring open source options, but these efforts were not yielding the desired results. The slow results, cumbersome tasks, and loss of productivity led them to seek a more efficient discovery and autoremediation solution. In 2020, the challenge and demands of managing moving targets in healthcare, as well as reducing re-work for developers led them to Data Theorem.
Case Study
Enhancing Application Security for Cvent with Data Theorem
Cvent, a leading meetings, events, and hospitality management technology provider, was facing challenges with the security of their applications. The applications were created using open-source tools, and the security process was largely manual. This made it difficult for the development team to accelerate their code development and release cycles while ensuring the security of each release in pre-production. Additionally, Cvent was struggling with conducting third-party checks on partners. While compliance checklists and audits were in place, they only captured a snapshot of a partner's commitment to security at a given time. This left Cvent and their partners vulnerable to security incidents from connected devices or phishing emails. Prior to Data Theorem, Cvent relied on penetration testing audits to expose vulnerabilities. However, the high costs and limited coverage of this methodology made it an inadequate solution. Cvent wanted application security to be a critical part of their daily development process.