NHI & Agentic AI Identity Security FAQ

Question 1

Why do consumer accounts need different IAM controls from workforce identities?

Accepted Answer

Consumer identities operate at much larger scale, with higher volatility, more self-service, and far less direct administrator oversight. That changes the control model. B2C CIAM has to handle registration, consent, social login, and account recovery in ways that support customer journeys while still resisting fraud and takeover attempts.

Question 2

Why do online portals matter so much in customer identity programmes?

Accepted Answer

Portals are where customers experience whether identity design actually works. If access, recovery, and session handling are clumsy, users often read that as a lack of reliability or control. Strong portal design improves service confidence because it gives customers a clear, repeatable way to view and manage their own data.

Question 3

How can practitioners tell whether their team is reading deeply enough?

Accepted Answer

A useful test is whether the team can explain the mechanism, the assumptions, and the limits of a recommendation in its own words. If it cannot, the team is probably consuming information faster than it is understanding it.

Question 4

Why does Active Directory still matter to modern identity programmes?

Accepted Answer

Active Directory still matters because it often acts as the authoritative control plane for authentication, group-based authorisation, and privileged administration. When directory trust is centralised, its availability and integrity affect user access, service accounts, and recovery operations across the enterprise. Identity teams should treat it as core security infrastructure, not an ageing back-office service.

Question 5

What breaks when purchases and identity are not unified across channels?

Accepted Answer

When purchases and identity are not unified, users can buy value on one channel and fail to see it on another, which looks like fraud or product failure from their perspective. Support teams then inherit the inconsistency, and trust drops quickly. Unified identity is what keeps entitlements recognisable across devices.

Question 6

Why do customer identities need different controls from workforce identities?

Accepted Answer

Customer identities behave at much larger scale and under far less organisational context than workforce identities. That changes recovery, assurance, privacy, and user-experience requirements. A control that works for an employee can create abandonment or compliance issues for a customer, so the design must reflect the identity subject and the business outcome.

Question 7

Why do RAG systems need more than a single quality score?

Accepted Answer

A single score can hide whether the retriever failed, the generator hallucinated, or the answer was correct but poorly explained. Separate signals for grounding, relevance, and retrieval quality help teams identify the real problem and avoid fixing the wrong layer of the pipeline.

Question 8

How should organisations govern SIM and eSIM lifecycles in large IoT fleets?

Accepted Answer

Organisations should treat SIM and eSIM handling as a lifecycle control problem, not just an inventory task. Define who approves issuance, who can modify profiles, how replacements are recorded, and when retired devices are fully revoked. Without that, device identity drift creates hidden access and support risk across the fleet.

Question 9

Why do eSIM profiles create lifecycle risk for connected devices?

Accepted Answer

Because the profile can remain active or reusable after the device relationship changes if no one is tracking its state. The risk is not only initial provisioning but also stale access, orphaned profiles, and incomplete offboarding. In fleet environments, that can leave network access attached to devices or subscriptions that should no longer exist.

Question 10

How should teams decide whether a value belongs in Secrets Manager or Parameter Store?

Accepted Answer

Use Secrets Manager for values that need automatic rotation, tighter access control, or direct cross-account sharing. Use Parameter Store for configuration values and lower-risk secrets where you can manage rotation manually or do not need it. The decision should be driven by lifecycle, access scope, and audit needs rather than by default platform preference.

Question 11

What breaks when Parameter Store is used for credentials that need rotation?

Accepted Answer

The team inherits the rotation workload itself. Without built-in rotation, every change depends on scripts, schedules, and custom logic that must be maintained, tested, and audited. That increases the chance of stale credentials, inconsistent revocation, and gaps between the secret’s intended lifecycle and its actual exposure window.

Question 12

Why do virtualisation monitoring platforms need lifecycle discipline?

Accepted Answer

Virtual machines are created, cloned, moved, and retired much faster than manual monitoring processes can reliably follow. Without lifecycle discipline, old objects remain monitored, new guests go unseen, and alerts no longer reflect the live environment. That undermines inventory accuracy and makes incident response slower and less trustworthy.

Question 13

How should automotive teams manage certificate lifecycles for connected vehicles?

Accepted Answer

Automotive teams should treat certificates as fleet identities with explicit owners, renewal rules, and revocation triggers. The practical goal is to automate issuance and replacement across vehicles, roadside units, and update services so that trust does not depend on manual administration or delayed maintenance cycles. Lifecycle visibility is as important as cryptography.

Question 14

What breaks when secrets are managed with sensitive=true alone?

Accepted Answer

Sensitive=true prevents accidental display in plans, outputs, and logs, but it does not encrypt state or stop Terraform from storing the underlying value. Teams that rely on it alone still end up with plaintext secrets in state files, remote backends, and local copies.

