For many privileged interfaces there can be multiple users that need to work over a single interface at the same time. Two classic examples are operating system interfaces and database administration interfaces. It is common for multiple system administrators (SAs) to be logged into an operating system performing different activities concurrently just as it is for database administrators (DBAs) to be logged into administrative DB sessions at the same time. The number of “concurrent” users can vary a lot, but in some cases exceed 50 concurrent users.
The problem is that in these scenarios it is extremely difficult to manage this concurrent activity effectively and to generate accurate information about each user as an independent set of records. More and more, organizations need real-time visibility over these concurrent user sessions with transparency, visibility, control and forensic records for each – just like ConsoleWorks has always provided for single-user sessions. However, even with ConsoleWorks managing multiple users like we would, single user sessions have historically been a real challenge.
ConsoleWorks provides the capability for multiple users to access the same privileged interface in their own private session. Multi-session creates private user sessions on demand to interfaces like operating systems and databases. User activity is recorded by individual and by all activity on a given connection target. Sessions are also private for users, no matter how many users need to access an interface at the same time. Individual (private) sessions are created as needed and then closed when work is complete to mimic the real nature of how people perform their work.
This capability extends ConsoleWorks security and compliance to multiple, concurrent users accessing the same target for different reasons – a common occurrence on operating systems, databases, and other IT assets.
