Before You Ask the Vendor: Build a Passive Due Diligence Layer

The vendor has already made the shortlist.

The business owner wants the contract signed this month. Procurement has scheduled the demonstration. The implementation team has started discussing integrations. Then security sends the questionnaire.

At that point, the assessment may still identify important problems. It may also be working against momentum that has already become a business constraint.

There is another problem.

The first substantial evidence often comes from the vendor itself: a questionnaire, policy packet, audit report, architecture diagram, penetration-test summary, or carefully prepared response from the sales and assurance teams.

That evidence matters. It is not the only evidence that matters.

The practical lesson is straightforward:

Third-party risk should begin with passive, evidence-based due diligence before direct outreach, then use vendor-supplied evidence to resolve what outside-in research cannot answer.

VendorRiskAI

Due Diligence Should Start Before the Questionnaire

In July 2026, NIST finalized SP 1326, the Cybersecurity Supply Chain Risk Management Due Diligence Assessment Quick-Start Guide. It defines due diligence as researching and verifying available, pertinent information about a supplier or product so that an acquirer can make informed decisions about new acquisitions or existing systems.

The guide makes an especially useful distinction.

Basic due diligence uses desktop research and publicly available information without contacting the supplier. Enhanced due diligence adds commercial datasets, proprietary sources, and supply-chain illumination tools. NIST recommends choosing the level of effort based on available resources and acquisition criticality, and validating findings against multiple sources when possible.

That creates a useful sequence:

  1. Learn what can be established independently.
  2. Identify what remains uncertain.
  3. Ask the supplier targeted questions.
  4. Validate the answers according to the consequence of being wrong.

The questionnaire becomes more valuable because it is no longer trying to discover everything from a blank page.

Vendor-Supplied Evidence and External Evidence Answer Different Questions

A supplier is usually the best source for information that is not externally observable.

That may include internal governance, access-control design, backup and recovery procedures, secure development practices, personnel controls, incident-response responsibilities, data flows, subcontractor oversight, and evidence from private testing or audits.

Outside-in research answers a different set of questions.

It can help establish:

  • Which legal entity the organization is actually evaluating.
  • Which domains, public services, certificates, applications, repositories, and infrastructure appear related to that entity.
  • Where public-facing operations and important dependencies are located.
  • Whether ownership, leadership, hosting, technology, or product-support conditions have changed.
  • Whether public records identify breaches, sanctions, exclusions, litigation, regulatory action, exposed credentials, obsolete technology, or other conditions relevant to the decision.
  • Which sub-tier providers or shared dependencies may create concentration risk across several suppliers.

Neither view is complete.

A clean external footprint does not prove that internal controls are effective. A strong audit report does not prove that every externally visible asset belongs to the assessed boundary, is currently maintained, or was included in the audit. A questionnaire response may be accurate when submitted and stale six months later. An external observation may be technically correct and still attributed to the wrong subsidiary, legacy domain, shared host, or acquired product.

The goal is not to choose between attestation and observation.

It is to reconcile them.

Start With the Decision, Not the Data

Passive research can produce a large amount of information very quickly. Without a decision boundary, that becomes another collection problem.

Begin by writing down the decision the research must support:

  • Should this supplier enter the shortlist?
  • What diligence is required before contract signature?
  • What conditions should appear in the agreement?
  • Does a proposed acquisition need deeper technical review?
  • Has an existing critical supplier changed enough to require reassessment?
  • Which vendors deserve scarce assessment time first?

Then define the consequence of supplier failure.

The final NIST CSF 2.0 C-SCRM Quick-Start Guide recommends that suppliers be known and prioritized by criticality and that requirements be scaled to the supplier’s importance and the risk presented by the product or service. The updated NIST SP 800-161 Revision 1 likewise treats supply-chain risk as an organization-wide risk-management problem rather than a procurement checklist.

