Skip to content

BSC audit log record must contain login #2302

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

Open
antonkovalenko opened this issue Feb 28, 2024 · 0 comments
Open

BSC audit log record must contain login #2302

antonkovalenko opened this issue Feb 28, 2024 · 0 comments
Assignees
Labels
area/blobstorage BlobStorage issues

Comments

@antonkovalenko
Copy link
Member

antonkovalenko commented Feb 28, 2024

It was discovered that some records in blob storage controller audit log don't contain login info of a user who initiated a request.

It's important to always in every possible case to log login of a user, who initiated a request to the system that caused changes in BSC.

DoD:

  1. All use-cases that cause BSC changes are listed in the comments
  2. Measures to log username of a subject who caused changes are listed, some are converted to separate issues
  3. IP address of YDB client is logged as well
  4. All cases are covered and username could always be found in BSC audit log
@antonkovalenko antonkovalenko added the area/blobstorage BlobStorage issues label Feb 28, 2024
robot-piglet pushed a commit that referenced this issue May 27, 2024
robot-piglet pushed a commit that referenced this issue Jun 4, 2024
…s version is used.. #2302

0843dd6fab7789634d13bdde50586f8d122288fa
This was referenced Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/blobstorage BlobStorage issues
Projects
None yet
Development

No branches or pull requests

2 participants