U.S. Bank has launched Protect 360, an identity, privacy and credit-monitoring service delivered through its mobile app and online banking. The move broadens the bank’s customer-protection offer beyond card and account fraud into the wider identity ecosystem.

The Essentials tier is available to eligible customers at no additional charge and includes credit monitoring, identity-risk alerts, dark-web monitoring and visibility of personal information on data-broker sites. A Premium tier costs $9.99 a month plus tax and adds automated data-broker removal and up to $1 million in identity-theft coverage, subject to policy terms. The service replaces the bank’s previous credit-monitoring offer.

U.S. Bank notes that alerts depend on matching information in TransUnion’s databases and that the score shown is educational rather than one used for lending decisions. Those qualifications are important: monitoring can make a customer aware of exposure, but it does not prevent every form of impersonation, account takeover or synthetic identity fraud.

The commercial lesson is that identity protection is becoming part of the everyday banking proposition rather than a specialist add-on. The governance question is whether customers understand what is monitored, which partners process their data and what action follows an alert. Banks should measure successful intervention, not just enrolment or notification volume.


Execution Level Governance- What audit-ready agent governance actually looks like
David Girvin, founder and CEO of Assury argues that model-in-the-loop review, AI governing AI, is fundamentally unreliable for regulated environments: even the best-performing models miss a meaningful share of violations, the reviewing model is typically provided by the same vendor being reviewed, and prompt injection or context poisoning can compromise both the acting agent and its supposed overseer simultaneously. He makes the case for deterministic, architecturally enforced controls instead, walking through Assury’s approach of autonomy zones, session risk accumulation, and credential starvation, which lets a compromised agent be cut off from its tools instantly rather than relying on time-boxed access. The conversation touches on why David is sceptical of just-in-time credentialing as a solution for agent security more broadly, since agent sessions don’t run on predictable human timescales, along with the current gap between how identity and security vendors are pitching agent protection and what he sees happening at the execution layer in practice. He also discusses the compliance and audit implications of probabilistic decision-making, arguing that regulated industries will increasingly need tamper-evident, hash-chained audit trails that can withstand scrutiny from auditors and regulators who are only beginning to understand agentic risk, and reflects on a named frontier lab’s own published framework as an example of the gap between research and practitioner reality. Elsewhere, David reflects candidly on building a bootstrapped security company in an increasingly crowded market, why he turned down aggressive VC funding to stay in control of the product, and what a credible third-party assessment of his own gateway would need to look like given that Assury sits directly in the execution path for every customer’s agents.
Share this post
The link has been copied!