Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing a Password is audited #1548

Closed
jvanderhoof opened this issue May 15, 2020 · 0 comments
Closed

Changing a Password is audited #1548

jvanderhoof opened this issue May 15, 2020 · 0 comments

Comments

@jvanderhoof
Copy link
Contributor

jvanderhoof commented May 15, 2020

As a security administrator, I want to know when users attempt to change their passwords so that I can detect any suspicious behavior.

GIVEN a running Conjur instance
WHEN I change my password with an invalid password 1
THEN I see an unsuccessful password change audit event 2

AND WHEN I change my password with a valid password 3
THEN I see a successful password change audit event 4

Notes
Conjur does not currently support changing another user's password. The only way to "fail" when setting a password is to attempt to change a password to something that does not meet the complexity requirements.


1 Change the admin user's password to a password that does not meet the complexity requirements:

$ curl -k -X PUT --data password --user admin:ADmin123!!!! \
http://localhost:3000/authn/cucumber/password

2 Unsuccessful "Change Password" audit event should follow the Audit Event convention. Before we implement, let's get agreement on the format. A possible format could be:

  • subject@43868
    • user: cucumber:user:admin
  • auth@43868
    • user: cucumber:user:admin
  • action@43868
    • result: failure
    • operation: update
  • MSGID: password
  • MESSAGE: "cucumber:user:admin failed to update password for cucumber:user:admin due to complexity requirements"
  • LEVEL: "notice"

3 Change the admin user's password to a password that meets the complexity requirements:

$ curl -k -X PUT --data ADmin123!!-new --user admin:ADmin123!!!!
http://localhost:3000/authn/cucumber/password

4 Successful "Change Password" audit event should follow the Audit Event convention. Before we implement, let's get agreement on the format. A possible format could be:

  • subject@43868
    • user: cucumber:user:admin
  • auth@43868
    • user: cucumber:user:admin
  • action@43868
    • result: success
    • operation: update
  • MSGID: password
  • MESSAGE: "cucumber:user:admin updated password for cucumber:user:admin"
  • LEVEL: "notice"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment