11770-8Revision
checker

Scope

Free check
No account
Questions
7 in the full check
Stored
Nothing
Uses
Clause 1, the two named functions and the evidence list
Date
The estimate, labelled

Is ISO/IEC 11770-8 your problem?

Clause 1 applies where a cryptographic key is derived from a human-memorised password. Answer seven questions and the reading names your scope, the gaps your answers expose and the dates that follow. An untouched form returns scope incomplete.

Scope and date check

0 of 7 answered
01Do you derive a cryptographic key from a human-memorised password anywhere?

A key used by another algorithm or to unlock a store counts. Hashing a password only to check a login does not.

02Which function produces that key?

Tick every one in use. The public introduction names Argon2i and PBKDF2; the others are a decision to record.

03Is a unique salt generated for each derivation?

A salt may be public. It must not be reused across derivations.

04Do you hold a written parameter record for each use?

Function, variant, salt, cost parameters, output length, library version and the benchmark date.

05Is the inventory of password-derived keys complete?

Every use, the asset it protects, the owner and the recovery path.

06Where does the cryptography evidence live?

The standard does not require an ISMS. The question is where the evidence has a home.

07Do customers send you security questionnaires?

If yes, the answer pack is part of the kit and should match the parameter record.

No account, no email, no storage. The reading is computed in your browser from the reviewed record.

Scope incomplete

Answer the questions to see your reading

An untouched check is not a pass. Tell us what you know and the reading will name the gaps, the estimated date and the next actions.

Your answers stay in this browser. Nothing is sent, stored or added to a list.

How the reading is decided

The engine is a rule, not a model. It reads your answers against the scope in clause 1, the two functions named in the public introduction, and the evidence list in the register. The same answers always produce the same reading. The table below is the regression set the build tests; each row cites the part of the record that justifies it.

The two named functions are Argon2i and PBKDF2. A profile that ticks Argon2id, scrypt, bcrypt or a proprietary function returns in scope with a gap: the public introduction names two functions, and the other is a decision to record, not a synonym.

ProfileReadingBasis
Derives a key from a password, uses Argon2i or PBKDF2, salt and parameters evidencedIn scope, hold and watchClause 1; clauses 6 and 7
Derives a key, uses PBKDF2, no written parameter recordIn scope, gaps to closeClause 7; Annex D
Derives a key, uses Argon2id and records it as Argon2iIn scope, gaps to closeClause 6 (Argon2i named, not Argon2id)
Derives a key, function not identifiedIn scope, gaps to closeClause 5; the public introduction
Derives a key, salt reused across devicesIn scope, gaps to closeClause 3.5, salt
Derives a key, inventory only covers the backup productIn scope, gaps to closeClause 1; clause 5
Unsure whether a password produces a keyLikely in scope, confirmClause 1
No password-derived key; login hashing onlyOut of scope on your answersClause 1
No answers at allScope incompleteThe check refuses to pass an untouched form
Password-derived key protects a backup onlyIn scope, gaps to close if parameters are missingClause 1; Annex D
Four functions in use across three productsIn scope, gaps to close until each is recordedClauses 6 and 7; clause 5
Argon2i on a phone, no benchmark on the weakest deviceIn scope, gaps to closeAnnex D guidance; clause 5
PBKDF2 with a library default countIn scope, gaps to closeClause 7; Annex D
Key derived once and never re-derived after a device swapIn scope, gaps to closeClause 5, use decision
Salt treated as a secret pepper and lost in a restoreIn scope, gaps to closeClause 3.5
No ISMS but a complete parameter recordIn scope, hold and watch, with a SHOULD on evidence locationNo ISMS requirement in the part
Supplier questionnaires answered from memoryIn scope, gaps to closeClause 5; the kit answer pack
A proprietary KDF with a design noteIn scope, gaps to closeThe public introduction names two functions
Keys derived from machine-generated device secrets, not passwordsOut of scope on the password testClause 1
A password manager wrapping a vault keyIn scope, gaps to closeClause 1; clauses 6 and 7
An encrypted backup with a passphrase and a printed recovery keyIn scope, gaps to closeClause 1; clause 5
Argon2i with parameters copied from a vendor blogIn scope, gaps to closeAnnex D guidance
A key derived from a password and then used as an HMAC keyIn scope, gaps to closeClause 1, key used by another algorithm
Unsure which of five products derive keysLikely in scope, confirmClause 1; clause 5

What the check does not do

  • It does not read your code, your configuration or your cloud account. It reads your answers.
  • It does not call an answer compliant, certified or audit-ready. The phrases are scope readings.
  • It does not treat an unknown as a pass. Unknown inputs return scope incomplete or likely in scope.
  • It does not create a deadline. The date is an estimate for planning.

If the answer is "in scope"

The register is the next read. Each of the 11 units carries its public status, the requirement where the public record proves one, our reading where it does not, the evidence a reviewer will ask for and a test you can run. The kit turns those rows into a dated plan you can hand to an owner.

Open the register See the dates