How to Build Secure GitHub Actions Workflows with Least-Privilege Principles

·1 views

GitHub Actions functions as an event-driven automation system that also manages compute resources and credentials, making security a central design concern. Workflows triggered by pull requests sit on a trust boundary, as branch names, commit content, and third-party action outputs can all be attacker-controlled. Experts recommend scoping token permissions explicitly to each job, using OpenID Connect for short-lived cloud credentials instead of long-lived secrets, and pinning third-party actions to immutable commit SHAs. Build and deployment stages should be kept separate, with the same verified artifact promoted across environments rather than rebuilt each time. Applying concurrency controls, using deterministic dependency installation, and treating logs as potential data-exfiltration risks are also key practices for hardening CI/CD pipelines.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Why HTTP 200 Status Codes Can Hide LLM Policy Failures in AI Gateways

When an LLM gateway's policy layer blocks or flags a message, it may still return an HTTP 200 status code, embedding the refusal inside the streamed response rather than signaling an error — making standard HTTP-level monitoring blind to the failure. This design choice is intentional on chat paths, where a 400 error would show a generic alert and hide the explanation, while a 200 keeps the reason visible to the user in context. The problem is compounded because a single POST request to a chat endpoint can contain an entire conversation history — meaning one HTTP log entry may represent dozens of individual messages, each subject to separate policy decisions. Traditional access logs record one status and one latency per request, but cannot reveal which specific message was blocked, which rule triggered, or whether a policy change caused widespread refusals. Effective monitoring of LLM traffic therefore requires message-level audit records that track policy outcomes per turn, not just transport-level HTTP responses.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

EU Parliament Calls for Stronger Platform Accountability on Cyberbullying

The European Parliament adopted a resolution on 30 April 2026 urging the European Commission to assess whether cyberbullying definitions should be harmonised across member states and whether cross-border criminal provisions are needed. The move is a political signal rather than binding law, and it does not immediately alter legal obligations for businesses or create a new EU-wide criminal offence. The resolution argues that existing frameworks, including the Digital Services Act, may not fully address cyberbullying in all contexts, and calls for more effective platform responsibility. It follows the European Commission's February 2026 action plan, 'Safer Online, Stronger Together', which outlined measures covering education, reporting mechanisms, victim support, and enforcement. Businesses operating online communities or communication channels are advised to monitor the evolving policy process closely rather than assume new compliance requirements are already in force.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Anthropic's Jacobian Lens Tests Whether AI Signals Actually Drive Model Outputs

Researchers at Anthropic have developed a tool called the Jacobian lens to address a long-standing gap in AI interpretability: the difference between a signal being detectable inside a model and that signal actually influencing the model's output. Unlike earlier methods such as the logit lens or tuned lens, which reveal what a layer's state resembles, the Jacobian lens measures whether internal representations do causal work by computing the model's averaged Jacobian from each layer to the final output. The tool includes four operations — READ, WRITE, PATCH, and ABLATE — that together allow researchers to edit internal quantities and observe selective behavioral changes, such as swapping a concept pattern to shift a model's arithmetic answer. Ablating these so-called J-space patterns caused multi-step reasoning to collapse to near zero, though the model retained fluency, sentiment classification, and fact retrieval, indicating the effect is task-specific rather than general. The work highlights that interpretability claims require causal intervention, not just correlation, to be considered reliable.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Idempotency Prevents Duplicate Charges in Distributed Systems

In distributed systems, a single user action can trigger multiple identical requests when network timeouts cause retry mechanisms to resend already-completed operations. This leads to real-world problems like duplicate payments, even though no individual component — the client, the network, or the server — has technically malfunctioned. The root cause is that a caller receiving no response cannot distinguish between a request that never arrived, one that failed, or one that succeeded but lost its reply. Since dropping retries entirely is impractical, systems are built on at-least-once delivery, making duplicate handling an inherent part of the protocol. Engineers can address this through three main strategies: designing naturally idempotent operations, using caller-supplied idempotency keys for deduplication, or relying on conditional writes that reject repeated state changes.

0 comments Read more at DEV Community