security

Case studies

Anonymous
Friday, February 17, 2012 - 10:17
security
incident response
technical guide
case studies
Overview
Read more

Staffing models for incident responses

Anonymous
Friday, February 17, 2012 - 10:17
security
incident response
technical guide
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.
Read more

Incident response functions

Anonymous
Friday, February 17, 2012 - 10:16
security
incident response
technical guide
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.
Read more

Reasons for incident response

Anonymous
Friday, February 17, 2012 - 10:16
security
incident response
technical guide
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.
Read more

Effective incident response

Anonymous
Friday, February 17, 2012 - 10:12
incident response
security
technical guide
GD/NOTE/009 (03/09)
Read more

Related information

Anonymous
Friday, February 17, 2012 - 08:06
further information
references
related information
security
technical guide
Section 2: Methods of Countering the Threats UCISA: Information Security Toolkit UCISA: Model Regulations SANS: Critical Security Controls
Read more

Requirements of an organisation connecting to Janet

Anonymous
Friday, February 17, 2012 - 08:05
organisation requirements
security
technical guide
6.1 Janet Policies Any organisation connecting to Janet is required to abide by three policies established to support the role of the network in enabling education and research. These are as follows:
Read more

Security measures within the Janet backbone

Anonymous
Friday, February 17, 2012 - 08:05
backbone
security
security measures
technical guide
5.1 Policy Filtering in the Backbone Routers
Read more

Network security

Anonymous
Friday, February 17, 2012 - 08:04
network security
security
technical guide
4.1 Use of Filters Within Routers for Network Access Control
Read more

Computer security

Anonymous
Friday, February 17, 2012 - 08:03
host security
security
technical guide
Connecting an insecure computer to a network places that computer, its users and any information it contains at risk. Insecure computers also represent a threat to other computers, users and information on the network, since intruders frequently use one compromised machine to attack others either simply by using it to generate network traffic in a distributed denial of service attack, or more subtly by using the access that the compromised computer or its users have to compromise others.
Read more
Subscribe to security