Urgent.News

What's breaking now, across thousands of outlets.

Tech

Zero Trust CI/CD: Keyless Bitbucket Deployment on Google Cloud

Using static Service Account (SA) keys in CI/CD pipelines has long been a common method for authenticating to Google Cloud Platform (GCP). However, storing long-lived credentials inside external pipeline environment variables introduces severe security vulnerabilities and ongoing operational friction. Google Mandiant demonstrated in a threat intelligence blog post ( Holes in Your Bitbucket: Why…

This article discusses the security risks associated with using static Service Account keys for authenticating to Google Cloud Platform (GCP) in Bitbucket CI/CD pipelines and how Workload Identity Federation (WIF) provides a modern, keyless authentication mechanism. It explains the benefits of WIF, which include short-lived token exchange, fine-grained scope control, and reduced security risks.

The article outlines the steps required to enable WIF in GCP projects, including creating a Workload Identity Pool and Provider, mapping Bitbucket identity to a GCP Service Account and granting necessary permissions.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Wazuh Exposure Reviews Should Start With API and RBAC Evidence

Wazuh Exposure Reviews Should Start With API and RBAC Evidence Wazuh combines endpoint agents, a manager, indices, and a web interface.

  • Wazuh API is the primary exposure point for security events and configuration changes.
  • Role-based access control (RBAC) governs API permissions beyond authentication.
  • Conduct comprehensive API review with various identities to assess authorization checks.

How to Apply Practices for Uncaught Exceptions in Node.js Error Tracking — Game Imports

Short answer: the best practices for handling an uncaught Node.js exception in a scheduled game-data import are to treat it as a failed batch, preserve it as one bounded error-tracking event, and…

  • Treat uncaught Node.js exception as failed batch in game imports
  • Capture exception once, charge telemetry to import job
  • Emit heartbeat, record completion after durable output

More from Thursday 29 October →