Reducing Firewall Log Volume by 93% with Kron Telemetry Pipeline
A Tier 1 mobile operator operates at massive scale, where firewalls in data centers and IT systems continuously generate high-volume telemetry streams. In this environment, Fortigate and Palo Alto firewalls were producing millions of log events per day, all forwarded directly into Splunk for analysis. A large portion of these logs were near-duplicates: repeated flows between the same source and destination, with only counters (bytesIn/bytesOut) incrementing. Without preprocessing, the operator had to either absorb the cost or sacrifice visibility. To address this, the operator deployed Kron Telemetry Pipeline as an intermediate processing layer between firewalls and Splunk.
Why SSH Security Matters — And How Kron PAM’s Privileged Session Manager Protects Your Enterprise
Secure Shell (SSH) has long been the backbone of remote administration for Linux/Unix servers and network devices. It replaced Telnet and other insecure protocols with encrypted communication, and today it’s used by virtually every enterprise to connect administrators, developers, and third-party vendors to critical systems. But as much as SSH has become indispensable, it’s also become one of the most exploited gateways for cyber attackers.
Stopping Attacks Before They Start: The Kron PAM Approach to Remote Access Security
Remote work isn’t “new”—but the way attackers get in keeps evolving. The latest numbers show that weaknesses in remote access (VPN appliances, exposed RDP, stolen credentials) continue to be among the most reliable paths to compromise. In 2025, the safest remote access is not a network tunnel—it’s a controlled, auditable, identity-first session that never exposes your environment directly. Kron PAM’s Secure Remote Access was built for this reality: VPN-less, browser-based, JIT, and fully recorded, with strong credential hygiene and data-layer guardrails.
Secure Ansible Automation with Kron PAM Password Vault
Modern DevOps practices heavily rely on automation tools like Ansible to configure systems and deploy applications. However, along with this convenience comes a critical challenge: managing passwords and secrets in automation scripts. Hard-coding credentials (passwords, API keys, etc.) directly in Ansible playbooks or configuration files can lead to severe security issues. In this blog post, we’ll explore the risks of storing secrets in playbooks, review some eye-opening statistics and breaches related to leaked credentials, and then see how Kron PAM and its Password Vault plugin for Ansible provide a secure solution. We’ll also walk through how the Kron PAM Ansible plugin works in practice and highlight the key benefits of integrating Ansible with a robust password vault.
Beyond Passwords: How Kron PAM's MFA Fortifies Your Enterprise Against Modern Threats
Let's be honest. In today's threat landscape, relying on just a username and password to protect your most critical assets is like using a screen door to stop a hurricane. It just doesn't work. Attackers are more sophisticated than ever, and stolen credentials are their golden ticket into your network. The statistics are staggering. According to the 2024 Verizon Data Breach Investigations Report, a whopping 68% of breaches involved a non-malicious human element, which includes things like falling for phishing scams and credential theft. Attackers aren't always hacking in; they're often just logging in with stolen keys. This is where Kron PAM changes the game.
