EvidenceSheet

8.3.5 If passwords/passphrases are used as authentication factors to meet Requirement 8.3.1, they are set and reset for each user as follows: • Set to a unique value for first-time use and upon reset. •

If passwords/passphrases are used as authentication factors to meet Requirement 8.3.1, they are set and reset for each user as follows: • Set to a unique value for first-time use and upon reset. •.

5
artefacts
2
held by a system
0
at each review
moderate
to go live
Identity provider / directory
where the evidence lives
teal = a system already holds it · olive = produced at each review

system holds itEvidence a system already holds

  • Configuration forcing a change immediately after first use · Identity provider / directory
  • Records or configuration showing the delivery method for the initial value · Identity provider / directory

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Procedures for setting and resetting passwords or passphrases · Policy repository / GRC workspace
  • Evidence each initial and reset value is set to a unique value rather than a standard or predictable one · Policy repository / GRC workspace
  • Observation of security personnel performing a reset, showing both elements applied · Policy repository / GRC workspace

First move

Start with the 2 of 5 artefacts that already live in a system (Identity provider / directory); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

8.3.4 Invalid authentication attempts are limited by: • Locking out the user ID after not more than 10 attempts. • Setting the lockout duration to a minimum of 30 minutes or until the user's identity · 8.3.6 If passwords/passphrases are used as authentication factors to meet Requirement 8.3.1, they meet the following minimum level of complexity: • A minimum length of 12 characters (or IF the system does not support 12