Your next customer won’t be human.
AI agents skip your screens and call your APIs directly. Every call needs to prove who asked, who it acts for and what this step is for.
The Curity Identity Server is now supported in FIPS mode.
If your environment requires FIPS 140-3 compliant cryptography, you can run Curity in a dedicated image.
Read the guide to learn more:
hubs.li/Q04CfQnZ0
According to Axios, JPMorgan Chase, BofA, Citi and Schwab are restricting third-party AI agents from customer accounts. The issue isn't AI itself, but how access is authorized and controlled.
Our take: hubs.li/Q04C7_8-0
How portable is your trust model, really?
In the latest article in our Security Sovereignty series, Mike Goerlich looks at what it takes to regain control and why true portability goes beyond deployment.
Read the article: hubs.li/Q04B_jj70
Guilds: skilled people who stand behind each other’s work. That’s the bar for the Curity Access Guild, our partner program. New name, more coming.
Resellers, integrators, MSPs and tech partners: get in early and help shape it.
hubs.li/Q04B-NxW0
#PartnerProgram
Digital sovereignty is about more than where data lives. Identity, authorization and policy are critical points of control too, especially in the age of agentic AI.
Mike Goerlich explores why in our latest article.
hubs.li/Q04Bd_jL0
A new chapter for Curity!
We're welcoming Simon Pearce as our new CEO, bringing global leadership experience in enterprise software and cybersecurity.
Get to know Simon and what's next for Curity: hubs.li/Q04zJQ2S0
MCP is stateless now. Your server identifies every caller by its access token so your authorization carries more weight than before.
👉 bit.ly/4ziUdtn
Meet our Jacob Ideskog along with other speakers from Curity, at the Nordic APIs Summit next week, October 13–14.
See you in Stockholm! 👋
Register: bit.ly/3UeFcdf
Tomorrow, October 2 at 14:00 CEST. Curity Identity Server 11.5 with the product team: custom password hashing, a refreshed Admin UI, passkeys across domains.
Register: bit.ly/4hx9NMd
It is a release day! Curity Identity Server 11.5 is out 🚀
Check out what's new and register for the live release webinar: hubs.li/Q04yymBv0
Digital sovereignty asks where your data lives. But there’s another question organizations need to ask: Who controls trust?
Curity CTO Jacob Ideskog on security sovereignty, identity, authorization and the impact of agentic AI:
hubs.li/Q04ycsGn0
What happens when the caller isn’t human? 🤖
We are heading to Nordic APIs Summit in Stockholm, October 13–14.
Join us for the talks and Day 0 Unconference.
Get 20% off with code curity20 at checkout.
👉 hubs.li/Q04ychZw0
SR 26-2 leaves agentic AI outside its model risk guidance, but banks still need to apply their own governance and risk controls. Can you establish which agent acted, whose authority it used and what it was allowed to do?
hubs.li/Q04xXVZ40
With a free trial, you can explore everything from simple authentication flows to the advanced token flows that make up Token Intelligence.
Try it in your own environment and see how it fits what you’re building.
hubs.li/Q04xQKsf0 (hubs.li/Q04xQKsf0)
Why doesn’t Curity offer SaaS? It’s a conscious architectural choice. Business-critical identity belongs under your control.
Explore the full argument: hubs.li/Q04xwWz90 #IAM #IdentitySecurity #SecurityArchitecture
Availability of the access layer is availability of the business.
Read why business-critical IAM should not be a SaaS job: hubs.li/Q04xcMYr0
IAM gets budgeted as security spend. For enterprises it's much more than a login box or a compliance exercise.
Learn more: hubs.li/Q04wPWCq0
Every API consumer is different so give each one a token that fits.
Partners, internal services, agents and customer apps all get access shaped to what they actually need. Your platform opens up without your risk opening with it.
bit.ly/465deTL
#APIsecurity #OAuth #IAM
