Habr•October 27, 2026•🇷🇺Translated from Russian

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

Habr•Other

Home Lab Overhaul: Securing Proxmox Infrastructure After Discovering 63,000 Forgejo Spam Accounts

A home lab administrator migrated Docker stacks to new LXC containers on Proxmox and uncovered multiple security misconfigurations. The setup relied on Cloudflare proxying, MikroTik port forwarding to NPMplus with CrowdSec, and Cloudflare Tunnels for admin panels. After fixing IP address logging in the WAF, logs revealed 63,021 spam accounts created on a Forgejo instance that had open registration. The operator disabled registrations, recreated the instance from verified Git mirrors, and eliminated direct internet exposure by routing all traffic through Cloudflare Tunnel. Additional controls included Zero Trust policies, device enrollment restrictions, and TOTP on Guacamole. The changes removed open ports, enforced proper client IP visibility for CrowdSec, and segmented public, limited, and admin access paths.

Habr•Other

Benchmarking AES-GCM and Ascon AEAD Performance on ESP32 and ESP8266 for Industrial Telemetry

Researchers conducted detailed experiments measuring the real-world costs of three AEAD implementations on ESP32 and ESP8266 microcontrollers used in industrial telemetry scenarios. The study compared mbedTLS AES-128-GCM, legacy Ascon-128 via CryptoLW, and a portable C++ port of NIST Ascon-AEAD128 across three load profiles ranging from stable low-frequency packets to maximum-rate 10 ms intervals. Key metrics included AEAD execution time, CPU cycles, memory usage, UDP transmission success rates, and power consumption captured via TC66C. Initial tests revealed significant UDP packet loss on ESP32 under MAX load due to ENOMEM and ENOBUFS errors in the lwIP stack, which were largely resolved after network handling improvements. Results showed AES-GCM completing in roughly 618 µs on ESP32 versus 803 µs for legacy Ascon-128, while the reverse held on the slower ESP8266 where legacy Ascon outperformed AES by a factor of approximately 3.5. The work highlights that network stack limitations often dominate over cryptographic overhead in high-throughput industrial sensor deployments.

AntiMalware•Other

ARinteg Earns Golden Partner Status from Ideco for NGFW Security Projects

ARinteg has been awarded Golden Partner status by Ideco following successful joint projects in network security. The integrator supplies and implements the Ideco NGFW Novum next-generation firewall for perimeter protection and secure remote access. Collaboration also covers customer migrations from foreign NGFW solutions to the Russian vendor’s product. Commercial Director Dmitry Slobodenyuk stated the new status will allow ARinteg to deliver fuller support across all implementation stages. Ideco’s Partner Relations Head Sergey Markin highlighted ARinteg’s technical expertise in large-scale deployments. The partnership supports import substitution and hybrid infrastructure requirements.

Habr•Other

Zero Trust in Practice: Avoiding YAML Pitfalls with Kubernetes NetworkPolicy and Istio

A detailed case study demonstrates how a single misplaced hyphen in a Kubernetes NetworkPolicy YAML file can unintentionally grant cluster-wide access instead of restricting it to a single client Pod. The example uses a shop namespace API connecting to an orders service in the backend namespace over TCP/8080, showing the correct use of namespaceSelector and podSelector together within the same from element. Tests on K3s with four vCPU and 4 GB RAM confirmed that only the intended client succeeds while others receive Connection refused. The implementation then extends to Istio with PeerAuthentication in STRICT mode and an AuthorizationPolicy limiting requests to GET /orders/* from the orders-api ServiceAccount. Additional checks cover RBAC permissions for creating Pods with specific ServiceAccounts and the need to verify DNS routes and existing allow-all policies. The article stresses maintaining an explicit list of required connections, testing both success and denial cases, and preserving rollback manifests before applying changes in production.