« Back to DataSecurityPolicies.com

Archive for the 'Vulnerability Management Policy' Category



Hardening Your Web Application Against SQL Injections

By Raheel Ahmad

WARNING:

The information provided is for educationally purposes only and not to be used for malicious use.

Before digging into what actually SQL Injection is, let me explain you what is SQL itself.

What is SQL?

Structured Query Language (SQL) is a specialized programming language for sending queries to databases. Most small and industrial- strength database applications can be accessed using SQL statements. SQL is both an ANSI and an ISO standard. However, many database products supporting SQL do so with proprietary extensions to the standard language. Web applications may use user-supplied input to create custom SQL statements for dynamic web page requests.

What is SQL Injection?

SQL injection is a technique that exploits a

Read the rest of this entry »

World Bank Data Breach

Photo credit: KAREN BLEIER/AFP/Getty Images

Photo credit: KAREN BLEIER/AFP/Getty Images

In breaking news directly related to data security policies, FoxNews is reporting that the World Bank has suffered possibly “the worst security breach ever at a global financial institution”:

 The World Bank Group’s computer network — one of the largest repositories of sensitive data about the economies of every nation — has been raided repeatedly by outsiders for more than a year, FOX News has learned.

It is still not known how much information was stolen. But sources inside the bank confirm that servers in the institution’s highly-restricted treasury unit were deeply penetrated with spy software last April. Invaders also had full access to the rest of the bank’s network for nearly a month in June and July.

In total, at least six major intrusions — two of them using the same group of IP addresses originating from China — have been detected at the World Bank since the summer of 2007, with the most recent breach occurring just last month.

While it remains unclear how much data has been pilfered from the bank, it’s a lot. According to internal memos, “a minimum of 18 servers have been compromised,” including some of the bank’s most sensitive systems — ranging from the bank’s security and password server to a Human Resources server “that contains scanned images of staff documents.”

One World Bank director tells FOX News that as many as 40 servers have been penetrated, including one that held contract-procurement data.

Despite the gravity of the break-ins, the bank is trying hard to pretend to outsiders it didn’t happen. “There were attempts to hack the bank’s computer systems last summer,” says a World Bank spokesman. “However, there was no compromise of confidential information.”

So if this actually happened, which data security policies could have helped prevent the “the worst security breach ever at a global financial institution”?

  • Corporate Security Policy
  • Incident Response Policy
  • Network Security Policy
  • Vulnerability Management Policy

Others?

Vulnerability Management Program

The National Institute of Standards and Technology (NIST) has a document especially useful to anyone writing their vulnerability management policy. It’s Special Publication 800-40, Creating a Patch and Vulnerability Management Program. You can find it here.

Here’s an excerpt:

Organizations need to create a comprehensive, documented, and accountable process for identifying and addressing vulnerabilities, patches, and threats within an organization. One possible approach is to have a formal, centralized patch and vulnerability group that supports the security efforts of local system administrators.

Specific recommendations for organizations implementing a patch and vulnerability management program are as follows:

  1. Create an inventory of all information technology assets.
  2. Create a patch and vulnerability group.
  3. Continuously monitor for vulnerabilities, remediations, and threats.
  4. Prioritize patch application and use phased deployments as appropriate.
  5. Test patches before deployment.
  6. Deploy enterprise-wide automated patching solutions.
  7. Create a remediation database (this is often included within enterprise patch management tools).
  8. Use automatically updating applications as appropriate.
  9. Verify that vulnerabilities have been remediated.
  10. Train applicable staff on vulnerability monitoring and remediation techniques.

An archive copy of the document is here: Vulnerability Management Program