Agentic AI insights: security, evaluation and governance for AI agents

The next move. Considered. Ideas for the people turning agentic AI into real work: strategy, systems and the evidence behind better decisions.

Latest perspectives

123 articles
Governance & privacy6 MIN READ

What changes when an AI agent can modify itself?

Self-modification turns runtime learning into controlled software change. Separate what may adapt, require evidence for promotion and preserve a recoverable baseline.

Strategy & transformation6 MIN READ

Who owns an AI agent after launch?

Live agents cut across product, operations, risk and technology. One accountable service owner needs explicit decision rights supported by named control owners.

Evaluation & assurance6 MIN READ

Testing logistics agents under disruption

A logistics agent earns trust when data becomes late, routes close and plans conflict—not when everything follows the timetable.

Cryptographic engineering6 MIN READ

Signatures are the harder half of the post-quantum migration

Key exchange migration is largely a configuration change. Signature migration runs into certificate sizes, fixed-width image headers, verifiers you cannot update and archives that must stay verifiable for decades.

Security engineering6 MIN READ

Write security requirements the team can actually test

"The system shall be secure against unauthorised access" cannot be implemented, reviewed or verified. Security requirements become useful when each one names an actor, a condition and an observable result.

Strategy & transformation6 MIN READ

Adoption is part of agent reliability

An agent is not reliable if people avoid it, over-trust it or route around its controls. Adoption evidence belongs beside technical performance evidence.

A little more clarity

Questions worth asking.

Start with the questions that shape a better decision.

Which enterprise agent questions does the Softlander blog examine?

The blog examines where agents create business value, how teams define release evidence, how authority and tool access should be bounded, and how engineering, security and governance owners can make a shared decision.

Who are the articles written for?

They are written for product, engineering, AI platform, security, governance and transformation leaders responsible for moving an agent workflow from idea or pilot towards accountable operation.

How do the articles relate to Softlander’s services?

Articles explain the problems and decision methods behind the consultancy’s service direction. They are educational material and do not replace a scoped review of an organisation’s actual system.