Overly broad permissions can turn one compromised account into a much larger security problem. Learn how to reduce unnecessary access, review privileges, and apply least privilege across modern Linux systems. Review Linux Privileges×

Alerts This Week
Warning Icon 1 514
Alerts This Week
Warning Icon 1 514

Stay Ahead With Linux Security News

Filter%20icon Refine news
X Clear Filters
X Clear Filters
View More

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Community Poll

Should Linux servers automatically install security updates?

No answer selected. Please try again.
Please select either existing option or enter your own, however not both.
Please select minimum {0} answer(s).
Please select maximum {0} answer(s).
/main-polls/157-should-linux-servers-automatically-install-security-updates?task=poll.vote&format=json
157
radio
0
[{"id":506,"title":"Yes \u2014 critical security patches should install automatically.","votes":0,"type":"x","order":1,"pct":0,"resources":[]},{"id":507,"title":"No \u2014 every update should be tested before deployment.","votes":0,"type":"x","order":2,"pct":0,"resources":[]},{"id":508,"title":"Only critical vulnerabilities should auto-install.","votes":0,"type":"x","order":3,"pct":0,"resources":[]},{"id":509,"title":"I patch when Reddit starts panicking.","votes":1,"type":"x","order":4,"pct":100,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350
bottom 200
Loading...

Explore Latest Linux Security news

We found 23 articles for you...
78

openSUSE Tumbleweed: SELinux Adoption Enhances Security Measures

openSUSE Tumbleweed is taking an innovative step toward improving security by transitioning from AppArmor to SELinux for new installations, which aligns with other major Linux distributions that already utilize its comprehensive policy enforcement capabilities. This move brings Tumbleweed closer to other major Linux distributions using this powerful, flexible policy enforcement method. . For us Linux security admins, this transition is an opportunity to increase system protection via SELinux's more detailed access controls. Still, it also introduces an additional learning curve as its configuration and management can be more complicated than AppArmor. Existing Tumbleweed installations will continue to run on AppArmor for greater flexibility and enable administrators to select an ideal time and date to switch. To help you understand and prepare for this transition, I'll discuss the security benefits of SELinux and the implications of this transition for Tumbleweed users. Understanding the Shift AppArmor has long been the default system security framework on Linux distributions, widely recognized for its ease of use and simplicity. However, openSUSE Tumbleweed developers recently opted for a more complex SELinux system instead because of its more refined approach to system protection. While AppArmor remains more accessible for beginners, SELinux introduces structured policies that give more precise control over how applications interact with each other and the system, making SELinux an integral component in environments where safety is paramount. Examining the Benefits of SELinux One of SELinux's primary attractions is its robust security policy framework, which defines how applications access files, devices, and other processes. Unlike AppArmor, which primarily focuses on file access, SELinux offers comprehensive policy-based control that extends to processes and users. This granularity enables administrators to enforce stricter security postures, minimizing the risk of unapprovedactions or breaches. Moreover, SELinux’s mandatory access control (MAC) replaces the traditional discretionary access control (DAC) model, adding another layer of defense. In an SELinux-enabled environment, even if an application is compromised, its ability to impact the rest of the system can be significantly restricted based on predefined policies. This makes SELinux an excellent choice for systems that require a heightened security level. The Learning Curve and Support As much as SELinux offers enhanced security features, it can also be quite complex for administrators switching over from AppArmor. To fully utilize its capabilities, transitioning admins must understand its terminologies, such as contexts, policies, and types. Writing and managing policies for SELinux can be challenging, but taking full advantage of its features is essential. Recognizing the learning curve associated with switching platforms, openSUSE community members have invested in creating detailed migration guides and documentation . These resources aim to assist admins through this transition with clear instructions and examples, helping them understand, configure, and troubleshoot SELinux on their systems. Furthermore, forums and community discussions provide invaluable real-world perspectives and advice from those who have already made the change. Flexibility for Current Users Existing Tumbleweed users will take comfort from AppArmor being supported, with existing installations not forcibly switching over to SELinux immediately. Administrators can operate their systems without immediate changes being required. This gives organizations more control in planning a smooth transition that fits their operational requirements, helping to avoid disruptions that might otherwise arise from sudden changeover. This dual-support approach caters to diverse infrastructure requirements. Admins can examine both security modules to see which best meets the needs of their environment - legacy systems that rely on AppArmor ornew deployments that might benefit more from SELinux. Preparing for the Transition Preparation for using SELinux requires first understanding its architecture and functionality. Unlike AppArmor's path-based security model, SELinux tags every system object with a security context that defines which processes can do what and which cannot, further granulating what processes can or cannot do at an object level. Administrators should expect to delve deep into understanding audit logs, creating custom policies, and addressing common concerns, such as understanding "denial" messages in their administration of SELinux systems. One practical method of becoming comfortable with SELinux is to begin with less critical systems. By activating the "permissive" mode for SELinux , administrators can observe which actions would be denied without actually enforcing restrictions, making troubleshooting and policy adjustments possible in a controlled fashion before moving the configuration into production environments. Our Final Thoughts: Is openSUSE Tumbleweed's Transition Part of a Broader Trend? OpenSUSE Tumbleweed's choice to adopt SELinux represents an ongoing trend toward more sophisticated security tools for Linux environments. As cyber threats continue to evolve, so must strategies and technologies designed to combat them. With its policy-driven framework, SELinux provides admins and users with an effective method to strengthen their defenses significantly. Security administrators looking to use SELinux should approach it as a challenge and an opportunity. Adopting it means expanding their technical knowledge beyond what may be familiar while at the same time strengthening their systems' security posture - potentially becoming an invaluable part of their professional toolbox. By joining forces with SELinux, openSUSE Tumbleweed affirms its dedication to offering users robust security options. While the transition may be challenging, administrators who make the leap will discover more powerful toolsthan ever to protect their systems and data - laying a strong foundation for future Linux security efforts. . For us Linux security admins, this transition is an opportunity to increase system protection via SE. opensuse, tumbleweed, taking, innovative, toward, improving, security, transitioning. . Brittany Day

Calendar%202 Feb 19, 2025 User Avatar Brittany Day Vendors/Products
209

Malware Scanning: Protect Linux Systems from Evolving Threats

As malware continues to evolve , it poses an ever-increasing threat to computing environments of all kinds - Linux systems included. While many may assume Linux is safe due to its robust built-in security features , such a mistaken assumption may open doors for exploitation. . Malware such as viruses, trojans, ransomware botnets, keyloggers, worms, and rootkits pose considerable threats, including data breach risks and potential operational disruption to organizations of any size. Thus, admins must remain vigilant, as even one infection could wreak havoc upon an organization's operations integrity, disrupting service delivery to customers or clients. Linux may seem secure at first glance; however, its inherent security can still be vulnerable. Unpatched software or improper configuration can expose systems to attacks like cryptojacking, where attackers use your resources for cryptocurrency mining without your knowledge, or DDoS attacks that severely disrupt operations. As a result of these vulnerabilities and risks, malware scanners such as ClamAV, Chkrootkit, or RKHunter help ensure a more secure operating environment by providing system administrators the means necessary for malware detection and mitigation so they can maintain stable and secure operating environments. In this article, we investigate practical tools for scanning Linux environments for malware, helping you develop reliable defense mechanisms against an ever-evolving threat landscape. Linux Malware Presents an Increasing Risk for Admins & Organizations Though Linux has historically been known as a highly secure operating system, Linux malware has seen an alarming uptick over recent years, raising significant concern among system administrators. Malware attacks targeting Linux systems have increased in both frequency and complexity. Backdoors and new malware families highlight the growing and evolving Linux malware threat. This trend presents Linux admins with an immense challenge. They must stay vigilant againstsuch complex and dangerous attacks while protecting their systems against newer and more dangerous threats that constantly emerge. Malware scanning is now essential for detecting and mitigating malware attacks before they cause extensive damage. Let's examine some excellent tools Linux admins can use for malware detection and elimination. Essential Tools for Scanning Linux Systems for Malware Admins and organizations need specialized malware scanning tools to mitigate Linux security risks effectively. ClamAV , for instance, is an open-source antivirus engine that detects various forms of malware. Its capabilities cover files, emails, and directories, providing system administrators with the flexibility they require in securing different environments. Its regularly updated virus database ensures maximum protection from newer threats. Chkrootkit is an invaluable tool for detecting rootkits—malware that embeds itself deeply within system processes to evade detection—by scanning for known signatures on system processes. It helps administrators quickly spot potential compromises that otherwise go undetected. Furthermore, its lightweight architecture and simple deployment make Chkrootkit an essential component of any Linux security toolkit. The Role of RKHunter in Vulnerability Assessment RKHunter enhances Linux systems' malware defenses with an integrative vulnerability assessment solution , offering comprehensive rootkit detection, system configuration evaluation, weak password scanning, and suspicious file change detection capabilities. It is invaluable in protecting systems by identifying and addressing vulnerabilities early before attackers can exploit them. It regularly executes to detect any possible malicious activities, helping uphold a robust security posture by effectively addressing vulnerabilities before outside forces can exploit them. Establishing an Effective Security Framework Implementing tools such as ClamAV, Chkrootkit, and RKHunter into any security framework isintegral. Regular scanning using these solutions can significantly lower the risk of malware infections, freeing organizations to focus on core operations without worrying about cyberattacks. However, these tools alone do not serve as sufficient defense. A comprehensive security strategy must incorporate user education, regular software updates , and best practices for secure system configuration to provide extensive protection from emerging threats. Let's examine some of these best practices in more detail. Best Practices for Protecting Against Linux Malware Training users on safe computing practices is vital in protecting Linux systems against malware. Making them aware of common dangers like phishing attacks or social engineering tactics empowers users to identify and avoid potential dangers. Additionally, implementing strict access control policies and creating strong password policies strengthen system defenses further. Regular software updates are also integral to maintaining robust security. By keeping all components current with updates, known vulnerabilities will be patched immediately, decreasing risk. Administrators should conduct routine audits to confirm that security measures are working properly and meet industry standards. Our Final Thoughts on Malware Scanning & Its Importance The increasing prevalence of malware in Linux environments underscores the necessity of employing effective malware scanning mechanisms. As sophisticated threats like cryptojacking and DDoS attacks advance and new attacks emerge, organizations cannot overlook the importance of strong security measures. By including robust tools like ClamAV, Chkrootkit, and RKHunter in their security strategies, system administrators can significantly improve their defenses against potential infections. Staying abreast of new threats and adapting security protocols are integral to maintaining Linux systems' integrity and security. An inclusive approach encompassing user education, software updates, andvigilant monitoring will ensure your systems can withstand emerging cyberattacks and threats. Organizations can protect critical assets while upholding operational continuity amid an ever-more hostile digital landscape by prioritizing security first and maintaining operational continuity over time. . Unix-based environments encounter vulnerabilities from malicious software such as worms, spyware, and backdoors. Discover essential detection utilities and methodologies.. Linux Malware, System Security Tools, Threat Detection Strategies, Anti-Malware Practices, Rootkit Prevention Software. . Anthony Pell

Calendar%202 Oct 10, 2024 User Avatar Anthony Pell Security Trends
83

TargetCompany: New Ransomware Variant Threatens ESXi Systems Security

Security researchers have recently identified an innovative Linux ransomware variant developed by the TargetCompany ransomware group. This variant targets ESXi environments and uses a custom shell script for payload delivery and execution, something not previously observed by TargetCompany operations. . To help you avoid falling victim to this ransomwareransomware , we will discuss the threat posed by this emerging variant and provide practical advice for protecting your systems against it. How Does This New TargetCompany Ransomware Work & Why Is It So Dangerous? TargetCompany ransomware has developed a Linux variant with distinct characteristics that make it stand out from previous variants. One key capability of this new variant is exfiltrating victim information onto two servers simultaneously, giving ransomware operators backup copies of any compromised files. Furthermore, this variant detects whether victim machines run VMWare ESXi environments. Targeting these environments allows threat actors behind TargetCompany to disrupt operations more effectively and increase the chances of receiving ransom payments. This variant employs a shell script for payload delivery and execution, indicative of the ransomware group's continuous development to use more sophisticated attack techniques. Targeting Linux environments aligns with an increasing trend of ransomware groups expanding attacks to critical infrastructure sites, thereby expanding victim numbers. Upon successful exploitation, the ransomware encrypts critical ESXi servers by appending ".locked" extensions to encrypted files and leaving a ransom note named "HOW TO DECRYPT.txt." Additionally, this variant uses a custom shell script to download and execute its payload while exfiltrating victim information across multiple servers. Such tactics pose significant difficulties for defenders when investigating incidents and responding accordingly. TargetCompany ransomware poses an extremely severe threat to organizations that rely onvirtualization servers as part of their core infrastructure. Encryption can result in significant operational disruption and financial losses for affected organizations, making it essential for them to take proactive measures against attacks of this nature. As ransomware evolves in tactics and capabilities, robust cybersecurity defenses must also evolve alongside it to protect sensitive data against any unintended access attempts. Practical Advice for Securing Linux Systems With ransomware groups like TargetCompany emerging as ever more threatening, Linux admins must actively secure their systems against potential attacks. Here are some concrete recommendations to improve the security posture of your environment: Implement Multifactor Authentication (MFA): Enabling MFA can help protect networks by deterring attackers from moving laterally within them and decreasing risk associated with unauthorized access to critical systems and data. Adhere to the 3-2-1 Backup Rule: Adherence to the 3-2-1 rule can help organizations recover data more easily after ransomware attacks. By creating three copies in two formats—with one stored offsite—they will ensure they can quickly restore files when necessary. Maintain a Proactive System Patch Management Strategy: Staying current with updates to operating systems and applications is crucial to avoiding attacks, so having an effective patch management protocol is essential in addressing vulnerabilities before they are exploited by adversaries. Adopt Endpoint Protection Solutions: Integrating endpoint protection solutions that detect and block malicious activities at the system level can significantly enhance the security posture of Linux environments. Perform Regular Security Audits and Vulnerability Evaluations: It is wise to conduct routine security audits and vulnerability analyses to detect and address potential weaknesses that could be exploited by ransomware threats. Linux admins can enhance their cybersecuritystrategy to strengthen the resilience of their systems against evolving threats, such as the TargetCompany ransomware variant targeting ESXi environments, by adopting these best practices into their cybersecurity strategy. Our Final Thoughts on Securing Linux Systems Against This New Ransomware Variant The TargetCompany ransomware group's new Linux variant targeting ESXi environments is yet another indicator of evolving tactics employed by threat actors to exploit critical infrastructure. Organizations must remain vigilant and strengthen their cybersecurity defenses against ransomware attacks to reduce the risk of falling victim. By employing proactive security measures, adhering to best practices, and staying aware of emerging threats in today's constantly changing cybersecurity landscape, Linux administrators can better secure their systems and data against sophisticated ransomware threats that pose constant danger. . Grasping the intricacies of TargetCorp's latest Linux ransomware iteration is vital for fortifying your infrastructure against forthcoming vulnerabilities.. Linux Ransomware, ESXi Protection, TargetCompany Threats, Cybersecurity Best Practices. . Anthony Pell

Calendar%202 Jun 06, 2024 User Avatar Anthony Pell Hacks/Cracks
210

Effective Techniques to Reduce Kernel Bugs in Linux Operating Systems

Linux admins and security practitioners face significant challenges in keeping their Linux systems secure amidst the constant threat of kernel bugs. Understanding and mitigating the vulnerabilities in the Linux kernel is essential in safeguarding your systems against exploits leading to compromise. Let's examine why kernel vulnerabilities are such a severe threat and mitigation strategies for protecting against them. . Why Are Linux Kernel Bugs Such A Severe Threat? How Can I Secure My System Against Them? The kernel is in a unique spot in the system, where even ordinary bugs can be transformed into vulnerabilities if exploited cleverly. Linux kernel developer Jonathan Corbet states, "In the kernel, just about any bug, if you're clever enough, can be exploitable to compromise the system." This statement raises important questions about the level of security that can be achieved in Linux systems and the measures required to protect them effectively. To address these concerns, Corbet suggests using long-term stable (LTS) kernel releases, which receive regular patches and fixes for identified vulnerabilities. He advises Linux admins and infosec professionals to ensure that their distributions run LTS kernel releases, as they provide a certain level of assurance against known threats. However, this approach has a caveat, as Corbet warns that LTS releases will no longer be supported for as long as they used to be. This change has long-term consequences, as it accelerates the phasing out of older kernel versions and emphasizes the need for regular updates to current versions. It is critical to highlight the Linux kernel developer community's immense efforts to maintain the kernel's security and stability . Corbet mentions the increase in first-time contributors, which indicates a vibrant and forward-moving community. However, he points out the critical issue of burnout among maintainers and long-time developers. Without adequate support, the risk of frustrated developers, deteriorating codequality, and increased security problems becomes a looming concern. Given these implications, companies must treat Linux work as a top priority and provide the necessary resources to support the community. Nearly all businesses depend on Linux. Ignoring this fact would be detrimental, as it could lead to compromised systems, data breaches , and financial losses. Regularly updating to the latest LTS kernel release and actively supporting the Linux developer community can go a long way toward maintaining system security. Our Final Thoughts on Protecting Against Linux Kernel Bugs This article aims to provide valuable insights into the challenges of keeping Linux systems safe from kernel bugs. The importance of proactive measures such as using LTS releases, supporting the developer community, and staying updated with the latest security patches must be emphasized. By critically analyzing the implications presented in this article, security practitioners can better understand the impact on their practices and make informed decisions to safeguard their Linux environments. . Protect your Linux system from kernel vulnerabilities with regular updates, minimal installations, security modules, and active monitoring for potential threats. Kernel Bug Management, System Protection Strategies, Linux Kernel Security. . Dave Wreski

Calendar%202 May 18, 2024 User Avatar Dave Wreski Security Vulnerabilities
79

Linux Kernel 6.7 Updates: Enhanced Security and Hardening Configuration

The release of Linux kernel 6.7 introduces various security features and updates. One notable improvement mentioned in the article is the update to the crypto subsystem, which focuses on reducing the use of insecure and obsolete crypto hashing algorithms. Removing SHA1 support for signing kernel modules or importing X.509 certificates and eliminating MD4 and MD5 hashing raises important security concerns. This highlights the Linux community's commitment to staying ahead of emerging threats and ensuring the robustness of the platform. . Another significant update is introducing the "hardening.config" profile, intended to help build a security-hardened kernel with predefined secure defaults. By activating this configuration, Linux admins can implement kernel memory permission enforcement, address space layout randomization, buffer length bounds checking, and other security tunables. This feature saves time and effort for system administrators, as they don't have to tweak all these settings manuall y. Landlock is an unprivileged application sandboxing feature that now expands its capabilities beyond file-system access controls to include networking. As an LSM, Landlock introduces access rights for TCP socket bind() and connect() system calls, allowing for more granular control over communications. This update opens up possibilities for tighter network security controls and can benefit systems that require strict network restrictions. One aspect that raises questions is the PE header generation changes in the x86/boot module. The restructuring of the PE header aims to improve system security, but we need to consider the long-term consequences. Will there be compatibility issues with existing systems and tooling? Will this change impact the performance of the Linux kernel on Windows systems? These are potential implications that need to be thoroughly evaluated. Additionally, support for NVIDIA's GSP firmware in the Nouveau open-source graphics driver, enhancements to file systems like Btrfs, andupdates to file systems such as EXT4, F2FS, and exFAT are notable changes in the 6.7 kernel. Including new hardware support, architecture improvements, and updates to security measures like AppArmor demonstrates the continuous evolution of the Linux kernel. From the perspective of security practitioners, the release of Linux kernel 6.7 emphasizes the importance of keeping the operating system up to date . As security threats evolve, staying on older kernel versions, like the deprecated Linux 4.14 series, can expose systems to potential vulnerabilities. Linux admins and sysadmins should consider upgrading to newer long-term supported kernels with extended support and the latest security enhancements. Our Final Thoughts on the Linux Kernel 6.7 Release In conclusion, the release of Linux kernel 6.7 brings significant security improvements that cater to the needs of Linux admins, infosec professionals, and internet security enthusiasts. The updates to the crypto subsystem, the introduction of the hardening configuration profile, and the expansion of Landlock's capabilities demonstrate the Linux community's continuous effort to enhance security. However, it is essential to consider the long-term consequences of changes like the PE header rework and ensure compatibility while striving for better security. Overall, staying up to date with the latest kernel versions and security features is crucial for security practitioners in maintaining a secure and robust Linux environment. Be sure to subscribe to our Linux Advisory Watch newsletter to stay updated on the latest Linux kernel vulnerabilities and mitigations impacting your systems. . The release of Linux kernel 6.7 introduces crucial enhancements in security measures and safeguards aimed at maintaining system reliability.. Linux Kernel 6.7, Security Features, Hardening Configuration, System Security, Crypto Updates. . Dave Wreski

Calendar%202 Feb 11, 2024 User Avatar Dave Wreski Security Projects
83

Protecting Devices from UEFI Exploits: Mitigating LogoFAIL Issues

A collection of new security vulnerabilities called LogoFAIL has been discovered hiding with the Unified Extensible Firmware Interfaces (UEFI) that we use for booting almost all modern computing devices. Linux or Windows, ARM or x86, it doesn't matter -- they're all vulnerable to these flaws! . This threat has been lurking in systems for decades. What makes it particularly concerning is the wide range of impacted consumer and enterprise-grade computers. The core of LogoFAIL is its exploitation of logos displayed on the device screen during the early boot process while UEFI is still running. Exploits occur during the earliest stages of the boot process. Hence, the attacks bypass UEFI defenses, such as Microsoft Secure Boot and Intel Secure Boot, that are meant to block bootkit infections. If you are vulnerable, you must make sure no one can get into the device in the first place. This requires patching your operating system and programs against all known attacks. Firmware fixes are on the way, but in the meantime, lock down your systems as much as you can so a LogoFAIL attacker doesn't gain a foothold. I found the article linked below helpful in understanding the specifics of this exploit and how to secure my systems against it. Check it out! . Protect your devices against LogoFAIL attacks targeting UEFI vulnerabilities in boot processes and ensure robust security practices.. LogoFAIL attacks, UEFI vulnerabilities, boot sector security, system hardening. . LinuxSecurity.com Team

Calendar%202 Dec 14, 2023 User Avatar LinuxSecurity.com Team Hacks/Cracks
72

IPFire 2.27 Core Update 173: New Modem Support and Enhanced Protection

IPFire 2.27 Core Update 173 is out to introduce support for 4G and 5G modems that use the QMI interface. . IPFire project’s Peter Müller announced today the release and general availability of IPFire 2.27 Core Update 173 as the first update to this open-source hardened Linux firewall distribution for routers and firewalls in 2023. Powered by the long-term supported Linux 6.1 LTS kernel series, IPFire 2.27 Core Update 173 is here to introduce support for the QMI (Qualcomm MSM Interface) a proprietary interface and the ability to interact with 4G and 5G modems that use the QMI interface. The new Linux 6.1 LTS kernel brings improved hardware support and security improvements for IPFire users, such as Landlock support, protection against direct memory access via malicious PCI devices on AArch64 (ARM64) systems, protection against cold boot attacks by allowing the firmware to wipe all memory when rebooting, and much more. The link for this article located at 9 to 5 Linux is no longer available. . OPNsense 23.1 introduces improved firewall features and dynamic routing capabilities, powered by FreeBSD 14.0.. IPFire Firewall, Linux Kernel 6.1, Network Security, Open Source Firewall. . Brittany Day

Calendar%202 Feb 28, 2023 User Avatar Brittany Day Firewalls
215

Ubuntu 22.10: GNOME Device Security Panel Excluded From Control Center

Coming with GNOME 43 is a "Device Security" panel within the GNOME Control Center. While intended to help ensure their system is protected, Ubuntu isn't onboard with this Device Security functionality yet and has stripped it out from their GNOME build for Ubuntu 22.10. . The GNOME Device Security area warns users if Secure Boot is disabled and other platform-related security settings that are less than ideal. This GNOME integration has been worked on by Red Hat engineers along with the lower-level platform checks tied into Fwupd and the like. Eventually the hope is this Device Security area could assist users in improving their security settings beyond just warning them over the current system state. This week Ubuntu 22.10's GNOME Control Center package (gnome-control-center) package patched out the Device Security panel entirely. The link for this article located at Phoronix is no longer available. . The latest security control center in GNOME is missing from Ubuntu 22.10, affecting user access to crucial system safeguarding functionalities.. GNOME Device Security, Ubuntu Security, Control Center Features, Secure Boot Status. . Brittany Day

Calendar%202 Sep 11, 2022 User Avatar Brittany Day Desktop Security
News Add Esm H340

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Community Poll

Should Linux servers automatically install security updates?

No answer selected. Please try again.
Please select either existing option or enter your own, however not both.
Please select minimum {0} answer(s).
Please select maximum {0} answer(s).
/main-polls/157-should-linux-servers-automatically-install-security-updates?task=poll.vote&format=json
157
radio
0
[{"id":506,"title":"Yes \u2014 critical security patches should install automatically.","votes":0,"type":"x","order":1,"pct":0,"resources":[]},{"id":507,"title":"No \u2014 every update should be tested before deployment.","votes":0,"type":"x","order":2,"pct":0,"resources":[]},{"id":508,"title":"Only critical vulnerabilities should auto-install.","votes":0,"type":"x","order":3,"pct":0,"resources":[]},{"id":509,"title":"I patch when Reddit starts panicking.","votes":1,"type":"x","order":4,"pct":100,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350
bottom 200