- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Auditing SYSUAF modifications to the SYSTEM ac...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2009 09:36 AM
тАО03-03-2009 09:36 AM
Re: Auditing SYSUAF modifications to the SYSTEM account
$ ANALYZE/AUDIT/EVENT=SYSUAF/SELECT=UAF_SOURCE=SYSTEM/FULL
The /SELECT=UAF... keywords have not been documented since VMS 6.2 but they still work the same way they always did. By that I mean /SELECT=UAF_MODIFY= never worked right, but /SELECT=UAF_SOURCE= seems to work fine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2009 10:46 AM
тАО03-03-2009 10:46 AM
Re: Auditing SYSUAF modifications to the SYSTEM account
That sounds like a good addition to Parsec's Undocumented VMS Features page at http://www.parsec.com/openvms/undocumented.php
- perhaps you can get them to add it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2009 03:33 AM
тАО03-04-2009 03:33 AM
Re: Auditing SYSUAF modifications to the SYSTEM account
Almost. This still allows to copy the sysuaf, modify it, delete the original and put the copy back in place. And then finish with adding the acl again.
I would add the delete to the acl too.
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2009 06:07 AM
тАО03-04-2009 06:07 AM
Re: Auditing SYSUAF modifications to the SYSTEM account
If not, the user can remove the ACL, modify the file and put it back again. And monitor audit entries of course. Otherwise it's logged but nobody knows.
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2009 06:56 AM
тАО03-04-2009 06:56 AM
Re: Auditing SYSUAF modifications to the SYSTEM account
That's a mechanism specifically intended for this situation.
Two users, both of which must be present to perform the privileged action(s).
As for all the auditing and accounting, that's comparatively insecure around privileged users; if you're privileged (and reasonably competent at DCL) it's usually easy to get rid of that stuff or (if you're somewhat better at OpenVMS and at your nefariousness) at covering your tracks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-06-2009 01:46 AM
тАО03-06-2009 01:46 AM
Re: Auditing SYSUAF modifications to the SYSTEM account
I like the two password setting for the system account, that will help.
I think it's going to end up being most of the suggestions on here to get a comprehensive audit trail.
Obviously there is the priv user issue being able to cover their tracks, but from a PCI-DSS standpoint, we're auditing what we need to, so that's good enough.
There's always got to be some element of trust with your priveledged users, otherwise the system just wouldn't work, you could spend months/years going to the nth degree of security access.
- « Previous
-
- 1
- 2
- Next »