←
Infisical723 posts
Infisical avatar✓

Infisical ✓

@infisical

The open source security infrastructure platform that teams use for secrets, certificates, and privileged access management.

◷ Joined August 2022▧ 137 Photos and videos
Infisical avatar
Infisical@infisical·Oct 27

We’re excited to announce we have raised a $40M Series B! This next round of funding lets us continue to strengthen our secrets, certificate, and access management products. We'll also expand the capabilities of Agent Vault, so engineers adopting AI agents can give them access without handing over the underlying credentials. Thank you to @eladgil, @GradientVC, @ycombinator, and our other investors, as well as our customers, community, and team for helping us get here!

0:39
Vlad Matsiiako avatar
⟳ Infisical retweeted
Vlad Matsiiako@matsiiako·Nov 16

If you're a startup getting serious about security after the recent breaches, here's where I'd start: > Enforce SSO + MFA everywhere. > Get secrets out of code and rotate exposed credentials (@infisical can automate rotation for you). > Audit access and enforce least privilege, with just-in-time access for anything sensitive. > Replace long-lived credentials with short-lived ones (look up Infisical dynamic secrets and add OIDC where it makes sense). > Lock down CI/CD pipelines and pin your dependencies. > Stop giving AI agents unrestricted access to secrets (see Agent Vault). > Set up audit logs and configure a SIEM.

Prasenjit Sarkar avatar
⟳ Infisical retweeted
Prasenjit Sarkar@stretchcloud·Nov 16

Your coding agent doesn't need your whole password vault. It needs exactly one credential, for exactly one call, and it should never actually see it. That's the gap Marc Köhlbrugge was circling when he asked why the best answer anyone has for agent credentials is still 1Password handing over full vault access on every run. It's also exactly the gap Infisical built Agent Vault to close, open sourced this month as a research preview. The idea is almost embarrassingly simple once you see it. Agent Vault sits in front of the agent as a forward proxy. Point the agent's HTTPS_PROXY at it, and every outbound call gets intercepted, stripped of whatever credential the agent tried to attach, and reinjected with the real one from an encrypted store before it reaches Stripe or GitHub or whatever API is on the other end. The agent operates completely blind to the actual secret, and it works underneath the interface layer too, so it doesn't care whether the call came from a CLI, an SDK, or an MCP tool. Compare that to where the rest of the category still sits. HashiCorp Vault and AWS Secrets Manager rotate credentials and issue short lived tokens, which shrinks the exposure window but still hands the workload the actual secret at some point. 1Password's agent integrations do the same thing Marc is complaining about, broad access by default. Infisical's pitch is that none of that matters if the agent gets prompt injected into reading its own secrets back to an attacker, a documented failure mode now, not a hypothetical one. Anthropic's Managed Agents architecture reportedly does something structurally similar, and Browser Use, Vercel, and Cloudflare have each built their own version of credential brokering for their own ecosystems. Nobody's converged on a shared standard yet, which is usually what happens right before one shows up. The catch Infisical admits to is that enforcement still leans on the agent actually respecting the proxy setting, and a network that isn't locked down lets a determined process route around it entirely. My take: that's a real limitation, not a reason to wait. Separating an agent from the secret it's using is a better default than hoping the agent behaves, even an imperfect version of it. x.com/marckohlbrugge/status/…

Vlad Matsiiako avatar
⟳ Infisical retweeted
Vlad Matsiiako@matsiiako·Nov 14

TLDR: static secrets leaked through stolen LLM transcripts. Here are 2 tips to protect yourself from breaches like this: 1. Automate secret rotation or get rid of static secrets completely. For example, @infisical offers 50+ templates for “dynamic secrets” (think secrets generated on the fly that are only valid for a very short period of time). Even if they leak, most likely they would have been revoked for a long time at that point. 2. Implement “honey tokens” - fake credentials that you can spread across your infrastructure. If an attacker tries to use it, you immediately know there has been a breach.

Infisical avatar
Infisical@infisical·Nov 12

It's the last day of @KubeCon_! Stop by booth 113 for all things secrets, certificates, and access management for developers and agents!

Post attachment
Infisical avatar
Infisical@infisical·Nov 10

KubeCon is off to a great start! We kicked things off yesterday with an event alongside our friends at @spaceliftio. It was a great way to get the week started! Now we're back on the show floor and ready for another exciting day. If you're at @KubeCon_ , swing by booth 113 to meet the Infisical team!

Post attachmentPost attachment
Infisical avatar
⟳ Infisical retweeted
Infisical@infisical·Nov 3

No more manually rotating Stripe API keys and risking broken services. Infisical can now rotate those secrets for you! Infisical is the first secrets manager to automatically rotate Stripe API keys. Set a schedule, and the old key stays valid while your app picks up the new one. Available on Advanced and Enterprise plans. Docs linked below 👇

6:19
Tony Dang avatar
⟳ Infisical retweeted
Tony Dang@dangtony98·Nov 1

We are building some seriously insane stuff in house right now @infisical and I can’t wait to share it with the world. This is truly on the edge of helping teams secure every agent deployment with considerations for developer ergonomics, on-behalf-of (OBO) permissioning, and full telemetry into all agent traffic. A future where you can sleep knowing that agents will act responsibly and access only required systems when needed is on the horizon.

Infisical avatar
Infisical@infisical·Nov 2

Introducing Managed Identity for Azure Key Vault! You can now connect Infisical to Azure Key Vault without storing a single Azure secret. Instead of a long-lived client secret, Infisical uses 5-minute tokens. Recent breaches have shown how long a static cloud credential can sit in a third-party platform before it becomes a problem. This removes the credential entirely. Under the hood, every Infisical org is now an OIDC issuer, so this approach can extend to anywhere that trusts outside identity providers. More Azure services and other clouds are on the way! infisical.com/docs/integrati…

0:23
Yuvaraj Sai avatar
⟳ Infisical retweeted
Yuvaraj Sai@yuvaraj_sai_·Nov 1

I wish I got to know about @infisical a couple of months ago. One of the best OpenSource Secret managers with great UX.

Vlad Matsiiako avatar
⟳ Infisical retweeted
Vlad Matsiiako@matsiiako·Nov 1

i hate SF halloween what do you mean you're a hardcoded API key

Post attachment
Garrett Gibbs avatar
⟳ Infisical retweeted
Garrett Gibbs@GarrettGibbs·Oct 28

Six months in and couldn’t be happier I joined Infisical at such a pivotal time. We’ve got an amazing team, real problems to solve, and a lot more to build.

0:39
Ben Davis avatar
⟳ Infisical retweeted
Ben Davis@davis7·Oct 27

Highly recommend architecting your projects in such a way they can be easily run in dev without any setup or env vars Then when u need to run it with the envs use some secrets manager so u just need one key (infisical is the best I’ve found for this)

Coffee with One 🇺🇸 avatar
⟳ Infisical retweeted
Coffee with One 🇺🇸@coffeewithone·Oct 27

We’ve been on @infisical since day 1 and haven’t looked back once. ❤️ AI has changed how fast we ship. Code gets written faster, agents get access to more systems and hat’s exactly where things quietly break if your secrets setup isn’t solid. Infisical is the reason we don’t worry about that. It just works, and our security is airtight because of it. Huge congrats to @matsiiako @maidulll @dangtony98 and the whole Infisical team on the Series B!!!!!

0:39