How to ensure that ssh jump host users are not using previous password set to meet security compliances such as PCI DSS , SOX, HIPAA , NIST , MAS, SOC2, FFIEC, NERC CIP , ISO 27001

To meet various security compliance like PCI DSS 3.2, SOX , HIPPA , NIST , MAS , FFIEC , SOC2, NERC CIP, ISO 27001 users should not be allowed to set a password that has been previously used. To ensure that users are using a different password from the previous ones when they reset their password, set the variable Settings->General->Security->Password/ Security Code Retries, so that when a user changes his password, the ssh jump host does not allow the last n passwords, n = number of password retries in settings plus one.

So you may set the number of password retries in settings to 2 to disallow the usage of the last 3 passwords.

password-retry

0 (0)
Article Rating (No Votes)
Rate this article
    Attached Files
    There are no attachments for this article.
    Related Articles RSS Feed
    Configure ssh timeout in ssh gateway
    Viewed 1806 times since Fri, Dec 1, 2017
    How to change the private key in use and change the default public key in use?
    Viewed 1941 times since Fri, Dec 1, 2017
    Set SSH User Expiry
    Viewed 725 times since Thu, Sep 20, 2018
    encryption type used for securing users ssh logs in ezeelogin
    Viewed 1139 times since Thu, Jun 15, 2017
    record rdp session
    Viewed 516 times since Thu, Dec 6, 2018
    How do i restrict commands that a user can execute in ssh in ezsh shell ?
    Viewed 2072 times since Wed, Jun 14, 2017
    Can I use Google 2FA, Yubikey , DUO simultaneously?
    Viewed 2077 times since Thu, Dec 14, 2017
    Enable Google reCaptcha
    Viewed 193 times since Fri, Feb 1, 2019
    Configure DUO 2FA in Ezeelogin SSH jumphost
    Viewed 1619 times since Thu, Nov 23, 2017
    How to stream the ssh sessions in real time?
    Viewed 2523 times since Wed, Nov 22, 2017