Question 15

What breaks when organisations cannot see eSIM profile status accurately?

Accepted Answer

They lose the ability to tell whether a profile is active, pending, installed, or effectively retired. That makes it difficult to prove which devices are authorised, which subscriptions are still valid, and which credentials should be revoked. Without accurate status visibility, lifecycle governance becomes guesswork rather than control.

Question 16

What is the difference between protocol translation and device identity governance?

Accepted Answer

Protocol translation solves message compatibility, while device identity governance decides whether the provisioning flow is trusted, observable, and consistent enough to operate at scale. A translation layer can make two systems talk, but it does not by itself prove lifecycle control, accountability, or supportability across the fleet.

Question 17

Why do IoT identity programmes still fail even when the standard is implemented?

Accepted Answer

They fail because the standard does not remove downstream variability. A device can be SGP.32-aligned and still break if a subscription platform, middleware layer, or operating process does not support the same message contract. In practice, interoperability is a lifecycle issue, because onboarding only works when every handoff in the provisioning chain can execute consistently.

Question 18

How should teams handle eSIM provisioning when SGP.32 devices and SM-DP+ platforms use different message formats?

Accepted Answer

Teams should test the full provisioning path before rollout and not assume that standards compliance guarantees interoperability. If devices speak ASN.1 and platforms still expect JSON, a translation layer may be needed, but it must be governed as part of the identity control plane. The key is proving end-to-end onboarding across every intended platform, not just in one lab environment.

Question 19

What do security teams get wrong about zero-touch eSIM provisioning?

Accepted Answer

They often treat zero-touch as a guarantee of scale rather than a claim that still depends on compatible infrastructure. The mistake is assuming that automated onboarding removes the need for validation. In reality, the more automated the process, the more important it is to confirm that every supported device, platform, and region can complete the same provisioning flow.

Question 20

Why do static token claims create risk in modern IAM programmes?

Accepted Answer

Static token claims create risk because they can outlive the access state they were meant to represent. A user may change role, context may change, or data sensitivity may change after login, yet downstream applications still trust the original claims. The result is authorization drift, where the token says one thing and current policy says another.

Question 21

How should security teams use real-time authorization at sign-in?

Accepted Answer

Use real-time authorization when token claims need to reflect current policy, context, or data sensitivity at the moment of issuance. Keep the policy engine separate from the application, and use the token as the signed handoff between authentication and enforcement. That approach improves consistency, but only if teams govern policy quality, fallback behaviour, and audit logging carefully.

Question 22

Why do AI pipelines need more than container security?

Accepted Answer

Container security only protects one packaging layer. AI pipelines also depend on models, weights, datasets, prompts, registries and retrieval sources, any of which can be altered before inference. A strong control model has to verify the entire artifact chain, not just the container boundary.

Question 23

How can organisations prove what AI model actually ran?

Accepted Answer

Use signed provenance metadata, certificate chains and pre-deployment verification to bind the running model to its source and approval history. That combination turns an opaque deployment into evidence that can support audit, incident response and compliance review.

Question 24

What breaks when model signing is missing?

Accepted Answer

Without model signing, you lose a reliable way to tell whether the artifact in production is the one that was reviewed and approved. That creates silent integrity drift, weakens auditability and makes rollback decisions harder because the team cannot prove what actually ran.

Question 25

What do teams get wrong about credential checkout?

Accepted Answer

Teams often mistake checkout for least privilege because the access is temporary. In reality, the privileged account and its secret still exist all the time, and the same credential may be used by multiple people. That makes attribution weaker and leaves a compromised secret useful until it is rotated or revoked.

Question 26

How should organisations decide which JIT model to use?

Accepted Answer

Use credential checkout only for legacy systems that cannot be redesigned, timed group membership for short escalation workflows, and direct permission assignment for day-to-day sensitive access. If the goal is truly to remove standing privilege, direct permission assignment is the model that gets closest to that outcome.

Question 27

Why do timed groups often fail to solve least privilege?

Accepted Answer

Timed groups fail when the group itself is too broad or poorly maintained. Automatic expiry removes the user from the group, but it does not redesign the group’s permissions, so the entitlement model remains oversized. The result is temporary membership in a standing privilege container, not true least privilege.

Question 28

Why do zero trust and SSO need to be aligned in identity programmes?

Accepted Answer

SSO centralizes authentication, but zero trust determines what happens after authentication succeeds. If the authenticated session is not constrained by context and least privilege, SSO can concentrate trust instead of reducing risk. Alignment matters because the login experience should not outpace authorization discipline.

Question 29

Who is accountable when a vulnerable embedded component ships in production?

