Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

LevelBlue Partners With Tenable to Deliver Expanded Vulnerability and Exposure Management Capabilities

Periodic vulnerability scans should no longer be an acceptable standard by any security-minded organization. What is needed is the ability for MSSPs to quickly identify and prioritize risks across all client environments. To enable this capability LevelBlue has developed and rolled out LevelBlue Exposure Management for Partners. This solution delivers continuous visibility, meaningful context, and clarity around how risks could impact the business.

Common ecommerce security vulnerabilities and testing strategies

Ecommerce platforms represent one of the most consistently targeted areas of the modern digital estate. They process payment data, store personal information, integrate with logistics and marketing systems, and underpin revenue for many large businesses. The combination of financial value and sensitive data makes ecommerce security vulnerabilities an attractive target for attackers.

Exposure Assessment Platforms Are Here and They're a Big Part of Successful CTEM

Gartner released its 2025 Magic Quadrant for Exposure Assessment Platforms in November 2025. The new categorization detailed in the report is something we view as a natural progression in response to the way enterprise risk has evolved over the years. It’s a move away from viewing vulnerabilities in a vacuum and looking at a more complete picture of the risk today’s enterprises face.

The Risk of Partial Cybersecurity Coverage

Many organisations take a phased approach to deploying password managers, starting with IT and security teams and planning to expand later. This approach is often shaped by practical constraints such as budgets, licensing and the need to balance competing priorities. Partial cybersecurity coverage leaves organisations exposed to breach paths that are actively exploited.

Securing Telehealth and Remote Healthcare With Keeper

Telehealth and remote work have become a major part of modern healthcare delivery. Clinicians, IT teams and third-party providers now access Electronic Health Records (EHRs) and billing platforms from home offices, mobile devices and distributed environments. As a result, healthcare organizations must secure access to Protected Health Information (PHI) beyond traditional on-premises environments.

OCR HIPAA Enforcement: Website Tracking Investigation Patterns

Three million patients. That’s how many had their most sensitive health information silently siphoned from hospital systems and handed to a party that had no authorization to receive it. The year was 2022. And what would become one of the largest unauthorized disclosures of protected health information ever documented didn’t arrive through a ransomware attack, a stolen credential, or a nation-state intrusion. It came from a piece of marketing software doing exactly what it was designed to do.

HIPAA + GDPR for Global Healthcare: Overlapping Requirements and Conflicts

If your organization serves patients in both the United States and the European Union, two regulators, HIPAA and GDPR, are already watching your website. Specifically, what happens in the seconds between a visitor landing on your page and your analytics stack doing its job. In March 2024, OCR mentioned that even unauthenticated website interactions, like a user browsing your oncology content or typing into a symptom checker, can constitute PHI if the visit is for health-related purposes.

CCPA for Mobile Apps: SDK Tracking Risks and Compliance Gaps

In 2024, the California Attorney General established a new standard for mobile app compliance after securing a $500k settlement with Tilting Point Media, owing to misconfigured SDKs in one of their games that led to inadvertent CCPA and COPPA violations. The issue? The misconfigured SDKs silently caused sales and the share of children’s data without parental consent. And despite the company’s argument that the misconfiguration was unintentional, the AG’s response set a precedent.

Per-Agent Guardrails: How to Set Different Policies for Different AI Agents

You’ve deployed five AI agents into your production Kubernetes cluster: a customer support chatbot, a fraud detection agent, a data pipeline processor, a code generation assistant, and an internal summarization bot. Your security team writes one set of guardrails and applies them uniformly. Within a week, you discover the code generation agent needs interpreter access the chatbot should never have.