Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

teleport

DevOps Credential Hygiene: How to Eliminate CI/CD Secrets with Teleport

Dec 22, 2025 By Meina Ghafouri In Teleport
Static credential practices — where certificates, keys, and tokens persist for months or years and are manually rotated — create systemic risk in DevOps pipelines. Rotating these secrets is time-consuming and costly. In fact, organizations may spend dozens of hours and involve multiple teams to rotate a single credential. Manual rotation quickly becomes impractical across thousands of service accounts. In this post, you will learn.
Read Post
datadog

Detect and block exposed credentials with Datadog Secret Scanning

Dec 1, 2025 By Michelle Sun In Datadog
Securing secrets is a difficult task. Developers frequently hardcode credentials for quick testing or use AI-generated code snippets that include live API keys or tokens. This means that enterprise secrets can inadvertently make their way into repositories and pipelines, exposing organizations to security and compliance risks without anyone noticing. When a secret is committed to a repository, it spreads quickly across branches, becomes difficult to track, and leads to leaks that are hard to clean up.
Read Post
keeper

Top Secrets Management Tools in 2026

Nov 12, 2025 By Ashley D'Andrea In Keeper
Organizations rely on a combination of internal systems and cloud services to run their business, all of which require sensitive credentials, such as API keys, SSH keys, database passwords, tokens and certificates. Secrets management refers to the storing, organizing and managing of these credentials to prevent unauthorized access.
Read Post
Featured Post
The Shift Left of Boom: Making Cyber Threat Prevention Practical Again

The Shift Left of Boom: Making Cyber Threat Prevention Practical Again

Nov 5, 2025 By John Dominguez, Senior Director of Product Marketing In Reach Security
The old saying "prevention is better than cure" has lost currency in today's cybersecurity industry. Instead, security teams are advised to assume that the business has been breached and focus on threat detection, investigation, response, and recovery. Yet, during cyber incident post-mortems, it is not uncommon to find that the business owned the tool that would have protected it against the breach. The problem arose because it wasn't correctly configured before the incident happened, and no one knew this - or if they did, they didn't have the time or resources to fix it.
Read Post

Copyright © 2026 OpsMatters™. All rights reserved.