A localized space to talk about EPM, specifically for Unix & Linux.
Recently active
Greetings! I'm Phillip Lehner, the Senior Director of Education at BeyondTrust, and I'm thrilled to lead our efforts in delivering exceptional learning experiences. I'm excited to share how we're elevating your journey with a new, streamlined method of accessing training: Success Included with BeyondTrust University. At BeyondTrust University, we believe our customers deserve nothing short of excellence in the tools they use. That’s why we’ve launched 'Success Included' — to elevate your learning experience and ensure you achieve success with BeyondTrust’s solutions. Success Included is an education program that makes foundational knowledge accessible to customers at no additional cost. It features easy-to-follow, self-paced eLearning courses that empower system administrators to configure and manage BeyondTrust products using industry best practices. Our goal is to equip learners with the knowledge needed to maximize the value of their investment with BeyondTrust. Because your
EPM-L and EPM-UL have extensive ability to log privilege access and sessions. You can use the pbsh and pbksh to log and record unprivileged session, however the problems with that are twofold. Firstly, the pb-shell environments are incompatible with Advanced Control and Audit rules, and secondly, the shell environments are out-of-date compared to modern shell environments. They lack modern features like command argument completion, wildcard completion, directory history stack and others due to their age. Maybe a modern shell environment like bash, zsh or fish will get integrated into the product.The first issue is easily taken care of by normal DAC file system permissions, they are unprivileged users after all. The second issue is more complex and could be solved by just forcing people to use pbksh, but there is a method of logging which is secure, and respects the users choice of shell. That is by using a combination of PAM (the Linux Pluggable Authentication Modules) and auditd.Audit
Hi Team, I am trying PMUL and want to ask if i can block any standard command without pbrun. Example:I want to block the standard ping but without using pbrun ping.ping 8.8.8.8 should be rejected. But for now, i can only reject if user executed pbrun ping 8.8.8.8.Can we do that in PMUL? (right now, i am using role-based policies)I have a case from end-user, they want to block all kind of command except 2 or 3 specific commands.Thanks
The following articles were published last week. New Knowledge Base Articles: KB0021526 - Endpoint Privileged Management for Unix Linux licensing FAQs KB0021758 - LDAP binding to Active Directory on EPM-UL fails with error - pbrun23.1.2-04[947719]: 3005 Request ended unexpectedly KB0021817 - Errors assigning EPM-UL license key - 3802.6 This host is not the Primary License server or 6025.78 Host is incorrect in the Registry Name Service Cache database KB0021830 - Error when trying to profile BIUL or EPM-UL servers "BIUL ERROR: sudo: sorry, you must have a tty to run sudo"
After the installation of BIUL 23.1 we are seeing below errors in logs. This is a custom installation of BIUL 23.1 on master server. pbksh.logDec 8 19:06:48 [368244] 1171 pbSSLAtomicWrite error 32: Broken pipe pbmasterd.logDec 8 19:18:24 [369488] 3018 LIBMANGLE_mangleRecvStart failure on fd 4. No data returned
The following articles were published last week. New Knowledge Base Articles: KB0021661 - EPM Unix & Linux (UL) supported versions lifecycle and OS compatibility information KB0021749 - Client registration or REST call from EPMUL failing in an environment with https_proxy configured "Failed to call REST API - HTTP returned error"
The following articles were published last week. New Knowledge Base Articles: KB0021713 - pbuninstall uses high amount of memory and CPU and is not behaving correctly on Ubuntu18 KB0021714 - User assigned to a Role Based Policy in EPM-L is unable to use the policy KB0021725 - 6101.53 Error accessing Message Router statistics error in msgrouter and pb.eventlog is not logging in eventlog
Hello! Last month our Chief Customer Officer, Sean Cashin, provided some information on our upcoming dedicated user community. I’m excited to announce that BeyondTrust launched our new BeeKeepers community on Monday, September 16th! Why BeeKeepers?The name BeeKeepers was born from the idea to protect and secure privileged identities, along with the paths those identities follow in order to gain privilege, aka Paths to Privilege. What does the BeeKeepers name mean to us?Imagine a company’s data and secrets as the honey in a beehive. BeeKeepers take care of the hive, protecting the honey and honeybees, from predators the live to steal the honey, damaging and destroying the hive. Now imagine you, BeyondTrust customers, IT Admins, SOC professionals, and CISOs are the BeeKeepers! And honeybees are identities – human and non-human – continuously travelling along their flight paths, the Paths to Privilege, collecting pollen and making more honey. BeeKeepers protect the honeybees’ path and con
The following articles were published last week. New Knowledge Base Articles: KB0021676 - Error: pbguid Exiting failed to read settings file /etc/pb.settings - general SQL error "
How to open a case for Endpoint Privilege Management for Linux (cloud)? The support Console includes only Mac & Windows option and there is no Linux option.
One of the things that becomes a big issue for customers, especially when we move to automated build processes, is “how do you allow a user to add/remove users or groups, but NOT allow them to add ‘root-capable’ accounts, or elevate their own access?” As has been well discussed in other forums such as OWASP: https://cheatsheetseries.owasp.org/cheatsheets/Input_Validation_Cheat_Sheet.html - input validation is very difficult to do properly, especially if all you’re doing is checking “are these options included in the input?” A lot of customers will simply try to grep the options for dangerous flags or mis-uses, but as documented above, this is not safe - a re-implementation of the commandline parsing is typically required for security.For a customer this month, we built a “pbuseradd” function that re-implements the “useradd” commandline validation, but adds protections such as “you cannot create a new backdoor root user”. One of the features we use to validate these backdoors is the F
Hello All,Leaning into the cliché, it’s hard to believe the year is half over already. As I'm sure is true for many of you, this has been a year of hard work and big changes at BeyondTrust. At the beginning of the year, I stepped into the role of Chief Customer Officer and welcomed both Mike Machado and Brett Thiess to the team as CISO and CMO, respectively. We also welcomed Ron Nissim and his team into the BeyondTrust family with the acquisition of Entitle, expanding BeyondTrust’s stance as an Identity Security leader! As the CCO, my passion and focus are on ensuring that our customers not only adopt but get real value from our products – securing their Identity landscape, minimizing the risk of threat actors, and limiting the blast radius of any incidents. Your thoughts and experiences are a key piece of guidance for us; from your NPS responses and feedback on your interactions with teams like support and services, to your engagement on changes we’ve made to products, we value the fe
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
