Risorse · 11

Identità e recupero dell'account: governare l'intero ciclo di vita

Collegare la creazione, la modifica, i privilegi, il recupero e la chiusura dell'account a prove verificabili e decisioni simulate.

Aggiornato · 8 min

Sala immaginaria vuota per la verifica delle identità con due chiavi di sicurezza, carta bianca e cartella bordeaux Illustrazione editoriale generata con IA

Obiettivi di questa guida

  • Collegare ogni account a una persona o a un servizio
  • Ridurre i privilegi permanenti
  • Proteggere le richieste di recupero
  • Revoca rapida senza interrompere la continuità

Verifica rapida

  • Chi approva la creazione e la modifica del ruolo?
  • Un vecchio fattore può reimpostare l'account da solo?
  • Le azioni sugli account condivisi sono attribuibili?
  • I privilegi scadono?
  • È stata esercitata la procedura di smarrimento del telefono?

Metodo passo passo

  1. 1

    Inventariare identità e dipendenze

    Elencare account umani, di servizio, condivisi, federati e di emergenza. Collegarli ad applicazioni, proprietari, metodi di autenticazione e dati accessibili.

    Risultato: registro di identità, account, sistema e proprietari.

  2. 2

    Collegare il ciclo di vita agli eventi

    Definire i trigger per onboarding, mobilità, assenza, modifica del ruolo, cessazione del rapporto di lavoro ed eliminazione. Misurare il ritardo tra l'evento e la modifica effettiva dell'accesso.

    Risultato: matrice eventi e azioni.

  3. 3

    Ridurre i privilegi

    Separare l'uso quotidiano dall'amministrazione, limitare la durata dell'accesso con privilegi elevati e rivedere i diritti in base al rischio del servizio.

    Risultato: catalogo dei ruoli ed eccezioni datate.

  4. 4

    Rafforzare il ripristino

    Utilizzare prove indipendenti, un canale sicuro, un ritardo adeguato e l'escalation umana per le richieste insolite.

    Risultato: albero decisionale per il ripristino.

  5. 5

    Prepararsi alla perdita e alla compromissione

    Pianificare la revoca di sessioni, fattori e dispositivi, la comunicazione con l'help desk, l'accesso di fallback e la conservazione proporzionata delle tracce.

    Risultato: manuale operativo per il blocco e il ripristino.

  6. 6

    Esercitarsi e migliorare

    Testare una partenza urgente, un telefono smarrito e un tentativo di impersonificazione. Osservare le decisioni, le tempistiche, le prove e l'impatto operativo.

    Risultato: rapporto di esercitazione e piano di rimedio.

Esempio pratico fittizio

Situazione illustrativa

Un amministratore perde un dispositivo di autenticazione mentre è reperibile. Il supporto verifica una prova concordata in precedenza, ottiene una seconda autorizzazione per il ripristino e invalida le sessioni interessate.

Decisione e prove attese

La procedura verifica la continuità del servizio e conserva la richiesta, l'autorizzazione, l'autenticazione sostitutiva e la revisione post-incidente.

Indicatori di gestione

IndicatoreCosa misuraPrima azione
Account attribuitiAccount collegati a un proprietario attivoGestire prima gli account senza proprietario
Ritardo di revocaTempo intercorso tra l'evento e la rimozione dell'accessoAutomatizzare i passaggi affidabili
Privilegio temporaneoAccesso elevato con durata e motivazioneScadenza predefinita dei diritti
Recupero verificatoRichieste successive a ogni prova previstaEsaminare ogni bypass

Errori comuni

  • Trattare le domande personali come prova valida
  • Consentire al supporto di bypassare l'autenticazione a più fattori senza doppio controllo
  • Dimenticare gli account di servizio
  • Mantenere il privilegio dopo un'assegnazione

Domande frequenti

L'autenticazione a più fattori è sufficiente?

No. Riduce alcuni rischi, ma il ciclo di vita, il recupero, le sessioni e i privilegi possono comunque rimanere vulnerabili.

Tutti gli account condivisi dovrebbero essere vietati?

Preferire identità individuali. Quando un account condiviso rimane necessario, documentarne il motivo, limitarne l'utilizzo e rendere ogni utilizzo attribuibile.

Cosa fare per prima cosa?

