Detecting Manually Compiled Network Daemons
Nessus plugin #33851 (Network daemons not managed by the package system) is a credentialed check that audits each of the server processes on the audited Linux system. If the running process is not part of a known system package, the plugin reports that the program is the result of a hand-compiled solution. Below is a screen shot of the plugin detecting a hand compiled httpd program:
Why should you avoid manually compiled programs on production systems?
System administrators sometimes argue that they prefer to use manually compiled programs rather than use a packaged version coming either from their OS vendor or their internal organization, as it gives them a better control of every compilation option, gcc optimization, etc... or just because they will claim they need a “newer” version of the daemon than what is provided by the Linux distribution they are using.
While this approach can make sense for a server running at home, the practice does not scale for the enterprise. Unless this is properly documented, using hand-compiled packages very often ties a given server to the administrator who compiled it, making him much harder to replace or second, makes that IT organization much less scalable.
Hand-compiling programs on production systems frequently opens the way to more hand-compiled packages. Due to the complex interdependencies of several open-source packages, installing the newest version of, say, a popular wiki, might involve compiling the newest version of PHP, which in turn will require the newest version of mysql-client, which may require upgrading several underlying libraries. This leads to a situation where upgrading the entire operating system becomes a daunting task, since Linux does always not guarantee backward binary compatibility. This leads the way to running production systems with outdated software years after they have been declared as "end of life" by their publisher. A full upgrade will inevitably lead to conflicts, where the system-provided Apache web server might compete with the locally compiled web server for port 80.
Good system administration practices dictate that one should deviate as little as possible from the environment provided by the operating-system vendor. While this might be frustrating sometimes, this approach guarantees you that a full-time security team will correct the security flaws found in the packages you use, that a full-time QA team made sure that your upgrade will be as painless as possible and it makes it much easier for your system administrators to recreate their environment on a clean system (without having to resort to copying / from one Linux system to another).
Finally, on commercially supported Linux distributions, hand-compiling several key programs may nullify the support contract.
For More Blog Posts Regarding Patch Auditing
The following previous blog posts deal with patch auditing:
Related Articles
Strengthening the Nessus Software Supply Chain with SLSA
April 16, 2024You know Tenable as a cybersecurity industry leader whose world-class exposure management products are trusted by our approximately 43,000 customers, including about 60% of the Fortune 500. But sometimes we like to give you a peek behind the curtain to share how we protect our own house against cyberattacks – and that’s what this blog is about. Today we’re sharing our experience adopting the supply-chain security framework SLSA, with the hopes that the lessons we learned will be helpful to you.
CISA and NSA Release Top 10 Cybersecurity Misconfigurations: How Tenable Can Help
October 19, 2023The NSA and CISA have released a joint cybersecurity advisory discussing the top 10 most common cybersecurity misconfigurations, and outlining ways to mitigate them. Read this blog to learn more and see how Tenable technologies can help discover, prevent and remediate these misconfigurations.
Cybersecurity Snapshot: The Latest on Supply Chain Security – SBOM Distribution, Open Source Flaws and a New Security Framework
April 21, 2023Check out what CISA says about the sharing of software bills of materials. Plus, why you should tread carefully with open source components. Also, the SLSA supply chain security framework is ready. In addition, security worries hold back enterprise IoT adoption. And much more!
Cybersecurity Snapshot: Prompt Injection and Data Disclosure Top OWASP’s List of Cyber Risks for GenAI LLM Apps
November 22, 2024Don’t miss OWASP’s update to its “Top 10 Risks for LLMs” list. Plus, the ranking of the most harmful software weaknesses is out. Meanwhile, critical infrastructure orgs have a new framework for using AI securely. And get the latest on the BianLian ransomware gang and on the challenges of protecting water and transportation systems against cyberattacks.
Active Directory Under Attack: Five Eyes Guidance Targets Crucial Security Gaps
November 21, 2024A landmark global report from cybersecurity agencies emphasizes 17 attack techniques against Microsoft Active Directory and cautions organizations to step up protections. In the first of our two-part series, we offer five steps you can take today to shore up your AD defenses.
Five Cyber Agencies Sound Alarm About Active Directory Attacks: Beyond the Basics
November 21, 2024A landmark global report emphasizes 17 attack techniques against Microsoft Active Directory and cautions organizations to step up protections. In the second of our two-part series, we take you beyond the basics to highlight three key areas to focus on.
- Security Frameworks