Useful criticality questions include:

  • What sensitive data will the supplier store, process, transmit, or be able to reach?
  • Which production systems, identities, networks, facilities, or business processes will it influence?
  • How quickly could the organization replace the service?
  • What would happen if the supplier became unavailable, untrustworthy, or legally unusable?
  • Which customers, regulators, safety functions, financial processes, or strategic transactions depend on it?

The deeper the dependency, the stronger the evidence requirement should become.

Build the Passive Evidence Record in Six Steps

A passive due diligence layer should produce a defensible record, not a mysterious score.

1. Resolve the identity

Start with the legal name, ownership structure, primary domains, relevant subsidiaries, product names, acquisitions, and known operating locations.

This sounds administrative. It is one of the most important technical controls in the process.

If the assessed entity is ambiguous, every later observation can be misattributed. A certificate, exposed service, breach record, code repository, or hosting relationship may belong to a parent, subsidiary, former brand, customer tenant, reseller, or unrelated organization with a similar name.

Record aliases and relationships explicitly. Do not quietly merge them into one profile.

2. Map the relevant external footprint

Collect only the evidence needed for the decision and allowed by policy, law, and the organization’s rules of engagement.

Depending on scope, that may include public corporate records, regulatory and exclusion lists, company disclosures, breach notices, domain and certificate data, public service metadata, published application information, public repositories, vulnerability and end-of-life information, hosting relationships, and identified supply-chain dependencies.

NIST SP 1326 organizes due diligence into five research categories: foreign ownership, control, or influence; provenance; resilience; foundational cyber practices; and supply-chain tiers. Those categories are broader than an internet scan. They connect technical exposure to ownership, location, operational reliability, product history, and dependency structure.

3. Separate observation, inference, and decision

Every material item should identify what kind of statement it is.

Observation: A public certificate record associates a hostname with a domain. A regulator published an enforcement action. A vendor announced an acquisition. A public repository contains a supported product’s code or documentation.

Inference: The asset may be part of the supplier’s current production environment. The acquisition may change service delivery. The observed version may indicate delayed maintenance. Several vendors may depend on the same provider.

Decision: Require clarification. Expand technical testing. Add a contract condition. Raise the monitoring frequency. Accept the risk. Remove the supplier from consideration.

Treating inference as fact creates false confidence. Treating observation as a decision allows an automated finding to replace accountable judgment.

4. Corroborate, timestamp, and preserve provenance

For each consequential finding, record:

  • The source and collection date.
  • The entity or asset to which it is attributed.
  • The observed fact.
  • The confidence in the attribution.
  • Corroborating or conflicting sources.
  • The age and likely shelf life of the information.
  • The business or technical decision it may affect.
  • The owner and next review date.

NIST SP 1326 specifically recommends validating findings through multiple sources when possible. It also warns that age, recurrence, severity, and current mitigation affect whether historical information remains relevant.

A ten-year-old incident may show organizational history. It may not describe current control performance. A DNS change from yesterday may be current. It may also be routine migration activity with no security significance.

Evidence needs context.

5. Convert findings into targeted supplier requests

The passive record should make the questionnaire shorter and sharper.

Instead of asking, “Do you manage vulnerabilities?” ask:

  • We identified a public service that appears to support this product. Is it inside the service boundary, and how is it maintained?
  • Your documentation names one hosting provider while current external evidence suggests another. What changed, and which subprocessor terms apply?
  • We found a product version with a published end-of-support date. Is that version still used for our proposed service?
  • Your ownership or operating-location data changed during the review period. Does that affect data access, support, resilience, or contractual commitments?
  • Several critical suppliers appear to rely on the same sub-tier provider. What continuity options exist if that provider fails?

These are not accusations.

They are requests to reconcile evidence.

The response can confirm attribution, explain a harmless condition, identify a stale record, disclose a compensating control, or reveal a real gap. Every outcome improves the decision record.

6. Define the refresh triggers before the contract is signed

Third-party risk does not become static after approval.

NIST SP 1326 recommends considering a continuous monitoring process, including when information should be refreshed and how reports will be updated. For banking organizations, the joint Interagency Guidance on Third-Party Relationships similarly describes ongoing monitoring throughout the relationship, scaled to risk and adjusted when the type or level of risk changes.

Useful reassessment triggers include:

  • A merger, acquisition, divestiture, or material ownership change.
  • A new hosting, cloud, identity, payment, data, or support dependency.
  • A material breach, outage, regulatory action, or public allegation.
  • A change in exposed services, certificates, domains, applications, or infrastructure.
  • Product end-of-life, loss of support, or a major technology transition.
  • Expansion into new data, systems, locations, business processes, or customer populations.
  • Repeated failure to explain or remediate a material inconsistency.

Calendar reviews still have value. Event-driven reviews catch change closer to the moment it matters.

Passive Does Not Mean Uncontrolled

An outside-in assessment needs its own governance.

Public availability does not make every collection or use appropriate. The process should define permitted sources, prohibited actions, privacy handling, data retention, evidence classification, analyst access, attribution standards, supplier communication, and escalation paths.

Passive research should not quietly become intrusive testing.

Do not bypass access controls, authenticate without authorization, exploit systems, create load, or probe a supplier beyond the approved rules of engagement. If a finding requires active validation, obtain authorization and move it into a separate assessment plan.

The record can also become sensitive when aggregated. A collection of public facts may reveal relationships, vulnerabilities, acquisition interests, concentration risk, or strategic dependencies that no single source discloses. Protect the resulting analysis according to its consequence, not merely according to the public status of its ingredients.

Measure Decision Quality, Not Finding Volume

A large passive-monitoring feed can look productive while leaving the organization unable to act.

More useful measures include:

  • Percentage of critical suppliers with identity and ownership resolved before direct outreach.
  • Percentage of proposed critical relationships with a passive evidence brief before shortlist or contract approval.
  • Percentage of consequential findings corroborated by more than one source.
  • Percentage of material observations with explicit attribution confidence and evidence age.
  • Time from supplier nomination to an initial decision-ready brief.
  • Percentage of passive findings converted into a targeted question, validation step, contract requirement, monitoring trigger, or documented disposition.
  • Number of critical suppliers sharing the same material sub-tier dependency.
  • Time from a material external change to owner acknowledgement and reassessment.
  • Percentage of unresolved high-consequence assumptions accepted by a named risk owner.

One measure deserves special attention:

How much supplier risk can you explain before you ask the supplier to explain itself?

The objective is not suspicion.

It is preparation.

What Security Leaders Should Do This Week

Choose one proposed or existing supplier that supports a high-consequence business process.

  1. Write the decision. Define whether the work supports shortlisting, contracting, renewal, monitoring, M&A diligence, or escalation.
  2. Set the criticality. Record the data, access, operational dependency, replacement difficulty, and consequence of supplier failure.
  3. Resolve the entity. Confirm the legal name, ownership, domains, subsidiaries, products, and relevant locations.
  4. Build a passive evidence brief. Use approved public and commercial sources to examine provenance, resilience, foundational cyber practices, and material supply-chain relationships.
  5. Label the reasoning. Separate observed fact, analyst inference, unresolved question, and risk decision.
  6. Ask only what the evidence cannot answer. Turn inconsistencies and unknowns into targeted supplier requests and validation steps.
  7. Define the refresh rule. Set calendar and event-driven triggers, a named owner, and a response path for material change.

A questionnaire is useful.

An audit report is useful.

A vendor meeting is useful.

They become more useful when the organization arrives knowing what it has already observed, what it still needs to learn, and which decision the evidence must support.

Do the quiet research first.

Then ask better questions.


Put SilentTiger to Work Before the Questionnaire

MicroSolved, Inc. positions SilentTiger™ as a passive vendor, supply-chain, and external-exposure monitoring capability for due diligence, third-party risk, M&A, and pre-approach research.