Accepted Answer

Accountability usually spans build engineering, product security, and release management because no single team owns the full chain from source revision to deployed image. Governance works only when one function can answer which artefacts were rebuilt, which products consumed them, and which devices still need replacement.

Question 30

How should organisations govern shared AI conversations that can be indexed by search engines?

Accepted Answer

Treat shared AI conversations like published content, not private drafts. Disable indexing by default, classify sensitive output before sharing, and require approval for any externally visible link. Governance should cover the account, device, data category, and retention rules so employees cannot accidentally turn confidential dialogue into searchable public material.

Question 31

Who is accountable when hardware-level policy features affect AI services?

Accepted Answer

Accountability should be shared across procurement, security architecture, legal, and platform operations, with a named owner for trigger authority and audit review. When a hardware control can affect availability or visibility, governance must be explicit enough to answer who approved it, who can activate it, and who reviews its use.

Question 32

How can security teams tell whether API exposure is becoming a governance problem?

Accepted Answer

Look for endpoints that return personal data without a clear identity decision, weak logging around record retrieval, and approval gaps between development and production. If the team cannot show who authorised the interface, what data it can expose, and how misuse is detected, governance is already failing.

Question 33

Why are encryption backdoor proposals a governance problem as well as a security problem?

Accepted Answer

They create hidden override paths that sit outside normal access governance. That means legal, policy, and provider decisions can alter the control environment without the customer’s direct approval, which complicates accountability, risk assessment, and compliance evidence for sensitive data.

Question 34

Why do strong encryption controls matter for compliance as well as security?

Accepted Answer

Strong encryption matters because it supports confidentiality expectations, but compliance depends on how the control is described and governed. If a service advertises protection while allowing exceptions or backdoor-style access, regulators may view the mismatch as deceptive. Teams need technical controls, accurate policy language, and evidence that exceptions are narrow and approved.

Question 35

How should teams govern requests to weaken encryption under external pressure?

Accepted Answer

Teams should route such requests through a formal exception process with legal review, security sign-off, scope limits, and a defined expiry or rollback condition. They should also decide in advance what users must be told and when. That prevents a temporary accommodation from turning into an untracked standing control failure.

Question 36

What do security teams get wrong about password spraying?

Accepted Answer

They treat it as an authentication nuisance instead of an identity reconnaissance method. Spraying tests where controls are weak, which accounts lack strong protection, and whether fallback paths can be abused. The real failure is not just weak passwords, but weak segmentation between accounts, systems, and trust boundaries.

Question 37

Why do managed service provider accounts create outsized risk?

Accepted Answer

Because they often bridge multiple clients and control planes, so one compromise can reach many environments. If those accounts have broad standing access, attackers inherit a ready-made distribution channel. The risk is highest when offboarding, session controls, and privilege scoping are weak or undocumented.

Question 38

Why do leaked AI credentials create a larger governance problem than a simple code mistake?

Accepted Answer

Because the secret is the authority. A leaked API key can authenticate directly to services, bypassing normal user interaction and creating a live access path that survives the original commit. That makes the issue a NHI lifecycle problem, where ownership, expiry, and revocation matter as much as detection.

Question 39

What breaks when sensitive identity data is accidentally shared outside controlled channels?

Accepted Answer

The main failure is loss of containment. Once a file leaves approved systems, copies can be forwarded, reposted, or retained in places the organisation cannot revoke. That turns a simple sharing error into a prolonged identity protection problem, especially when the data can be used to locate, profile, or target named individuals.

Question 40

Why do leaked identity records create risks beyond privacy compliance?

Accepted Answer

Because some records are operationally dangerous, not just personal. If the data identifies people who may face retaliation, fraud, or coercion, the incident affects safety, duty of care, and crisis response. Security teams must therefore assess harm potential, not only legal exposure or notification thresholds.

Question 41

Why do internet-facing collaboration servers increase lateral movement risk?

Accepted Answer

They often sit between users, content, and internal services, so a single exploit can expose more than the application itself. If the server can reach privileged back-end resources or cached credentials, the attacker can pivot from application compromise into broader identity and access abuse. Segmentation and least privilege determine how far that pivot goes.

Question 42

What breaks when a SharePoint zero-day gives unauthenticated remote code execution?

Accepted Answer

The login boundary breaks first, because the attacker does not need credentials to execute code on the server. From there, the compromise can move into file-system writes, web shell deployment, and internal reconnaissance. In identity terms, that creates a foothold near service accounts, admin sessions, and downstream systems that were never meant to be internet reachable.

Question 43

Why do AI agent source leaks matter for IAM and NHI governance?

Accepted Answer

