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×
Desktop Security
security advisory vulnerability
security advisory vulnerability GNOME is officially shortening its standard vulnerability disclosure window from 90 days to 30 days, a change that impacts upstream maintainers, downstream Linux distributions, and system administrators in how they handle software vulnerabilities. The policy shift, announced by long-time security coordinator Michael Catanzaro , addresses modern software patching realities and a growing influx of automated submissions. . Because GNOME is the default desktop environment on several major Linux...
Jul 21, 2026
Security Vulnerabilities security advisory moderate
security advisory moderate For organizations that run a self-hosted Git platform, it’s no longer just about hosting static code repositories. Today, Git servers are responsible for deployment pipelines, API tokens, SSH keys, package repositories, and the automation scripts that push code directly. Confirm that the upgrade addresses known vulnerabilities but also provides production environments. . That makes them trusted systems within the development environment and attractive targets for attackers looking to move...
Jul 20, 2026
Server Securitydata privacy automation
data privacy automation Every system admin has lived through the same Monday morning ritual. A queue of forty tickets, half of them password resets, permission errors, or disk space warnings that any experienced technician could resolve in under two minutes. The other half require actual judgment. For years, automation promised that software would eventually sort the two apart on its own. That promise is now being tested in production Linux environments. . Early results are reshaping how IT teams think about tier-1...
Jul 17, 2026
Privacydata collection automation
data collection automation You're running a web scraping project to collect pricing data from e-commerce sites. You set up a pool of datacenter proxies, launch your scripts, and within minutes — banned . CAPTCHAs everywhere. Your data pipeline stops before it really begins. . It's a frustrating scenario that plays out daily in ad verification, market research, and multi-account management. The website doesn't know you're doing legitimate research or monitoring. It just sees traffic coming from IP ranges it recognizes as...
Jul 17, 2026
Security Trends security advisory social engineering
security advisory social engineering Business Email Compromise used to be a numbers game — mass-blasted emails, broken English, an obvious "URGENT WIRE TRANSFER" subject line. That era is over. Generative AI has turned BEC into a tailored, low-noise operation that mimics writing style, voice, and even video presence. This piece looks at what's actually changed under the hood, what defenders are testing in response, and why so many organizations are still structurally unprepared for it. . The Infrastructure Problem Nobody Wants to...
Jul 17, 2026
Refine news
X Clear Filters
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?
Trending News
Loading...
Explore Latest Linux Security news
We found 2 articles for you...
83
security flawcybercrimedigital certificatesBit9 Breach Highlights Critical Security Flaws and Vendor Accountability
By confessing that its mistakes led to security breaches at three customers, Bit9 has sparked debate over whether the industry is ready to block hackers that see vendors as the door to other companies. . Bit9 disclosed last week that cybercriminals stole digital code-signing certificates from its computers and then used them to drop malware in the systems of three unidentified customers. The vendor acknowledged that the theft occurred on computers that it had failed to protect with its own product, which allows only software on a whitelist to run. The link for this article located at CSO is no longer available. . Bit9's revelation of a breach uncovers serious flaws in cybersecurity protocols and vendor responsibility.. Bit9 Breach, Cybercriminal Activity, Digital Certificates, Malware Incidents, Security Accountability. . LinuxSecurity.com Team
Feb 12, 2013
•
Hacks/Cracks
78
risk managementsecurity practicesbug fixesExamining Vendor Responsibilities in Security Bug Management
In last week. The reader wrote to say that his company often sits on security bugs until they are publicly announced or until at least one customer complaint is made. Before you start disagreeing with this policy, hear out the rest of his argument. The link for this article located at InfoWorld is no longer available. . Vendors delaying security bug fixes until public scrutiny poses ethical issues, prioritizing reputation over user safety and eroding trust in digital products. Vendor Accountability, Risk Management, Bug Fix Strategies. . LinuxSecurity.com Team
May 14, 2007
•
Vendors/Products
78
IT securitysoftware liabilityvendor accountabilityBruce Schneier Advocates Software Vendor Accountability for Security
Software companies should be made liable for the security problems that arise in their products, according to security guru Bruce Schneier. In a presentation at the LinuxWorld OpenSolutions Summit, the BT Counterpane CEO said that this was the only way to help improve IT security, the effects of which were currently taken for granted. . By modifying the cost-benefit analysis and giving greater IT security responsibility to software companies through liability assignment, security could eventually be improved, he said. "All I need is for the cost of doing the bad [work] to increase. This is why I favor software liability because it raises the costs of bad software." The link for this article located at Techworld is no longer available. . Through a revision of the risk-reward evaluation, technology firms can be made responsible for deficiencies in information technology security.. Software Liability, Vendor Accountability, IT Security. . LinuxSecurity.com Team
Feb 15, 2007
•
Vendors/Products
78
application securitysecurity standardsIT risk managementSun's Vendor Accountability Call for Enhanced Software Security
Sun's chief security officer last week said that vendors should bear legal responsibility for any security vulnerabilities found in their software, and should work harder to build more secure platforms and applications.. . .. Sun's chief security officer last week said that vendors should bear legal responsibility for any security vulnerabilities found in their software, and should work harder to build more secure platforms and applications. "Currently, it's a case of saying to firms, 'You pay, we promise you nothing, have fun.' But we need to put in place legal targets, perhaps for 2010 or 2015, and improve our methodology to provide much higher security standards if we are to accept liability," said Whitfield Diffie, Sun Microsystems chief security officer, speaking at the Information Security Solutions Europe (ISSE) event in Vienna last week. The call comes as a group of US users are proposing a class-action lawsuit against Microsoft because of Windows' vulnerability to computer viruses, which they claim could trigger "massive cascading failures" in global computer networks. Other experts at the event said that IT buyers share some responsibility for the increase in attacks via the internet. "Security has not had a big space in large companies in 2002 because it is difficult to make a clear business case to the chief finance officer for security, and that has to change," commented Michael Niebel, director general of the European Commission's information society, responsible for co-ordinating data security initiatives. The link for this article located at vnunet is no longer available. . The primary security officer at Sun highlights the vendors' obligation under the law to ensure their software is secure when dealing with weaknesses.. Software Liability, Vendor Accountability, IT Risk Management. . LinuxSecurity.com Team
Oct 14, 2003
•
Vendors/Products
82
database securityOracle databasevendor accountabilityDepartment Of Energy Mandates Enhanced Oracle Database Security
The department of energy has done something unusual for a federal agency. It has become an example of excellent cyber-security practice. It has done this by pressuring Oracle to elevate security in its 9i database product--in the process, taking software out . . . . The department of energy has done something unusual for a federal agency. It has become an example of excellent cyber-security practice. It has done this by pressuring Oracle to elevate security in its 9i database product--in the process, taking software out of the shadows of "as is" licenses and putting it in the spotlight of a government procurement action. DOE's action could begin a process that improves the security of the technologies available to the public and private sectors alike. To win this open-ended deal, Oracle promised to deliver its database in a secure configuration and took responsibility for the security of the software going forward. Future patches must be delivered quickly and cannot create new problems or vulnerabilities if Oracle wants to continue getting paid. It's the kind of vendor commitment that every enterprise merits but that only the $59 billion IT buying power of the federal government can effect right now. The link for this article located at eWeek is no longer available. . The energy sector establishes a benchmark by insisting on advanced safety measures from Microsoft for fortified cloud infrastructure.. Database Protection, Cybersecurity Standards, Government Procurement, Vendor Accountability. . Anthony Pell
Oct 07, 2003
•
Government
82
security researchsoftware securitycybersecurity legislationClarke's Visit to MIT: Software Security and Vendor Guidance
After releasing a draft of the National Strategy to Secure Cyberspace for comment in September, Clarke has embarked on a cross-country tour, soliciting feedback on the document and stumping for passage of the bill that would create the Department of Homeland . . . . After releasing a draft of the National Strategy to Secure Cyberspace for comment in September, Clarke has embarked on a cross-country tour, soliciting feedback on the document and stumping for passage of the bill that would create the Department of Homeland Security. During his most recent stop, at the Massachusetts Institute of Technology, audience members gave Clarke a wide range of suggestions for the strategy, with many of them centering on the theme of vendor responsibility for insecure software. Many people asked Clarke, chairman of the President's Critical Infrastructure Protection Baord, to consider recommending some form of regulation for the software industry as a way to spur vendors into writing more secure applications. Clarke resisted the idea, as he has in the past, saying that he'd rather rely on market forces and customer demand to weed out the careless vendors. One area where Clarke agreed that new legislation might be in order is security research. One audience member complained that the Digital Millennium Copyright Act and anti-hacking laws are preventing legitimate security researchers from publishing information on new vulnerabilities. The link for this article located at eWeek is no longer available. . After releasing a draft of the National Strategy to Secure Cyberspace for comment in September, Clar. releasing, draft, national, strategy, secure, cyberspace, comment, september. . Anthony Pell
Oct 17, 2002
•
Government
78
network securitydata protectionsecurity measuresEnhancing Network Security: The Role Of Vendor Accountability
Network security is not a technological problem; it's a business problem. The only way to address it is to focus on business motivations. To improve the security of their products, companies - both vendors and users - must care; for companies to care, the problem must affect stock price. The way to make this happen is to start enforcing liabilities.. . .. Network security is not a technological problem; it's a business problem. The only way to address it is to focus on business motivations. To improve the security of their products, companies - both vendors and users - must care; for companies to care, the problem must affect stock price. The way to make this happen is to start enforcing liabilities. The only way to get many companies to spend significant resources to ensure the security of their customers' data is to hold them liable for misuse of this data. Similarly, the only way to get software vendors to reduce features, lengthen development cycles and invest in secure software development processes is to hold them liable for security vulnerabilities in their products. The link for this article located at NW Fusion / Schneier is no longer available. . Cybersecurity necessitates organizational responsibility to foster genuine transformation and enhance information safeguarding protocols.. Business Accountability, Software Liability, Security Measures. . LinuxSecurity.com Team
Apr 25, 2002
•
Vendors/Products
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?
Trending News
Search Topics
Powered By
Linux Security - Your source for Top Linux News, Advisories, HOWTOs and Feature Releases
QUICK LINKS
subscribe to newsletters!
Like staying secure? So do we.
Sign up for updates, tips, and alerts!