Preventing Secret Leaks: Integrating Secret Managers with Automated Scanners
Security teams often discover hardcoded tokens in repositories only after they have already been exposed. The standard response involves revoking the key, rotating credentials, and cleaning the code, yet the same mistakes recur within weeks when another developer commits a temporary credential to a .env file without updating .gitignore.
The root cause lies in treating secrets as static constants rather than living entities with a defined lifecycle. The article outlines four stages where processes typically break: creation and generation, storage, usage in runtime or CI/CD, and rotation or revocation.
Deckhouse Stronghold and HashiCorp Vault address the generation stage by issuing dynamic secrets on demand with short time-to-live values and least-privilege scopes. Developers are prohibited from creating keys manually through database consoles or local notebooks; all requests must route through the central manager.
At the storage stage, organizations must avoid placing credentials in Git repositories, shared Wiki pages, or KeePass files protected only by a chat password. CodeScoring.Secrets and Gitleaks continuously scan code, Git history, and pull requests to catch any secrets that bypass the manager.
During usage, secrets should never appear in command-line arguments, unencrypted logs, or Docker image layers. In-memory injection via Kubernetes CSI drivers or Stronghold Agent keeps credentials only in RAM. Additional masking rules in GitLab CI automatically redact sensitive values from pipeline output.
The final stage requires automated rotation through lease mechanisms. When a lease expires, the manager invalidates the credential, closing the window that allowed the five-year exposure in the Toyota case. Service tokens created by departing employees must also be revoked systematically rather than left active.
Combining a centralized Secret Manager with continuous secret detection creates overlapping controls that reduce reliance on individual developer discipline and prevent secrets from reaching public or internal repositories in the first place.
Related articles
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.
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.
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.
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.