NextFin

CyberArk Leverages Amazon Bedrock and Apache Iceberg to Quadruple Support Productivity via AI-Driven Log Automation

Summarized by NextFin AI
  • CyberArk has achieved a 4x increase in engineer productivity through the integration of Amazon Bedrock’s generative AI and Apache Iceberg’s open table format, significantly reducing support case resolution times.
  • Simple support cases now take under 30 minutes to resolve, while complex investigations have been reduced from 15 days to just a few hours, showcasing a major efficiency gain in the cybersecurity sector.
  • The transition to Apache Iceberg allows for immediate data queryability in Amazon Athena, enhancing data management and cost-effectiveness as customer data volumes grow.
  • CyberArk’s implementation of autonomous AI Agents marks a shift in root cause analysis, enabling engineers to handle more cases daily and decoupling business growth from headcount increases.

NextFin News - In a significant leap for AI-driven enterprise operations, identity security leader CyberArk has successfully overhauled its technical support infrastructure, achieving a 4x increase in engineer productivity. According to Amazon Web Services (AWS), the transformation was made possible through the strategic integration of Amazon Bedrock’s generative AI capabilities and Apache Iceberg’s open table format. As of February 18, 2026, the company reports that simple support cases which previously required up to six hours of manual labor are now resolved in under 30 minutes, while complex investigations have seen timelines collapse from 15 days to just a few hours.

The initiative, spearheaded by CyberArk Software Engineer Moshiko Ben Abu, addressed a chronic bottleneck in the cybersecurity industry: the fragmentation of customer log data. Support engineers often spend the majority of their time not on diagnosis, but on the manual ingestion and formatting of logs from diverse vendor environments. By deploying a serverless architecture on AWS Fargate, CyberArk now utilizes the Claude 3.7 Sonnet model via Amazon Bedrock to automatically generate "grok" patterns—structured expressions that parse unstructured text. This "zero-touch" log processing allows the system to understand and structure new log formats in minutes, a task that previously took days of custom engineering.

The technical backbone of this efficiency gain lies in the transition to Apache Iceberg. In legacy systems, data availability was often delayed by AWS Glue crawlers that ran as asynchronous batch jobs. Iceberg’s metadata layer eliminates this dependency by tracking table structures and schema changes instantly. According to AWS, this allows data to be queryable in Amazon Athena the moment it is written. Furthermore, the use of PyIceberg has enabled CyberArk to manage these tables within a Python-based serverless environment, bypassing the need for expensive and complex Apache Spark clusters. This architectural simplification ensures that as customer data volumes scale, the infrastructure remains cost-effective and responsive.

Beyond data ingestion, the implementation of autonomous AI Agents represents a fundamental shift in how root cause analysis is performed. These agents, powered by Bedrock, interact with the data lake and internal knowledge bases to identify event flows and recommend solutions. U.S. President Trump’s administration has frequently emphasized the importance of American leadership in AI and domestic technological efficiency; CyberArk’s move exemplifies how private sector entities are operationalizing these technologies to maintain a competitive edge. By allowing engineers to handle 8 to 12 cases per day—up from a previous average of two to three—the company has effectively decoupled business growth from linear headcount increases.

From an analytical perspective, CyberArk’s success signals a broader industry trend: the move toward "Agentic Data Lakes." The integration of LLMs (Large Language Models) directly into the data pipeline suggests that the value of generative AI is shifting from simple chatbots to deep structural automation. For financial analysts, this represents a significant improvement in operational margins for SaaS providers. By reducing the "Cost to Serve" through 95% faster resolution times, companies can reinvest capital into R&D rather than ballooning support departments. The use of ACID transactions within Iceberg also ensures data integrity, a critical requirement for security firms handling sensitive customer PII (Personally Identifiable Information).

Looking forward, the trajectory for CyberArk involves further automation through Amazon S3 Tables and Bedrock AgentCore. These emerging technologies promise to automate table maintenance—such as compaction and file cleanup—further reducing the manual overhead for data engineers. As AI models like Claude 3.7 continue to evolve in reasoning capabilities, the role of the human support engineer is likely to transition from a data wrangler to a high-level supervisor of autonomous systems. This case study serves as a blueprint for the 2026 enterprise: one where the synergy between open-source data formats and proprietary AI models creates a self-optimizing operational loop.

Explore more exclusive insights at nextfin.ai.

Insights

What are the core technical principles behind CyberArk's log automation?

What historical challenges did CyberArk face in its support infrastructure?

What role does Amazon Bedrock play in CyberArk's AI-driven operations?

How has CyberArk's engineer productivity changed since implementing log automation?

What feedback have users provided regarding CyberArk's new support system?

What trends are emerging in the cybersecurity industry following CyberArk's innovation?

What recent updates have been made to Apache Iceberg that benefit CyberArk?

What potential future advancements could further enhance CyberArk's automation?

What are some challenges faced by CyberArk in implementing AI technologies?

How does CyberArk's approach compare to competitors in the cybersecurity space?

What impact do generative AI models have on the overall cybersecurity landscape?

How has the integration of LLMs changed operational processes in data management?

What are the implications of CyberArk's automation for the future workforce?

How does CyberArk ensure data integrity in its automated systems?

What are the key features of the Claude 3.7 model used by CyberArk?

What lessons can other companies learn from CyberArk's log automation implementation?

What controversies exist around the use of AI in customer support roles?

How does CyberArk's use of serverless architecture impact cost and efficiency?

Search
NextFinNextFin
NextFin.Al
No Noise, only Signal.
Open App