La perdita dell'autenticazione principale e l'improvvisa assenza di un utente con privilegi elevati rivelano rapidamente le reali dipendenze.

Identità: fattori, sessioni e recupero

Le note dettagliate di questa edizione sono disponibili in inglese.

An authentication method must be assessed alongside enrolment, recovery and the sessions it opens. A passkey label, a phone or a biometric sensor does not by itself establish the assurance level of the entire service.

References use NIST SP 800-63B-4, finalised in July 2025, and WebAuthn Level 3, a W3C Recommendation since 25 August 2026. AALs describe authentication transactions rather than product scores or certifications earned by ticking this table. Application depends on service scope and risk assessment.

Sources consulted on .

Due chiavi di sicurezza senza marchio in un laboratorio informatico vuoto Illustrazione editoriale generata con IA
Two unbranded keys in an empty lab. Appearance proves neither key non-exportability nor assurance level.

Compare eight methods without confusing their guarantees

Compare eight methods without confusing their guarantees
Method and referenceProperty and conditionsRecovery and dependenciesEvidence to request
Entered password

NIST · Authenticators and password requirements

Knowledge factor; a false site can relay or capture the secret.Depends on the password manager and the password replacement path.Length policy, compromised-secret blocking and a tested replacement journey.
Manually entered TOTP

NIST · Authenticators and password requirements

Possession of a shared secret; manual entry does not bind the output to the legitimate session.Plan for loss of the generator and protection of seeds or provider backups.Authorised enrolment, secret protection and revocation; do not call every OTP phishing-resistant.
SMS or voice code

NIST · Authenticators and password requirements

PSTN out-of-band channel, restricted in the NIST framework; manual codes are not phishing-resistant.The number, carrier and SIM or line changes are dependencies.Channel justification, risk signals, alternatives and number-change procedure.
Simple push approval

NIST · Authenticators and password requirements

Approval without cryptographic verifier-name or channel binding does not establish phishing resistance.Lost phones and application re-enrolment require handling.Actual protocol, user intent and enrolment controls; the push label alone is insufficient.
Syncable WebAuthn with UV

NIST · Syncable Authenticators

W3C · WebAuthn Level 3

Cryptographic binding to the service; user verification (UV) must be requested and checked when required. Syncable keys are exportable in NIST terminology.The sync account, its devices and its recovery enter the trust boundary.Sync and UV requirements. Syncable methods do not fit AAL3, which prohibits key export.
Device-bound WebAuthn with UV

NIST · Authentication Assurance Levels

W3C · WebAuthn Level 3

Service binding and user verification. Device-bound alone does not establish non-exportable hardware protection.Device loss requires another authorised method or controlled recovery.Storage properties, UV, proof of non-exportability when needed and tests of actual clients.
WebAuthn key without UV

NIST · Authenticators and password requirements

W3C · WebAuthn Level 3

Service binding, but possession alone in this case. A touch or user presence (UP) flag is not proof of user verification (UV).Plan a second authorised method and lost-key revocation.UP/UV checks and the factor combination required by the service; hardware form alone does not establish MFA.
Biometrics considered alone

NIST · Authenticators and password requirements

In the NIST framework, biometrics accompany a physical authenticator in MFA; they are neither secrets nor sufficient standalone mechanisms.Provide a non-biometric alternative and protect biometric information appropriately.Comparison location, activation role and accessible alternative; distinguish biometric comparison from cryptographic proof.

Three AALs: distinguish requirements and recommendations

Three AALs: distinguish requirements and recommendations
Level and factorsResistance and key exportOverall reauthentication timeoutInactivity
AAL1

One factor can suffice at this level.

Phishing resistance not imposed by this level; key export permitted.At most 30 days: SHOULD recommendation.No numeric ceiling in this reference; define the service policy.
AAL2

Two distinct factors.

A phishing-resistant option must be offered; key export permitted under applicable conditions.At most 24 hours: SHOULD recommendation; establishing a definite overall limit remains mandatory.At most 1 hour: SHOULD recommendation.
AAL3

Cryptographic authenticator and additional or activation factor.

Phishing resistance and a non-exportable private key required.At most 12 hours: SHALL requirement.At most 15 minutes: SHOULD recommendation.