Because leaked source often reveals how the agent authenticates, what it logs, and which identities or tokens it can touch. That information helps attackers target trust assumptions, but it also helps defenders see where access boundaries are too loose. In practice, source leakage can turn an engineering issue into an identity governance problem.

Question 44

Why do AI agents create a separate data governance problem from human users?

Accepted Answer

AI agents can access and move data at machine speed across systems, but they do not naturally fit human review processes or ownership models. That means teams must govern them as non-human identities with explicit permissions, logging, and revocation paths. If they are treated like ordinary users, oversight gaps appear quickly.

Question 45

What breaks when insider-risk programmes only monitor people and not AI agents?

Accepted Answer

Programmes miss the delegated layer where sensitive actions are increasingly executed. An AI agent may access data, chain tasks, or trigger workflows on behalf of a user, but if the agent is not tracked as an identity, its permissions and behaviour sit outside normal governance. That creates blind spots in accountability, review, and containment.

Question 46

How do AI agents change email governance for IAM teams?

Accepted Answer

AI agents that read or send email become non-human identities with delegated authority. That means their mailbox access, content handling, and outbound actions need lifecycle control, scope limits, and monitoring. If the agent can trigger business actions, it needs governance that matches the impact of those actions.

Question 47

Why do agentic workspaces create harder IAM and NHI governance problems than ordinary automation?

Accepted Answer

Agentic workspaces combine human intent, delegated access, and machine execution in one path, so the security question becomes attribution and scope rather than simple authentication. IAM and NHI governance must prove which identity acted, what it was allowed to do, and whether the action stayed inside its intended boundary.

Question 48

What is the difference between blocking an agent in the registry and disabling its identity?

Accepted Answer

Blocking in the registry limits whether users can install or use the agent in supported Microsoft 365 experiences. Disabling the identity stops authentication and token issuance for that agent identity. Those actions are not interchangeable, so teams should choose the control based on whether the goal is discovery suppression, usage restriction, or identity revocation.

Question 49

What do security teams get wrong about agent registration in Microsoft environments?

Accepted Answer

They often assume that registration creates an identity and that visibility implies control. In reality, a registry can hold metadata without creating the enforceable identity layer, so teams must verify linkage, ownership, and permission boundaries before treating the agent as governed.

Question 50

Who is accountable when a grey-market device or vehicle leaves the rightful owner locked out?

Accepted Answer

Accountability usually spans the OEM, dealer, reseller, and service provider because each may control part of the identity lifecycle. The key question is which party owns registration, re-binding, and recovery when the official support model is absent. Without that assignment, the weakest channel becomes the de facto access policy.

Question 51

Why do companion apps and backend APIs create such a large risk in connected cars?

Accepted Answer

Because they are the external surfaces that translate identity into physical control. When those services can change permissions or issue vehicle commands, any weakness in registration, authorisation, or monitoring can have real-world impact. Teams need to treat those APIs as privileged services, not as simple mobile integrations.

Question 52

What breaks when connected-vehicle accounts are tied to phone numbers that can expire or be cloned?

Accepted Answer

The ownership model breaks because the account, not the vehicle, becomes the primary control point. If the phone number lapses, is cloned, or is held by a third party, the legitimate owner can lose access to commands such as unlock, start, and location. That creates a lockout and extortion risk, not just an authentication issue.

Question 53

How do security teams know if first-90-day monitoring is working?

Accepted Answer

It is working when the organisation can spot abnormal access, unusual data movement, or identity inconsistencies early enough to intervene before trust is established. Good monitoring produces actionable escalation, not just alerts. It should also surface whether a new hire is using data, systems, or communication patterns outside the expected role profile.

Question 54

What breaks when candidate identity is not verified strongly enough in hiring?

Accepted Answer

Weak verification breaks trust at the point where identity becomes access. A candidate can pass interviews, obtain onboarding credentials, and inherit entitlements before anyone confirms they are who they claim to be. That creates a gap where legitimate-looking access can be used for insider theft, persistence, or data exposure before normal controls catch up.

Question 55

What breaks when merchant onboarding is too fast and too shallow?

Accepted Answer

When onboarding moves too quickly, platforms can approve merchants that cannot be properly verified, creating fraud exposure, chargeback losses, and compliance failures. The core breakdown is not speed itself, but the loss of assurance that the business is real, owned by the right people, and operating within acceptable risk thresholds.

Question 56

Why do merchant onboarding controls need to be risk based?

Accepted Answer

Merchant populations are not uniform, so one verification depth cannot fit every applicant. Risk-based controls let PSPs apply stronger checks to higher-risk industries, jurisdictions, or ownership structures while reducing friction for lower-risk merchants. That balance improves conversion without abandoning due diligence.