MSI can help organizations:

  • Build decision-focused passive due diligence profiles for prospective and existing suppliers.
  • Map externally observable assets, dependencies, ownership, provenance, and change indicators.
  • Corroborate findings across public and authorized commercial sources.
  • Separate observation from inference and translate evidence into targeted supplier questions.
  • Prioritize deeper assessment according to supplier criticality and business consequence.
  • Establish repeatable monitoring triggers for material external change.
  • Support M&A, supply-chain, vendor-risk, and pre-engagement research without treating passive evidence as proof of internal control effectiveness.

To discuss SilentTiger or a passive vendor-risk assessment, contact MicroSolved at info@microsolved.com or +1.614.351.1237.

Relax. We’re on watch.

AI tools were used as a research assistant for this content, but human moderation and writing are also included.

The Leak Is Already Outside: Build an External Exposure Response Loop

The DLP dashboard is green.

Repository push protection is enabled. The approved file-sharing platform blocks public links. Managed laptops prevent copying sensitive files to removable media. The security team can point to policies, controls, alerts, and training.

Then someone finds a current API key in a public repository.

Or a configuration file in a support forum. A source-code fragment in a paste. An internal hostname in a public issue. A customer data sample in a forgotten cloud share. A credential in a contractor’s fork.

The organization did not see the information leave.

That does not make the exposure less real.

This is the gap between data-loss prevention and external-exposure response. Prevention controls watch selected systems, users, repositories, interfaces, and transfer paths. They are necessary. They are not proof that sensitive information never crossed a path the organization could not see.

The practical lesson is simple:

A data-protection program is incomplete until it can find, neutralize, and learn from sensitive information that is already outside the managed boundary.

SecurityReporting

Prevention Sees the Paths It Controls

Organizations should prevent sensitive data from leaving in the first place.

That includes classifying information, limiting access, using secrets managers, scanning source code, blocking known secret patterns, controlling file sharing, monitoring managed endpoints, and reducing the lifetime and authority of credentials.

The joint CISA and FBI guidance on Product Security Bad Practices identifies hardcoded credentials and secrets in source code as a dangerous practice for products used in critical infrastructure and recommends secrets managers and scanning within the development process.

GitHub provides another useful example. Its secret-security guidance distinguishes push protection, which attempts to stop supported secrets before they enter a repository, from secret scanning and public monitoring, which identify exposures that already exist. GitHub describes public monitoring as visibility into credentials exposed beyond repositories owned by the enterprise.

That distinction matters.

Preventive and detective controls are not interchangeable. One attempts to stop the event. The other assumes prevention can fail and looks for evidence afterward.

Even strong platform controls have scope. GitHub’s own secret-scanning documentation describes supported patterns, pair-matching conditions, legacy-token limitations, large-push conditions, and other cases in which push protection may not detect or block a secret.

That is not an argument against push protection.

It is an argument against treating any point control as proof of absence.

Public repositories are only one possible destination. Sensitive material can also appear in support portals, issue trackers, package artifacts, code forks, shared folders, archived pages, discussion sites, and third-party systems. Some of those channels belong to the organization. Others do not. Some produce useful logs. Others may provide only a timestamp, a URL, and a copy of what was exposed.

The control model must account for both conditions:

  1. Prevent what can be prevented inside managed workflows.
  2. Monitor and respond where prevention cannot provide complete visibility.

Treat External Exposure as Incident Evidence

Finding sensitive material outside the organization is not merely a content-cleanup task.

It may be evidence of an incident.

An exposed credential may still authorize access. A configuration may reveal trust relationships, administrative interfaces, naming conventions, or control gaps. Source code may disclose intellectual property, security assumptions, embedded secrets, or exploitable implementation details. A customer record may trigger privacy, contractual, legal, or regulatory obligations. A seemingly harmless internal identifier may help an attacker improve targeting.

The correct response depends on what the artifact can do, what it reveals, how current it is, and who may have obtained it.