These values are not cookie lifetimes to copy blindly. NIST distinguishes overall and inactivity limits and then defines reauthentication rules. Applications may choose shorter periods based on risk. IAL concerns identity proofing and FAL federation: AAL does not replace either dimension. NIST §2 →

Passwords: seven precise NIST reference points

Single factor
Minimum 15 characters required.
Within MFA
Minimum 8 characters required when the password is used only in a multifactor process.
Accepted length
Allowing a maximum length of at least 64 characters is recommended.
Composition
No imposed mixture of character types.
Replacement
No arbitrary periodic changes; force a change when there is evidence of compromise.
Secrets to reject
Compare against commonly used, expected or compromised passwords.
Entry assistance
Allow password managers and autofill; permitting paste is recommended.

NIST §3.1.1.2 →

Recovery: four classes and their conditions

Previously saved code
At least 64 random bits in the NIST framework; offline subscriber storage, hashed server storage and invalidation after use.
Code issued on demand
Codes sent by text or voice are valid for at most 10 minutes; email codes for at most 24 hours. Verify addresses and apply the target level’s conditions.
Recovery contact
Organise contact addresses and associated checks; a personal relationship does not replace technical recovery requirements.
Repeated identity proofing
An option for previously identity-proofed accounts. Without prior identity proofing, do not claim to re-verify an unknown identity.

Replacing a forgotten password through another still-valid authenticator is binding a new authenticator rather than necessarily account recovery. Document notifications, delays, revocations and responsibilities so support does not become a bypass. NIST §4 →

Connect authentication, sessions and incidents

Connect authentication, sessions and incidents
StageProposed practical checkObservable evidence
EnrolCheck who authorises a new authenticator and notify the subscriber through a known path.Record of binding, associated method and authorisation basis.
AuthenticateCheck the protocol, expected domain and required factors before granting access.Results on chosen clients, with presence and verification indicators separated.
Manage the sessionDefine overall expiry, inactivity, reauthentication for sensitive actions and logout invalidation.Expired-session, logout and post-revocation access tests.
Report lossIdentify the affected authenticator, preserve useful evidence and decide invalidation based on suspected compromise.Report timeline and observed access result after handling.
RecoverFollow a documented path, notify and prevent an old session from adding a new method without appropriate checks.Successful recovery case and refused bypass case.
Leave the serviceRemove obsolete authenticators and access; address relevant sessions, devices and sync authorisations too.Revoked methods, removed access and remaining dependencies.

WebAuthn: verify the response at the service

The server must correlate the challenge, authorised origin, RP ID hash and signature with the expected ceremony and check required flags. UP signals presence; UV signals user verification. BE and BS describe credential backup eligibility and state without independently certifying the sync system. Use a maintained library and the complete procedures in specification sections 7.1 and 7.2. WebAuthn Level 3 →

Include people who use a different journey

WCAG 2.2 criterion 3.3.8, level AA, addresses cognitive tests during authentication with specific exceptions and assistance mechanisms. Test password managers, paste, labels, keyboard, cancellation and fallback in practice. NIST requires a non-biometric alternative; making it usable is part of design. WCAG 2.2 · 3.3.8 →

Continue with identity governance →

Primary references and scope

Publication and consultation dates are distinct. Proposed tests and evidence are editorial; linked normative texts govern. Vendor documentation describes its own product and does not establish your application’s AAL.

Estensioni: permessi e accesso

Le note dettagliate di questa edizione sono disponibili in inglese.

Robust authentication does not describe extension access

Phishing resistance does not remove the need to examine what runs in the browser after a session opens. A manifest provides clues about cookies, scripting, debugging and identity without establishing collection.

  • Test approved extensions in a profile dedicated to sensitive operations.
  • For identity, inspect OAuth scopes and recipients; this permission does not enumerate identity-provider rights.
  • Distinguish session revocation, token revocation, extension disablement and native-component removal.

Read the permission directory and manifest examples →

Google Chrome · Stay secure · Documentation consulted 2026-10-23; browser behaviour remains version-dependent

Riferimenti ufficiali

I riferimenti supportano il metodo. Adattare i controlli al proprio contesto; non costituiscono una certificazione. I titoli dei riferimenti originali e i documenti di origine potrebbero essere in un'altra lingua.

Riferimenti consultati il .