Data breach: Only 16 per cent self-identified

POS system attacks come of age in Australia.

Only 16 per cent of organisations that faced a breach in 2011 detected it prior to a notification by a third party, according to an analysis of investigations conducted last year by [[xref: https://www.trustwave.com/pressReleases.php?n=trustwave-report-reveals-global-data-breach-and-security-trends |Trustwave's SpiderLabs security team|]].

The vast majority, 84 per cent, were informed by either a regulatory body, law enforcement or the public, and on average the attackers behind the breach that was discovered by a third party had 173.5 days to rummage around the target’s environment.

The report shows that the time between the initial breach and when an investigation takes place is up to three years.

The important figure that distinguishes self-identification to discovery from an external source was that in the case of self-identification, the organisation knew of the breach on average after 43 days rather than 173 days.

Currently the most common way for an organisation to discover they have been breached is through regulatory notification. In a third of the cases law enforcement notified the organisation, up from just 7 per cent in 2010.

One of the most common methods of infiltrating corporate IT systems was weak administrator username and password combinations.

A particular risk for organisations was IT outsourcing arrangements, which provided third-party VPN access to internal systems. Hackers scan the web for ports used by remote access applications, which remain highly vulnerable when default configurations are left in place. Sixty-one per cent of infiltration cases occurred using this method and 19.9 per cent occurred through weak credentials or client side attacks.

Client side attacks were primarily (60 per cent) caused by system admins using production environments for personal use, such as accessing personal email accounts, social networking sites and Flash and Java-based gaming sites.

SQL injection attacks were also in 6.9 per cent of the incidents SpiderLabs investigated.

In terms of getting data out of the organization, attackers often exploited the lack of “egress” our outbound filters. Firewall deficiencies were behind 84 per cent of successful exfiltration cases. Correct firewall configurations should ensure data is being sent to the propoer location, over the proper port, using an authorised protocol, Trustwave points out.

Australia: POS systems in focus.

Trustwave reports that investigations its Spider Labs division conducted in Australia focused primarily on point of sale (POS) systems, such as the PIN entry device used to read cards and collect PINs.

While attacks on improperly stored data on the PIN device were more common, its investigators picked up the first data “in transit” attack in late 2011, marking a migration of an attack technique already seen in the US and Europe.

In the case of an in-transit attack, the criminal would use memory dumping malware that intercepts and captures clear-text payment card data transmitted between the PIN entry device and the POS system.

It did not disclose how many investigations it has conducted in Australia, but said that 90 per cent of its investigations in the APAC region related to payment card data compromises, noting that attacks had shifted away from e-commerce sites towards POS systems.

Tags: security breach, security trends, Trustwave SpiderLabs

Comments

1

Mya

Fri 24/02/2012 - 17:53

The information bits are good

Post new comment

The content of this field is kept private and will not be shown publicly.
Users posting comments agree to the CSO comments policy.
Login or register to link comments to your user profile, or you may also post a comment without being logged in.
CSO Corporate Partners
  • FirEye
  • Clear Swift
  • Trend Micro
  • Sophos
  • NetIQ
rhs_login_lockGet exclusive access to CSO, invitation only events, reports & analysis.
CSO Directory

NetIQ iSeries Security

The NetIQ iSeries Security Solutions helps you eliminate security risks and maintain business continuity

Security Awareness Tip
Clearswift tips: Guidelines for introducing and policing an effective IT Policy

1. Make it clear that the policy is not about playing ‘Big Brother’ but to ensure the security of employees, company information and data and to safeguard the company’s reputation.
2. Invest time to get buy-in from managers and their teams.
3. Convey the message of flexibility – with regard to social media, it is not about blocking staff usage but working in everyone’s interests to ensure that threats are contained.
4. Introduce a regular company-wide training programme that everyone attends at regular intervals throughout the year, not merely as part of an induction programme.
5. Within the training programme make sure that there are specific examples to demonstrate each rule or regulation, and that there is a clear explanation of the dangers of casual or careless talk on social networking sites. Again use examples, employees need to understand the consequences of raising a throwaway comment that has negative connotations for the business, as much as they need to be aware of dangers of making a more direct but ill-considered attack on a competitor, regulator or even a fellow colleague. They need to be clearly advised on any impact on the company and/or legal action or inquires that may be raised as a result.
6. Alert employees to any changes in policy through regular clear communication.
7. Reinforce the operational policy guidelines regularly, cover everything from blogging to Facebook, LinkedIn and Twitter.
8. Ensure that the rules are fair and that they apply throughout the business.
9. Enforce the rules – if there is a deliberate or malicious contravening, disciplinary action needs to be taken. A policy isn’t worth having if it is seen to be lax and unenforced.
10. Review the policy regularly to ensure you keep up to date with new systems and technology.

Phil Vasic is Regional Director, APAC, at Clearswift, the software security company www.clearswift.com
Security ABC Guides

7 Ways to Protect Your Business Printers

Can a hacker burn down your business by remotely setting one of your printers on fire? Researchers at Columbia University have recently proposed such a scenario, although HP quickly denied that it's possible. However, even if your printers can't be used as remote firestarters, there are many risks involved in networking a printer.