This is why deletion alone is not containment.

Removing a repository, post, attachment, or cached page can reduce continuing exposure. It does not invalidate a credential, erase copies, reverse indexing, identify prior access, or prove that the information was never used.

For secrets, the priority is authority.

The OWASP Secrets Management Cheat Sheet recommends that secrets be revocable, rotated, limited in lifetime and privilege, and supported by lifecycle records that help responders understand who had access and when the secret was used or changed. Stopping the application or deleting the exposed file does not necessarily revoke the credential behind it.

For other data classes, the priority may be different. The organization may need to preserve evidence, restrict further access, notify an owner, assess contractual scope, request removal, investigate misuse, or determine whether the material exists in additional locations.

The external artifact is the beginning of the response question, not the end.

Build the External Exposure Response Loop

A practical external-exposure capability has five stages: discover, classify, neutralize, trace, and learn.

1. Discover: What is visible outside the boundary?

Define the sensitive artifacts the organization cares enough to recognize.

The list may include:

  • Credentials, tokens, private keys, and connection strings.
  • Source code and proprietary algorithms.
  • Device, cloud, application, and network configurations.
  • Internal domains, hostnames, project names, and administrative paths.
  • Customer, employee, regulated, or contractually protected data.
  • Documents carrying distinctive identifiers, watermarks, or structured patterns.

Then define the monitoring scope, frequency, owners, escalation path, and evidence-handling requirements for each class.

No discovery method sees the entire internet. A useful program therefore states its coverage and blind spots explicitly. It distinguishes continuous monitoring from periodic searches, platform-native scanning from broader exposure monitoring, and confirmed findings from possible matches that still require analyst validation.

The goal is not to claim universal visibility.

The goal is to reduce the period during which a consequential exposure remains unknown.

2. Classify: What can the artifact enable?

Do not prioritize solely by how embarrassing the artifact looks.

Classify it by authority, sensitivity, current validity, exploitability, reach, and affected business process.

Ask:

  • Is this an active secret, an expired secret, or a string that only resembles one?
  • What systems, data, funds, or actions could it authorize?
  • Is the artifact complete enough to use, or does it become dangerous when combined with other information?
  • Is the exposed copy current, historical, partial, or modified?
  • Does it contain regulated data, customer information, trade secrets, or security architecture details?
  • Is it publicly accessible, indexed, cached, mirrored, or limited to a narrower audience?
  • Who owns the asset and who has authority to contain it?

The fastest path to a good decision is a prepared owner map. Security should not discover during the incident that nobody knows who can rotate the key, suspend the integration, contact the platform, interpret the contract, or decide whether operations can tolerate emergency change.

3. Neutralize: Remove authority before chasing every copy

If an exposed artifact grants access, invalidate that authority first.

Revoke the token. Rotate the key. Terminate sessions. Disable the account. Restrict the affected interface. Replace the certificate. Narrow the permission. Add temporary monitoring or access controls while the permanent change is implemented.

Then address continuing availability of the artifact through the appropriate channel: delete an owned copy, request removal, use an established takedown process, restrict a share, or work with the platform or third party that hosts it.

Containment order matters.

If responders spend hours removing a public page while the exposed credential remains valid, they are reducing visibility without reducing authority. A downloaded copy can still work.

The neutralization plan must also account for dependencies. Rotating one secret may break applications, vendors, automated jobs, recovery processes, or downstream services. That is a reason to engineer revocation and replacement paths before an incident, not a reason to keep exposed authority alive.

4. Trace: How did it get there, and what happened next?

Once the immediate risk is controlled, reconstruct the path.

Determine:

  • Where the artifact originated.
  • Which person, system, process, or third party handled it.
  • When it became exposed and when the organization discovered it.
  • Whether logs show access, authentication, downloading, reuse, or related activity.
  • Whether the same material exists in forks, mirrors, archives, tickets, backups, chat systems, or build artifacts.
  • Whether similar artifacts were created by the same workflow.
  • Whether an attacker could combine the finding with other public information.

