incident response

Anonymous
Overview
Anonymous
The basic staffing requirement of an incident response function is that there be some individual or individuals able to receive and respond to reports during the function's operating hours. The speed of response should be set as part of the function's agreed operating policy, however the working arrangements should allow for emergency situations where action to resolve a problem needs to take priority over all other normal work.
Anonymous
From the preceding discussion it is clear that any organisation connected to Janet must have at least a basic response capability to deal with security incidents as required by its Janet contract. There are also good reasons why the organisation should not be content with this minimum but should provide additional functions for the benefit of its own users and its operation. This extended capability is likely to involve people and groups beyond the basic security incident response group, some of whom may be located in a different part of the management structure.
Anonymous
There are a number of different reasons why a Janet customer site should improve its response to computer security incidents. Depending on the circumstances, different reasons will carry different weight in each organisation: however an effective incident response function should bring benefits in all these areas.
Anonymous
GD/NOTE/009 (03/09)
Anonymous
From time to time Janet CSIRT may report activity to you that is related to the Conficker worm. Typically this is a record of traffic from an infected host, to a Conficker sinkhole server. These sinkhole servers pretend to be part of the worm’s command and control infrastructure. The worm then attempts to load a web page on the sinkhole server, that were the server real, would contain instructions for the worm. Our reports typically look like this
Anonymous
The Conficker worm (also known as Downup, Downadup and Kido) is probably the most prevalent computer worm on Janet and the Internet at this time. It’s success can be attributed to it’s use of a number of different vectors it uses to infect machines:
Anonymous
Zeus is the name for a family, or perhaps ecosystem of malware that is created and customised using a single toolkit. Not only does the toolkit generate the executable that infects systems, but it also produces server files that act as the command and control infrastructure for the operator’s botnet. Primarily Zeus is used to steal banking details through the use of keystroke logging and screen captures that are sent from the infected system to the command and control sever.
Anonymous
Carberp is the name of the latest in an increasing line-up of information stealing malware that have evolved in the last few years. As in the case of it’s forerunners (Torpig/Mebroot,Clampi, ZeuS and SpyEye) the most recognised role of Carberp is to steal users e-commerce payment transaction data (e-banking, Paypal, debit/credit card etc.), although any sensitive data is at risk (personal identity or research data for example).
Anonymous
Janet CSIRT routinely processes netflow data to detect signs of Conficker infections on Janet.
Subscribe to incident response