Audit Linux privileges now to limit compromise, escalation, and system-wide damage. Review Linux Privileges×
The financial services industry is well ahead of other markets when it comes to making secure coding a reality, but other firms, including smaller independent software vendors, aren't making the effort, according to Ryan Berg, a senior architect of security research for IBM. The CEO within an organization can make the difference, Berg said. . If the CEO makes a commitment to building more software development improvements and shows that commitment in the budget, the entire software development process could gain more positive changes, Berg said. In this interview, Berg outlines the threat landscape, explains how companies can make incremental changes to their software development processes and which models organizations can turn to for guidance. We hear so much about the need for companies to focus on secure software development. Why should software security be a priority? Ryan Berg: About 12 years ago, I worked at a company called BBN and at the time one of the things we introduced at BBN was the first managed firewall services. So back 12 years ago, one of the greatest threats to an organization was access to the network. That's what everyone was concerned about. Firewalls came around and you needed an advanced degree just to configure a firewall. But one of the biggest requests that came in to our network operation center was: "Can you open this port for me?" As more and more application services came onto the network, they tried to open the firewall more and more to make them work. At the time the applications and Web applications were pretty bad. The threat landscape at the time was Web defacement. Then the Web started to evolve and about five years ago we saw more and more dynamic content pushed onto the Web and more actual business functions happening. The firewall still provides a baseline of security, but you allow port 80 and you allow a freeway of activity into your network. What used to be a closed off sense of what was internal and what was external is now evaporated. It appears that mostorganizations, once they're doing business on the Internet, allowing traffic in and out of their network on port 80, they've essentially allowed an open door for access into your infrastructure. The link for this article located at Search Security is no longer available. . A leader's dedication to robust programming practices strengthens software creation and elevates security measures throughout the company.. Secure Coding, Software Development, Threat Landscape. . LinuxSecurity.com Team
Security experts agree that there's something wrong with the software development process, but there are differing opinions on how to solve the problem. It's another day in the life of a security pro -- or a hacker. Much of your time is spent searching applications for that one weak point, the one that will lead to the breach of sensitive data. And nearly every day, somebody finds one. Or more.. With all of the security know how offered today -- and all of the advanced tools offered to applications developers -- why is software still riddled with security vulnerabilities? The answers are many, and they don't always agree. And solutions to the problem? Those are even more diverse. Vulnerabilities start, experts agree, because developers don't understand how to build security into the code they write. "There's a lot more acceptance of security as part of the process now, but historically developers have never been responsible for security," says Brian Chess, founder and chief scientist at Fortify, a company that makes tools for secure software development. "We all understand locks and keys, but not many of us are locksmiths. That's where most developers are." The link for this article located at Dark Reading is no longer available. . Software development faces security challenges despite numerous tools. Developers often focus on features over security due to deadlines, leading to vulnerabilities.. Secure Coding Practices, Software Development Security, Application Security Tools. . LinuxSecurity.com Team
In an ideal world, words like cryptography and security wouldn't even exist, but the real world is far from perfect, so software developers have to spend a good deal of time building security into applications. Cryptography is just one piece of the security puzzle, along with SSL/TLS, certificates, digital signatures, and so on. This article explains how to use PHP to implement the most common cryptographic algorithms. In addition to describing PHP's default encryption functions, you'll see how to use a wide variety of cryptographic libraries and packages. Building security into your web applications is an important skill to have. Have you thought about adding cryptography to your php programs? If so this article looks at ways of doing so.. The link for this article located at Devx is no longer available. . Explore strategies for implementing cryptographic techniques in PHP applications to enhance security measures and safeguard confidential information.. PHP Security Practices, Cryptographic Libraries, PHP Encryption Techniques. . Bill Locke
This is the first in a series of newsletters, where we talk with Linux experts who will be speaking at the LinuxWorld Conference and Expo, which runs Aug. 14-17 at the Moscone Convention Center in San Francisco. PHP, PERL and other languages are useful and easy to learn tools that can be used to build some pretty functional Web-based applications. They can also be the bane of a system administrator's existence, especially when slapped together and used to publish Web apps accessible to the outside world. . "Due to the ease that some languages allow people to write Web applications people are throwing Web applications up left and right without any kind of security review," says David Cafaro, a systems analyst for the Advanced Research Computing group at Georgetown University. An example could be something as simple as a Web form on an apps server. If the code is poorly written, or is running on a vulnerable machine, this could allow someone to gain access as an Apache user, Cafaro says. If the Apache server isn't updated, or if an unknown vulnerability exists in the software for example, this could possibly allow someone to get root access to a machine. "People just have to pay attention to what they're putting up there and realize that it's for the world to see, and for the world to toy with," Cafaro says. . The significance of fortifying web applications on Linux cannot be overstated as specialists delve into strategies for improved security.. Web Application Security,LinuxWorld 2023,Security Insights,Application Security. . LinuxSecurity.com Team
I would like to announce the availability of a new and free resource to the software security community, the SC-L email discussion forum. The moderated forum is open to the public. The group's purpose is, "to further the state of the practice of developing secure software, by providing a free and open, objectively moderated, forum for the discussion of issues related to secure coding practices throughout a software development lifecycle process (including architecture, requirements and specifications, design, implementation, deployment, and operations).". . . . I would like to announce the availability of a new and free resource to the software security community, the SC-L email discussion forum. The moderated forum is open to the public. The group's purpose is, "to further the state of the practice of developing secure software, by providing a free and open, objectively moderated, forum for the discussion of issues related to secure coding practices throughout a software development lifecycle process (including architecture, requirements and specifications, design, implementation, deployment, and operations)." (The complete text of the group's charter, including its acceptable and unacceptable usage policies, can be found at ) To subscribe to the list, simply connect to and follow the directions on the form. Submissions should be sent (by subscribers only) to
Jeremy Allison goes against a Microsoft security specialist in this open source vs proprietary debate. "I believe that the open source development model does create software with significantly fewer exploitable holes than proprietary software. ... I know that programmers of proprietary . . . . Jeremy Allison goes against a Microsoft security specialist in this open source vs proprietary debate. "I believe that the open source development model does create software with significantly fewer exploitable holes than proprietary software. ... I know that programmers of proprietary software leave holes and take more liberties than open source programmers. The reasons are simple: Their management and marketing departments are screaming for the code to ship, doing it right is harder than doing it quickly and, after all, they think, who is going to know? I've been in this situation myself. On the other hand, most open source software is written by people for whom programming is not a chore. It's a craft, and they take great pride in doing their work properly. Away from the demands of marketing and management, they are able to create the code that they want to write, not the code that will make the most money. The difference in the quality of the code produced by the two methods is staggering." The Microsoft side counters with "Commercial software tends to be more secure than open source software, for simple economic reasons. Simply put, you get what you pay for. Commercial development organizations have a powerful motivation to get security right: Their livelihoods depend on it. That's why commercial software firms use advanced tools and follow processes that leverage knowledge of known security flaws to drive "lessons learned" into new code. Commercial software firms not only employ people who are dedicated and passionate about security, they also pay them to do the hard, tedious work - including testing - that's not especially interesting to most open source volunteers." The link forthis article located at Interactive Week is no longer available. . Delving into the ongoing security discourse surrounding open source versus proprietary software, featuring perspectives from industry specialists.. Open Source Security, Proprietary Software, Security Perspectives, Exploitable Holes, Software Development. . LinuxSecurity.com Team
Get the latest Linux and open source security news straight to your inbox.