Similar Searches

Related Posts

  • Critical Control 2: Inventory of Software (February 2, 2010)

    Critical Control 2: Inventory of Authorized and Unauthorized Software While we are starting to see some research being done on hardware level attacks (i.e. BIOS level viruses have been proven to be a viable concept), most exploitation of systems revolve around finding vulnerabilities in the software. Any time a piece of ...

  • Critical Control 4: Secure Configurations for Network Devices (February 4, 2010)

    Critical Control 4: Secure Configurations for Network Devices such as Firewalls, Routers, and Switches Most systems are installed with a default installation and not properly hardened for the organization that is using the device. Therefore hardened images need to be created for each of the core devices on your network. This is similar ...

  • Critical Control 3: Secure Configurations for PCs and Servers (February 3, 2010)

    Critical Control 3: Secure Configurations for Hardware and Software on Laptops, Workstations, and Servers Most systems are installed with a default installation and not properly hardened for the organization that is using the software or device. Therefore hardened images need to be created for each of the devices and software an organization ...

  • Critical Control 5: Boundary Defense (February 5, 2010)

    Critical Control 5: Boundary Defense Controlling the flow of information is critical to properly protecting critical information. Systems and their respective data must be broken down into trust levels or classifications. Any connectivity between networks of different trust must be through a robust boundary defense that properly protects and controls information flow ...

  • Critical Control 10: Continuous Vulnerability Assessment and Remediation (February 10, 2010)

    Soon after new vulnerabilities are discovered and reported by security researchers or vendors, attackers engineer exploit code and then launch that code against targets of interest.  Any significant delays in finding or fixing software with critical vulnerabilities provides ample opportunity for persistent attackers to break through, gaining control over the ...

Related News

Related Posts

  • Critical Control 2: Inventory of Software (February 2, 2010)

    Critical Control 2: Inventory of Authorized and Unauthorized Software While we are starting to see some research being done on hardware level attacks (i.e. BIOS level viruses have been proven to be a viable concept), most exploitation of systems revolve around finding vulnerabilities in the software. Any time a piece of ...

  • Critical Control 4: Secure Configurations for Network Devices (February 4, 2010)

    Critical Control 4: Secure Configurations for Network Devices such as Firewalls, Routers, and Switches Most systems are installed with a default installation and not properly hardened for the organization that is using the device. Therefore hardened images need to be created for each of the core devices on your network. This is similar ...

  • Critical Control 3: Secure Configurations for PCs and Servers (February 3, 2010)

    Critical Control 3: Secure Configurations for Hardware and Software on Laptops, Workstations, and Servers Most systems are installed with a default installation and not properly hardened for the organization that is using the software or device. Therefore hardened images need to be created for each of the devices and software an organization ...

  • Critical Control 5: Boundary Defense (February 5, 2010)

    Critical Control 5: Boundary Defense Controlling the flow of information is critical to properly protecting critical information. Systems and their respective data must be broken down into trust levels or classifications. Any connectivity between networks of different trust must be through a robust boundary defense that properly protects and controls information flow ...

  • Critical Control 10: Continuous Vulnerability Assessment and Remediation (February 10, 2010)

    Soon after new vulnerabilities are discovered and reported by security researchers or vendors, attackers engineer exploit code and then launch that code against targets of interest.  Any significant delays in finding or fixing software with critical vulnerabilities provides ample opportunity for persistent attackers to break through, gaining control over the ...

Critical Control 7: Application Software Security

Critical Control 7: Application Software Security

When a programmer creates code for a program, their main focus is to ensure they deliver working code on time. They do not take the time to ensure that all of the code is free of security vulnerabilities. The assumption is made that this will be done during other phases of the development process. Attacks against vulnerabilities in Web-based and other application software have been a top priority for criminal organizations in recent years. Application software that does not properly check the size of user input fails to sanitize user input by filtering out unneeded but potentially malicious character sequences, or does not initialize and clear variables properly could be vulnerable to remote compromise. Attackers can inject specific exploits, including buffer overflows, SQL injection attacks, and cross-site scripting code to gain control over vulnerable machines. In one attack, more than 1 million Web servers were exploited and turned into infection engines for visitors to those sites using SQL injection. During that attack, trusted Web sites from state governments and other organizations compromised by attackers were used to infected hundreds or thousands of browsers that accessed those websites. Many more Web and non-Web application vulnerabilities are discovered on a regular basis. 

To avoid such attacks, both internally developed and third-party application software must be carefully tested to find security flaws. For third-party application software, enterprises should verify that vendors have conducted detailed security testing of their products. For in-house developed applications, enterprises must conduct such testing themselves or engage an outside

...
Read the original story


Source: Eric Cole @ McAfee Security Insights Blog

Write a Comment

Copyright © 2010 The Security Blog. All rights reserved.
Web Statistics Homeland Security blogs & blog posts