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

New (or Modified) Technique: User Session Monitoring #363

Open
vikhari opened this issue Mar 1, 2025 · 1 comment
Open

New (or Modified) Technique: User Session Monitoring #363

vikhari opened this issue Mar 1, 2025 · 1 comment

Comments

@vikhari
Copy link

vikhari commented Mar 1, 2025

User Session Monitoring

A potential place for this concept is under Platform Monitoring, though maybe this can belong under another Detect area.

Digital Artifacts

  • Log
  • Network Traffic (something that encompasses GUI desktop capture like Web Network Traffic)

Definition

User sessions can be monitored in a live or retroactive manner in a number of ways, including authentication (login/logoff), system logs, keylogging/command history, live user behavior analytics, and screen capture (video or screenshots).

How it works

Some PAM (and other types of) tools can capture user actions via the methods described in the definition to be able to monitor privileged user activities, such as graphically recording RDP sessions. This may be done for auditing purposes when a privileged user's session involves actions that indicate misuse, unintentional introduction of vulnerability, etcetera. It also may be performed to catch threat actors in-the-act without their knowledge, though this is an edge use case. In general the concept of monitoring also involves non-repudiation. For PAM tools that perform graphical capture this often is done by having network traffic routed through a proxy node where that node has the resources to handle the recording process. For PAM tools that perform log and command monitoring although data can be shipped to a SIEM the tools themselves also typically have interfaces for filtering activity, allowing PAM administrators to terminate sessions that seem suspicious.

Considerations

When using this feature the following should be considered:

  • Keylogging features used for defensive purposes can also be used offensively if compromised
  • Video screen capture is very expensive in terms of storage, bandwidth, and potentially CPU/GPU resources
  • (more to come through discussions on this issue)

References

There are other examples of this but here is one: https://docs.delinea.com/online-help/secret-server/session-recording/session-rec-overview.htm

@vikhari
Copy link
Author

vikhari commented Mar 1, 2025

Potential related issues:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant