Change temporary passwords of third parties
Summary​
The system must force the change of temporary passwords, which are generated by a third party, after their first use.
Description​
Temporary passwords are often harder to remember and shared over systems whose future integrity may not be guaranteed by the system that created them. Furthermore, there is no control over who has access to the secret besides the third party. Therefore, the passwords should be changed after their first use.
Supported In​
This requirement is verified in following services
| Plan | Supported |
|---|---|
| Machine | 🔴 |
| Squad | 🟢 |
References​
- NIST 800-63B-6_1_1. Binding at enrollment
- MITRE ATT&CK®-M1027. Password policies
- CMMC-IA_L2-3_5_9. Temporary passwords
- HITRUST CSF-01_d. User password management
- HITRUST CSF-05_k. Addressing security in third party agreements
- HITRUST CSF-09_g. Managing changes to third party services
- FedRAMP-IA-5_3. Authenticator management - In-person or trusted third-party registration
- FedRAMP-PS-7. Third-party personnel security
- OWASP MASVS-V4_5. Authentication and session management requirements - Password policy
- NIST 800-171-5_9. Allow temporary password use for system logons with an immediate change to a permanent password
- SIG Core-H_3_1_8. Access control
Vulnerabilities​
Search for vulnerabilities in your apps for free with our automated security testing! Start your 21-day free trial and discover the benefits of our Continuous Hacking Machine Plan. If you prefer a full service that includes the expertise of our ethical hackers, don't hesitate to contact us for our Continuous Hacking Squad Plan.