What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Databricks is entering the security-information and event-management market with Lakewatch, an “open, agentic SIEM” built on its lakehouse platform. Announced on March 24, 2026, Lakewatch is designed to collect security, IT, application, and business data; retain it in open formats; and apply analytics and AI agents to detection, investigation, and response.
The important qualification for buyers is availability: Databricks’ announcement described Lakewatch as being in Private Preview. The reviewed material does not establish general availability or public pricing. Lakewatch is therefore best viewed as an emerging SIEM competitor and architectural option—not yet as a proven, turnkey replacement for Splunk, Microsoft Sentinel, or another incumbent.
As an Amazon Associate I earn from qualifying purchases.
What is Databricks Lakewatch?
A SIEM, or security information and event management system, collects and normalizes security events, searches and correlates them, identifies suspicious activity, generates alerts, and supports investigation and response.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallDatabricks describes Lakewatch as an open, agentic SIEM. Those terms describe its central strategy:
#1 Best Overall
- Compact and Efficient Design: The FortiGate 40F is designed for small to mid-sized businesses and enterprise branch offices, featuring a compact, fanless desktop form factor that ensures quiet operation and minimizes space usage.
- Robust Connectivity Options: Equipped with 5 GE RJ45 ports, including 1 WAN port and 4 internal ports, this model provides essential connectivity and flexibility for various network configurations in a small-scale environment.
- High-Performance Security: Offers up to 1 Gbps IPS throughput and 600 Mbps threat protection throughput, using Fortinet’s purpose-built security processor technology to deliver industry-leading performance and protection for SSL encrypted traffic.
- Advanced Threat Protection: Integrated with Fortinet’s AI-powered FortiGuard Labs, the FortiGate 40F offers comprehensive cybersecurity, identifying and mitigating both known and unknown threats to maintain robust security across your network.
- Simplified Management and Deployment: Features a user-friendly management console that provides comprehensive network automation and visibility, coupled with Zero Touch Integration with Fortinet’s Security Fabric for easy deployment.
- Open: security telemetry can be stored in open data formats rather than being confined to a proprietary SIEM database. Databricks says Lakewatch supports the Open Cybersecurity Schema Framework (OCSF), Delta Lake, and Apache Iceberg.
- Agentic: AI agents are intended to assist with ingestion, detection creation, rule tuning, threat hunting, investigation, and response. The available material does not establish that unrestricted autonomous response is available or appropriate for production use.
- Security lakehouse: security data becomes governed enterprise data that can be analyzed alongside identity, application, operational, and business information.
Databricks says Lakewatch uses Unity Catalog for governance and auditability and connects security workflows with capabilities such as Genie and Genie Spaces. These are Databricks product-positioning claims and should not be treated as independent validation of the platform’s operational maturity.
Read Databricks’ Lakewatch announcement.
Why is Databricks moving into cybersecurity?
Databricks already sells a large-scale data and AI platform. Security operations are a logical adjacent market because modern organizations generate enormous volumes of logs from identity systems, endpoints, networks, cloud services, applications, and business systems.
Security teams also need longer historical retention. An old authentication event, cloud change, or endpoint signal may become important only after an incident is discovered. Databricks’ argument is that a lakehouse can retain and analyze this data more flexibly than a system built primarily around proprietary storage and ingestion-based licensing.
Free tools Windows power users keep installed
One-click scans. No signup required.
The company is targeting several persistent SIEM problems:
- Per-gigabyte or per-event ingestion charges.
- The cost of keeping full-fidelity telemetry for long periods.
- Proprietary data models and workflow lock-in.
- Separation between security, IT, application, and business data.
- Difficulty customizing detections and investigations.
- Limited ability to analyze large historical datasets with AI.
- Pressure to discard, sample, or downsample telemetry to control licensing costs.
That is a product-positioning argument, not proof that every incumbent SIEM has the same pricing or architectural limitations. Buyers should compare complete contracts and workloads rather than assume that a lakehouse automatically costs less.
How the Lakewatch architecture is intended to work
The proposed workflow looks like this:
- Ingest: collect security logs, identity events, endpoint data, network telemetry, cloud events, application logs, business data, and potentially other data types.
- Normalize: map events to OCSF or another consistent schema so detections can work across vendors and sources.
- Store: retain raw and processed data in open formats such as Delta Lake or Apache Iceberg.
- Govern: use Unity Catalog and related controls for permissions, fine-grained access, lineage, and auditability.
- Detect: run rules, queries, analytics, machine-learning workflows, and AI-agent processes.
- Investigate: combine natural-language questions with structured threat hunting and historical analysis.
- Respond: send alerts or actions to downstream systems, applications, workflows, or human analysts.
This architecture can be powerful for an organization that wants security data to remain reusable outside the SIEM interface. It can also create more implementation responsibility. A customer may need to design data contracts, handle deduplication and time synchronization, maintain schema mappings, build detection-as-code pipelines, integrate case management, and define retention and legal-hold policies.
Where AI fits—and what remains unproven
Databricks associates Lakewatch with Genie, Genie Spaces, defensive security agents, and custom applications built with Databricks Apps and Lakebase. The announced use cases include:
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →- Assisted or automated log ingestion.
- Detection creation.
- Rule tuning.
- Natural-language threat hunting.
- Multi-step investigation.
- Detection and response assistance.
- Custom security applications.
There is an important difference between asking an AI system to summarize telemetry and allowing an agent to change an account, isolate an endpoint, block a network connection, or modify a production control. The reviewed sources do not establish Lakewatch’s exact model providers, approval gates, prompt protections, permissions model, rollback mechanisms, or evidence-trace behavior.
Controls buyers should require
Any evaluation of agentic security operations should verify whether the product provides:
- Read-only defaults for investigation.
- Human approval before containment or account changes.
- Evidence links and reproducible queries for every finding.
- Protection against prompt injection in untrusted logs and telemetry.
- Secrets isolation and least-privilege tool access.
- Rate limits and blast-radius controls.
- Complete audit logs.
- Rollback procedures.
- Testing against false positives, missed detections, and unsafe actions.
AI cannot compensate for incomplete or badly normalized data. Missing identity context, inconsistent timestamps, duplicate events, incorrect OCSF mappings, retention gaps, and excessive false positives can undermine both conventional detections and AI-assisted investigations.
Rank #2
- HARDWARE PLUS SECURITY SERVICES: FortiGate-60F Firewall Appliance bundled with 1 year of FortiCare Premium and FortiGuard Unified Threat Protection.
- UNIFIED THREAT PROTECTION (UTP): Secures against advanced online threats with comprehensive web filtering and anti-botnet technologies.
- OPTIMIZED FOR MEDIUM-SIZED BUSINESSES: Tailored for businesses needing robust security without the infrastructure of larger enterprises.
- RELIABLE CUSTOMER SUPPORT: FortiCare Premium ensures high-quality support and service continuity.
- EFFECTIVE PROTECTION: Employs advanced filtering technologies to safeguard against sophisticated threats.
Integrations and the announced ecosystem
Databricks’ launch material identified an Open Security Lakehouse ecosystem involving Anvilogic, Arctic Wolf, Cribl, Obsidian, Okta, Palo Alto Networks, 1Password, Panther, Proofpoint, Rearc, Slack, TrendAI, Wiz, Zscaler, and SiftD.ai.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesHowever, a named ecosystem participant is not automatically a generally available connector. It does not prove that an integration is equally deep, bidirectional, supported in every cloud or region, or ready for production. Prospective customers should ask which connectors are available now, who supports them, what data they ingest and export, and whether response actions are supported.
See the announced partner ecosystem.
Databricks-reported performance and cost claims
Databricks conference material describes a reference or production-style implementation that reportedly:
- Ingested 13 TB per day.
- Collected data from 22 sources.
- Achieved detection in under 15 minutes.
- Reported 94% MITRE ATT&CK coverage.
- Claimed up to 80% lower total cost of ownership.
These figures are useful indicators of what Databricks wants prospective customers to evaluate, but they are not independent benchmarks. The 94% figure also measures coverage, not detection precision, recall, response quality, or real-world security outcomes.
“Up to 80% lower TCO” is a best-case company claim, not an expected average. A meaningful comparison would need to identify:
- The incumbent product and contract used as the baseline.
- Daily data volume and retention period.
- Storage, streaming, batch, and query-compute assumptions.
- AI-model and agent usage.
- Migration and detection-content conversion costs.
- Engineering and staffing requirements.
- Whether endpoint, threat intelligence, SOAR, case management, and response costs were included.
- Whether the result was audited or independently reproduced.
A lakehouse may reduce the cost of retaining raw telemetry while increasing platform-engineering and operational costs. Existing Databricks customers may also have a very different incremental business case from organizations adopting Databricks for the first time.
Review Databricks’ reference implementation description.
Lakewatch versus established SIEM platforms
| Criterion | Lakewatch approach | What to compare with incumbents |
|---|---|---|
| Data model | Open formats and OCSF support claimed by Databricks | Proprietary models, open export options, and portability |
| Storage | Lakehouse storage using Delta Lake or Apache Iceberg | Retention economics, searchable history, and data ownership |
| AI | Genie and agentic workflows for detection and investigation | Evidence quality, permissions, approval gates, and model governance |
| Customization | Data engineering, analytics, and custom application tooling | Out-of-the-box detections, playbooks, and workflow flexibility |
| Implementation | Potentially substantial platform and detection engineering | Turnkey deployment and managed content maturity |
| Commercial maturity | Private Preview in the reviewed announcement | Public availability, documented pricing, support, and certifications |
Splunk Enterprise Security
Splunk Enterprise Security is an established option for mature SOCs that value broad content, search, integrations, and established analyst workflows. Buyers concerned about ingestion and retention economics should compare total costs carefully rather than assume either platform is cheaper.
Microsoft Sentinel
Microsoft Sentinel is likely to be particularly attractive in environments standardized on Azure, Entra ID, Defender, and Microsoft’s wider security ecosystem. Its center of gravity is Microsoft-native integration rather than a Databricks-centered lakehouse.
Recommended Free Tools
Google Security Operations
Google Security Operations is another option for organizations seeking an established security-operations platform connected to Google Cloud and Google’s security services. Compare ingestion, retention, analytics, AI, and cloud integration directly.
Rank #3
- 【Up to 1100 Mbps VPN Speed 】 Hardware-accelerated WireGuard and OpenVPN-DCO deliver up to 1100 Mbps VPN throughput, over 3× faster than Brume 2 for smooth remote access and file transfers.
- 【Three 2.5G Ports & Multi-WAN】Tri-port 2.5GbE design with flexible WAN LAN configuration supports multi-gigabit wired setups, dual-ISP Multi-WAN and failover to keep home and SOHO networks online.
- 【Stealth VPN Obfuscation】VPN obfuscation disguises VPN traffic as regular HTTPS, helping you evade blocking, bypass restrictive networks and maintain stable, private connections.
- 【DPI protection】Deep Packet Inspection with visual dashboards blocks adult/gambling/malicious sites, while SQM and QoS prioritize gaming, calls, and video when bandwidth is tight
- 【OpenWrt & USB 3.0 Expansion】OpenWrt with 1GB DDR4 and 8GB eMMC lets you install plugins and build VPN, ad-blocking or NAS, while USB 3.0 Type‑C connects high-speed storage or 4G/5G dongles
Panther and managed detection services
Panther is relevant to buyers evaluating security-lake and detection-engineering approaches, but its relationship to Lakewatch and the depth of any integration should be verified separately.
Organizations that want an operational outcome rather than a platform-building project may prefer a managed detection and response provider such as Arctic Wolf. The trade-off is less control over the underlying data architecture and workflows.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Availability and pricing
Lakewatch was announced on March 24, 2026. The Databricks Community announcement reviewed for this article described it as being in Private Preview. The reviewed material does not establish general availability, a public SKU, a self-service purchase path, or a public Lakewatch price list.
Do not infer Lakewatch pricing from Databricks’ general platform pricing. The underlying platform generally uses usage-based cloud pricing, but Lakewatch-specific economics could involve storage, compute, ingestion, AI usage, support, implementation, and partner services. Only a formal Databricks evaluation or quote can establish the commercial model.
Before signing up for a preview or sales evaluation, ask for:
- Preview scope, production restrictions, and target availability.
- Supported clouds and regions.
- Data-retention and search-cost assumptions.
- Charges for ingestion, storage, compute, AI, and egress.
- Included detection content, threat intelligence, case management, and response integrations.
- Support commitments and service-level terms.
- Compliance certifications and data-residency controls.
- Migration assistance and responsibility for ongoing engineering.
Security data may contain personal, regulated, or sensitive information. Buyers should verify encryption, key management, role- and attribute-based access, audit-log retention, regional processing, third-party model access, and Lakewatch-specific compliance coverage. Databricks notes that security profiles and regional support can vary by feature and geography; Lakewatch-specific coverage was not established in the reviewed sources. See Databricks’ security profile documentation.
Who should evaluate Lakewatch?
Strong fit
- Organizations already invested in Databricks, its governance model, and related cloud infrastructure.
- Enterprises retaining very large volumes of security telemetry.
- Teams that need long-term access to raw events.
- Organizations combining security data with identity, application, operational, or business context.
- Security programs with detection engineers and data-platform expertise.
- Buyers willing to evaluate preview-stage product risk.
Wait or proceed cautiously
- Organizations that need a mature, turnkey SOC platform immediately.
- Teams with limited data-engineering capacity.
- Buyers requiring public pricing, established support terms, or independently documented production maturity.
- Organizations that need proven case management, managed content, and response workflows on day one.
Weak fit
- Small security teams that cannot operate a data-and-detection platform.
- Organizations with no Databricks investment and no reason to adopt its broader platform.
- Buyers seeking a fixed-price security appliance or a single bundled SIEM license.
- Organizations unable to accept uncertain availability, pricing, or integration depth.
Questions to answer in a proof of concept
- Can the platform ingest the organization’s highest-value sources without losing fields or event order?
- How accurately are vendor-specific events mapped to OCSF?
- What is the cost of storing raw and normalized data for the intended retention period?
- What are the real query, streaming, and AI-compute costs?
- How quickly can analysts investigate a known incident using both recent and historical data?
- How many useful detections are available without custom engineering?
- Can every AI conclusion be traced to evidence and reproducible queries?
- What approvals are required before an agent can take action?
- How are prompt injection, malicious log content, secrets, and excessive permissions handled?
- Can alerts, cases, and response actions integrate with existing endpoint, identity, ticketing, SOAR, and messaging systems?
- What happens if a connector, agent, model, or lakehouse workload fails?
- Can the organization export its data, detections, cases, and operational knowledge if it later changes platforms?
The bottom line
Lakewatch is strategically significant because it extends Databricks’ lakehouse and AI capabilities into security operations. Its strongest pitch is not simply a new dashboard or chatbot; it is a different data foundation for SIEM—one that emphasizes open storage, long retention, cross-domain analytics, and customizable AI-assisted workflows.
That approach may be compelling for large Databricks customers with high telemetry volumes and strong engineering teams. It is less compelling as an immediate replacement for a mature SIEM when turnkey content, managed operations, proven integrations, public pricing, and production maturity matter most.
For now, the responsible conclusion is that Lakewatch deserves structured evaluation, not an automatic migration decision. Its long-term credibility will depend on general availability, detection quality, response safety, integration depth, transparent economics, and evidence beyond Databricks’ own launch and conference claims.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
