Skip to content
BLOG CONTACT US
PRODUCT
ENDPOINTS SERVERS
 NETWORK
DEVICES PLATFORM &
INTEGRATIONS
SOLUTIONS
IDENTIFY VERIFY FORTIFY ZERO TRUST SUPPLY CHAIN DEVICE HEALTH REMOTE WORK HIGH-RISK
TRAVEL
RESOURCES
KNOW YOUR
OWN DEVICE THREAT REPORT SOLUTION BRIEFS PRODUCT BRIEFS WHITE PAPERS VIDEOS BEST PRACTICES
COMPANY
EVENTS NEWS ROOM PRESS RELEASES CAREERS CONTACT US
REQUEST A DEMO
REQUEST A DEMO
BLOG CONTACT US
PRODUCT
ENDPOINTS SERVERS NETWORK
DEVICES PLATFORM &
INTEGRATIONS


SOLUTIONS
IDENTIFY VERIFY FORTIFY ZERO TRUST SUPPLY CHAIN DEVICE HEALTH REMOTE WORK HIGH-RISK
TRAVEL

COMPANY
EVENTS NEWS ROOM PRESS RELEASES CAREERS CONTACT US

RESOURCES
KNOW YOUR
OWN DEVICE THREAT REPORT SOLUTION BRIEFS PRODUCT BRIEFS WHITE PAPERS VIDEOS BEST PRACTICES

Blog


Our take on the pressing issues of firmware and hardware security, including the latest threat research, best practices and industry developments.

Everyone Gets a Rootkit
From 33% to 69% …. Does it Matter?
Zero Trust is a critical strategy for defending our ever-growing digital attack surfaces. But Zero Trust Architecture is incomplete without device firmware and hardware verification. While adding context-aware checks on user activities does help, it cannot account for the many functions that occur inside a device, below the operating system. Three simple checks on device integrity can pave the way in this regard. Here are some examples: Add device vulnerability and firmware patch level risk to network access control. Access from an at-risk device has a long tail of impact. Once data is processed by the device, firmware attacks that happen later may bypass controls like encryption or security software that might have otherwise protected critical resources. Before enabling a device to affect mission-critical assets, check for vulnerabilities and updates. Extend context-aware access control to include device behaviors. Just like access patterns can reveal risky user activity, devices have common behavior profiles, and anomalies can reveal low-level tampering or installation of malicious firmware. Inventory components inside a device in order to enable revocation based on component properties if needed. The ability to revoke access to online sessions or offline data should extend to the device itself. If future events reveal backdoors or serious supply chain concerns, a component level inventory will help quantify exposure and enable quick and decisive action if it becomes necessary. A simple Eclypsium scan collects the information needed for these actions and more. Connect with us to discuss what might be appropriate for your environment
Three Steps to Complete Your Zero Trust Architectu …
Eclypsium Detects Severe Vulns in Accellion FTA Devices
Eclypsium Detects Severe Vulns in Accellion FTA De …
NIST Kicks the Can Feature Image
NIST Kicks the Can: Why We Need to Address Firmwar …
Feature Image Dell BIOSDisconnect
Eclypsium Discovers Multiple Vulnerabilities Affec …
Feature Image You Can't Unsee the Rabbit
You Can’t Unsee the Rabbit: Perspectives on the …
Network Unmanaged Devices Feature Image
Extending Visibility and Security to Network and U …
What to ask when auditing firmware security compliance
What to Ask When Auditing Firmware Security
Boothole How It Started How It's Going
BootHole: How It Started, How It’s Going
A Secure Supply Chain Requires Independent Visibility Into Firmware Feature Image
A Secure Supply Chain Requires Independent Visibil …
In the Shadow of Sunburst: Hunting for Firmware Persistence in the Context of Supply Chain Attack IR
In the Shadow of Sunburst: Hunting for Firmware Pe …
1 2 3 … 6 Next >

Back to Top
Subscribe to Below the Surface
A firmware and hardware threat report from our research team.
Privacy Policy

© Eclypsium, Inc.