← Înapoi la Urmăritori

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 153
  1. Automating Code Security Reviews

    Also: The title has been editorialized for marketing purposes.

  2. Littlefactory

    I just published my homebrew coding agent orchestrator I’ve been using in the last - checks calendar - three months.

  3. All You Need Is CLI

    One of the engineers behind Manus shared a bunch of interesting tips about building agents.

  4. Test Theater

    This is an interesting framing about agents writing meaningless tests: Unless you are very clear and careful, AI coding assistants at the moment will look at your implementation and write tests that confirm your code does what it already does.

  5. Scaling Vulnerability Management with AI

    As the product grows and engineers are adopting AI tooling, the security team has more and more code to protect from vulnerabilities.

  6. Agentbox

    Since there are so many to choose from, I built my own sandbox for local coding agents.

  7. On Sandboxing Agents

    I am still on a quest to stay out of the loop with coding agents, to reach warp speed yoloness.

  8. Agent Sandboxes

    I am forcing myself to stay out of the loop, and I am looking at ways to sandbox coding agents running without supervision.

  9. GH Issues Considered Dangerous

    We are moving towards a place where ticketing systems will become an important component to protect, akin to CI/CD.

  10. Claude Code Sandbox

    How does Claude Code sandbox work when used with --dangerously-skip-permissions?

  11. How I Think About Agentic Risks

    Fully aware that this might be obsolete in half a year, this is my current mental model to reason about AI Agents risks.

  12. Coding Agents Security Theater

    Security is hard so let’s skip it.

  13. Finding vulnerabilities with LLMs

    Finding vulnerabilities in modern web apps using Claude Code and OpenAI Codex.

  14. The nx Breach

    How did they breach nx to publish a malicious package?

  15. How to Sell to Security Teams

    Context I wrote this some time ago as an internal memo for marketing and product to help craft value propositions to sell security tools to security teams.

  16. I’ve spent a good year working on a security strategy to manage multi-cloud environments, in this article I want to share what I wish we did in advance to be better prepared.

  17. Using Apps Script for scripting GSuite / Google Workplace will generate Google Cloud Platform (GCP) projects in the background.

  18. Service Accounts in Google Cloud Platform (GCP) are the main vector to hack an account: it’s easy to use them wrong and end up with a compromised key and a lot of headaches.

  19. Securing containers is a complex task.

  20. Google Cloud IAM for Security Teams

    Identity and Access Management (IAM) is an important piece of the cloud puzzle and it’s usually a source of headaches from a security point of view.

  21. whispers

  22. whalescan

  23. version-checker

  24. vector

  25. tunshell

  26. trailscraper

  27. terragoat

  28. talisman

  29. synator

  30. syft

  31. Stormspotter

  32. stash

  33. starboard-octant-plugin

  34. starboard

  35. spacesiren

  36. SkyArk

  37. sinker

  38. SimuLand

  39. SFPolDevChk

  40. secrets-store-csi-driver-provider-azure

  41. rode

  42. regula

  43. rego-policies

  44. professional-services

  45. PowerZure

  46. opa-image-scanner

  47. lsh

  48. litmus

  49. kubernetes-goat

  50. kubernetes-examples