NIST SP 800-61 Rev. 3 frames incident response as part of cybersecurity risk management rather than a stand-alone activity and connects preparation, detection, response, and recovery. External-exposure work should follow the same logic. The team needs enough evidence to reduce immediate impact and improve the system that allowed the exposure.

Tracing must remain proportionate. Not every public identifier justifies a full forensic investigation. Not every old credential remains usable. The classification stage should drive the depth of response.

5. Learn: Which control or assumption failed?

The last stage converts a one-time cleanup into program improvement.

An exposure may reveal:

  • A secret embedded in code because the approved retrieval method was too difficult.
  • A repository that did not inherit the organization’s security configuration.
  • A contractor or vendor using an unmanaged development workflow.
  • Sensitive troubleshooting data copied into a support channel.
  • A DLP policy that covered endpoints but not build logs or cloud collaboration.
  • A credential with excessive privilege or no practical rotation process.
  • A data classification rule that employees could not apply to real work.
  • An alert that reached a mailbox nobody owned.

Fix the common cause, not only the visible artifact.

The question is not simply, “Did we remove it?”

The better question is, “What changed so that the same process is less likely to expose the next artifact?”

Prioritize Authority, Exposure, and Business Consequence

External findings need a decision model.

A useful triage approach considers three dimensions.

Authority

What can the artifact authorize or enable?

An active administrative credential, signing key, production token, or remote-access configuration may require immediate containment. A disabled test credential may require documentation and process correction without the same urgency.

Exposure

Who could obtain it, and for how long?

Public, indexed, and mirrored content has a different exposure profile from a restricted ticket available to a small support team. However, restricted does not mean safe. Third-party access, retention, forwarding, and account compromise still matter.

Business consequence

What could happen if the information is used or disclosed?

Consider system control, customer harm, financial movement, service disruption, regulatory scope, intellectual property, safety, contractual commitments, and reputational impact.

These dimensions prevent two common mistakes.

The first is treating every match as a crisis.

The second is treating a small-looking artifact as harmless when it carries substantial authority.

Measure the Response, Not Just the Number of Hits

Raw alert volume is a weak success measure.

More useful measures include:

  • Time from external publication to discovery.
  • Time from discovery to owner acknowledgement.
  • Time to invalidate active authority.
  • Time to determine the affected systems and data.
  • Percentage of high-impact secrets with a tested emergency rotation path.
  • Percentage of material findings with preserved evidence and documented disposition.
  • Recurrence rate by workflow, business unit, vendor, repository, or artifact type.
  • Percentage of monitoring patterns with a named owner and review date.
  • Number of findings that produced a control, process, or architecture improvement.
  • Percentage of high-risk exposures for which misuse could be assessed from available logs.

One metric deserves special attention:

How long does it take to make a discovered artifact harmless?

Discovery creates the opportunity to respond.

Neutralization changes the risk.

Where ClawBack Fits

MicroSolved currently positions ClawBack™ as a data-leak detection capability supporting exposure monitoring, advisory retainers, and vCISO relationships, with evidence that can support response conversations.

That is the right place for external-exposure monitoring in the operating model.

Its job is not to replace DLP, repository controls, secrets management, identity governance, incident response, or legal and privacy review. It helps close the visibility gap between what internal controls observed and what may be visible outside the organization.

The value of a finding depends on the process around it:

  • What classes of information are in scope?
  • Which sources and channels are monitored?
  • How are possible matches validated?
  • Who owns each artifact class?
  • What evidence is preserved?
  • What requires immediate escalation?
  • How will credentials be revoked, files removed, and downstream impact assessed?
  • How will lessons feed back into prevention?

ClawBack should therefore be treated as part of an exposure-response capability, not as an isolated alert feed.

What Security Leaders Should Do This Week

Choose one artifact class with meaningful business consequence: production API keys, administrative credentials, network configurations, source code, customer records, or another clearly owned data set.

