Centralized Secret Management: Comparing Eight Tools for DevOps and Spring Boot Applications
The article addresses the growing complexity of handling secrets in modern software development. Passwords for test databases often reside in .env files, API tokens sit in CI variables, and production credentials are distributed through corporate password managers. As teams expand, questions arise about access control, copy proliferation, credential updates, and the consequences of access revocation.
Centralized secret storage provides a single source of truth, environment separation, least-privilege policies, audit logging, and lifecycle management. However, simply storing values does not automatically revoke previously downloaded copies or change passwords in target systems such as PostgreSQL.
The piece defines a secret as any value that grants access to resources or allows actions on behalf of a user or application. Configuration elements like service URLs or port numbers are not secrets and can safely remain in repositories. Spring Boot examples illustrate externalized values using placeholders such as ${SPRING_DATASOURCE_PASSWORD}.
Delivery methods are analyzed in detail. CLI run commands launch child processes with secrets injected into the environment. Agents can template files or supervise processes. SDK integrations allow direct API calls, while export options create .env files that should be avoided in production workflows. Tools offering ready-made run scenarios include Infisical, Doppler, 1Password CLI, and Bitwarden Secrets Manager.
Authentication considerations stress the importance of distinct identities for humans and machines. Issuing a single long-lived token to an entire team undermines auditability and revocation capabilities. Environment-specific policies and identity-based authentication are recommended where infrastructure permits.
The comparison table covers placement options (cloud or self-hosted), delivery without plaintext files, and primary use cases. HashiCorp Vault and OpenBao stand out for dynamic credentials and lease management, while Yandex Lockbox integrates tightly with cloud IAM. Licensing differences, offline caching behavior, and Enterprise feature availability are highlighted for each solution.
Practical guidance for Java and Gradle projects includes configuring Spring Cloud Vault with Config Data API imports and selecting compatible versions. The article concludes that tool choice depends on data residency requirements, dynamic credential needs, audit depth, and operational ownership.
Related articles
Rostelecom Refactors InfoSec Careers: Matching Employee Skills to Evolving Business Priorities
Rostelecom's information security block developed a systematic approach to reassess employee expertise and redirect talent to new roles when business structures change rapidly. In one case, an architect hired for a specific team was reassigned after the unit was disbanded, initially moving to a similar position that did not fully align with his broader competencies. HR-business partner Olga Lapshina examined the specialist's full background, including prior work in audits, methodology development, regulatory documentation, university teaching, and scientific research, plus strong mentoring abilities with younger staff. These skills matched the needs of the methodology department, leading to a transfer supported by an individual development plan and a mentor via the internal Tochka Rosta platform. Within two months the employee contributed improvements that accelerated preliminary InfoSec audits by 30 percent and risk assessments by 20 percent while expanding threat scenario coverage by 10 percent. The initiative demonstrates Rostelecom's emphasis on horizontal career movement and retention of experienced professionals through structured career tracks.
How to Avoid Becoming the Hero of 'My Program Deleted 800 GB': Safe Recursive Deletion in Bash and Python
A recent Habr article examines dangerous patterns in recursive file deletion scripts that have caused massive data loss incidents, including an 800 GB wipe triggered by Telegram Desktop on Windows. The piece analyzes classic mistakes such as empty variables in rm commands and extra spaces that turned single paths into multiple destructive arguments, referencing the 2015 Steam Linux bug and the 2011 Bumblebee installer error. It provides hardened Bash templates using set -euo pipefail, ${VAR:?} checks, realpath validation, and --one-file-system flags to prevent deletion of forbidden directories or symlinked targets. The Python section introduces a safe_rmtree wrapper that enforces root boundaries, rejects symlinks, uses resolve(strict=True), and checks shutil.rmtree.avoids_symlink_attacks before proceeding. Additional recommendations include dry-run modes, marker files, temporary directory usage, and logging to make deletion operations auditable and reversible where possible.
Hackers tamper with refrigeration units in European supermarkets, setting temperatures to +50 °C
Attackers gained unauthorized access to refrigeration and freezer control systems in supermarkets across several European countries, including Sweden, Belgium, Luxembourg, and Estonia. In multiple locations they altered temperature settings to +50 °C, risking widespread spoilage of perishable goods. The incidents primarily affected older, unpatched Danfoss controllers that had been connected to networks for remote maintenance. Estonian manufacturer Kitman Coldtech reported that one attack on a legacy Danfoss system was detected and stopped within approximately ten minutes, preventing any damage. Similar intrusions were confirmed by Swedish chains ICA and Coop, following earlier incidents in French supermarkets in October that resulted in product losses. Experts note that legacy industrial controllers remain attractive targets because they are often left exposed once placed online for convenience.
AmneziaWG Container for MikroTik Routers Delivers Top Performance Six Months After Launch
A developer released an AmneziaWG container for MikroTik devices in February 2026 and has since added major improvements in speed, protocol support, and stability. The lightweight container leverages the router's native WireGuard implementation for cryptography while handling AmneziaWG obfuscation in software. Performance now reaches 250-350 Mbit/s on models such as Hap Ax3 and RB5009B after switching to C code and increasing buffer sizes with RouterOS 7.24. New features include server mode for connecting multiple MikroTik devices, random port hopping, IPv6 support, dynamic DNS, and offline configuration. The project survived an early GitHub ban caused by test scripts and has grown to over 370 stars while remaining fully offline and privacy-focused.