Technology keeps getting easier to use.
Passwords are replaced with single sign-on. Apps connect automatically. Devices sync in the background. APIs let systems talk to each other. Browsers remember sessions. AI assistants can access calendars, documents and email so they can be more useful.
All of that is convenient.
But convenience rarely comes for free.
That is the point behind Convenience Is an Attack Surface. Every time we remove friction for the user, we usually create another connection, permission, token, session or trust relationship somewhere behind the scenes.
The user sees one click.
The system may see five different systems trusting each other.
That is where the risk appears.
Single sign-on makes life easier because users do not need a different password for every application. But it also means one identity can become the key to many services.
A browser that keeps you logged in saves time. But if someone gains control of that session, they may not need the password at all.
An API integration removes manual work. But that integration may also carry credentials and permissions that remain active continuously.
The same pattern is becoming even more important with AI.
An AI assistant becomes more useful when it can read email, search documents, access calendars and call external tools. But every additional capability expands what the assistant can reach if something goes wrong.
This does not mean convenience is bad.
Security that makes technology impossible to use usually does not survive very long either.
The better approach is to recognise that convenience changes the architecture.
If users need single sign-on, protect the identity strongly.
If applications need APIs, limit the permissions.
If sessions remain active, monitor them and make them easy to revoke.
If AI agents need tools, control which tools they can call and what actions those tools are allowed to perform.
Convenience should reduce effort for the user without creating unlimited trust underneath.
That distinction matters.
Good technology makes complicated things feel simple.
Good security makes sure that simplicity does not quietly become excessive access.
Because every time we make something easier to use, we should probably ask one more question:
What did we have to trust to make it this convenient?