Then run this exercise:

  1. Define what a recognizable exposure looks like. Identify patterns, identifiers, owners, and likely external channels.
  2. Document current coverage. Record which preventive and detective controls can see the artifact, and which paths remain outside their scope.
  3. Prepare the owner map. Name the people who can classify the finding, revoke authority, approve operational impact, preserve evidence, request removal, and assess notification obligations.
  4. Test neutralization. Measure how long it takes to revoke or replace the artifact without creating uncontrolled business disruption.
  5. Simulate one discovery. Walk the finding through discover, classify, neutralize, trace, and learn.
  6. Verify the logs. Confirm that responders can determine whether the artifact was used and which systems were affected.
  7. Close one recurring path. Improve the workflow most likely to produce the same exposure again.

Data-loss prevention is important.

Secret scanning is important.

Repository protection is important.

None of them can prove that sensitive information is absent from every external place the organization does not control.

Build the response loop for the moment the leak is already outside.


Put External Exposure Monitoring Into the Security Program

MicroSolved, Inc. can help organizations:

  • Define external-exposure monitoring requirements for credentials, source code, configurations, and other sensitive artifacts.
  • Integrate ClawBack findings into vCISO, advisory, and incident-response workflows.
  • Build artifact classification, ownership, escalation, and evidence-handling processes.
  • Test credential revocation, session termination, takedown, and downstream-impact procedures.
  • Review DLP, repository, secrets-management, vendor, and cloud-collaboration control gaps.
  • Turn recurring exposures into practical control and process improvements.

To discuss ClawBack or an external-exposure response review, contact MicroSolved at info@microsolved.com or +1.614.351.1237.

Relax. We’re on watch.

AI tools were used as a research assistant for this content, but human moderation and writing are also included.

 

AI Agents Need Autonomy Budgets, Not Just Governance Policies

Most organizations are granting AI agents authority faster than they are defining the limits of that authority.

That is the problem.

We have already started treating AI agents as digital workers. That is the right mental model. An agent that can access data, call tools, trigger workflows, generate artifacts, influence decisions, or alter enterprise state is not just another application. It needs identity. It needs boundaries. It needs oversight. It needs evidence. It needs a human owner. It needs a kill switch. That has been the right foundation for agent governance.

But it is not enough.

There is another question that needs to be asked much earlier:

How much damage is this agent allowed to cause before a human must approve the next action?

Not theoretically.

Not in vague risk language.

In actual economic terms.

How much money can it spend?
How many systems can it change?
How many records can it touch?
How much customer impact can it create?
How much privacy exposure can it cause?
How much reputational risk can it accumulate?

If we cannot answer those questions, we have not governed autonomy.

Continue reading →

Passkeys, Not Passcodes: A Practical Enterprise Guide to Moving Beyond Passwords

There is a small terminology problem in the identity world right now, and it matters more than it looks.

A passcode or PIN is usually a local unlock secret. It unlocks a phone, a laptop, Windows Hello, an authenticator app, or a hardware security key. A passkey is different. A passkey is the standards-based replacement for passwords, built on FIDO2/WebAuthn. The user unlocks the passkey locally with a fingerprint, face scan, device PIN, pattern, or security key, but the website or application receives cryptographic proof — not a reusable password. FIDO defines passkeys as FIDO authentication credentials based on FIDO standards, tied to an account, and used with the same process the user already uses to unlock a device.

That distinction is not pedantry. It is the difference between a local unlock method and a replacement for one of the most abused controls in the history of computing.

Passwords have had a long run. They also have had a long list of failures: reuse, phishing, spraying, stuffing, database theft, weak reset workflows, help desk abuse, and user fatigue. We have spent decades trying to compensate for those failures with complexity rules, expiration schedules, password managers, SMS codes, mobile push prompts, training campaigns, and detective controls.

Some of those helped. Some just moved the pain around.

Passkeys change the model.

Continue reading →