Matches in SemOpenAlex for { <https://semopenalex.org/work/W2066057766> ?p ?o ?g. }
Showing items 1 to 38 of
38
with 100 items per page.
- W2066057766 abstract "Computer viruses, worms, denial of service attacks, equipment failures, vandalism, theft and other unwelcome events can send your computer services staff scrambling and cause a variety of problems for your user community. Even the least of these situations can be a distraction for your staff. The most severe can provide an unscheduled opportunity to test your disaster recovery procedure! How does your organization react to these events? Do you have a clearly-defined process in place to deal with unexpected incidents that threaten the security or operation of your systems.Eastern Connecticut State University is a public liberal arts institution with an enrollment of about 5000 students. Our Information Technology Services (ITS) group has implemented a process that provides a framework for an orderly response to unexpected events. The process is an adaptation of security incident response recommendations from the National Institute of Standards and Technology, Internet Security Systems, Inc. and other resources, which have been tailored for our institutional needs. At the core of the process is the Incident Response Team, which consists of a team manager, a technical leader and other ad hoc team members, depending on the nature and severity of the event. The team concept takes advantage of institutional expertise from law enforcement, human resources, audit, public relations, facilities management, legal services and other technical resources within ITS. The team manages information gathering, analysis, recovery and administrative functions to ensure a controlled, coordinated approach to incident response.Our presentation will focus on the phases of the incident response process and the role of the Incident Response Team. Flexibility, wise use of resources, effective communications and analytical skills are contributing factors to a successful response effort. We will draw upon our own experiences in discussing communication with the user community, severity level guidelines, evidence gathering, essential documentation, and lessons learned along the way." @default.
- W2066057766 created "2016-06-24" @default.
- W2066057766 creator A5051117311 @default.
- W2066057766 date "2003-09-21" @default.
- W2066057766 modified "2023-09-24" @default.
- W2066057766 title "Incident handling" @default.
- W2066057766 cites W2115628417 @default.
- W2066057766 cites W2130734770 @default.
- W2066057766 cites W214177289 @default.
- W2066057766 doi "https://doi.org/10.1145/947469.947496" @default.
- W2066057766 hasPublicationYear "2003" @default.
- W2066057766 type Work @default.
- W2066057766 sameAs 2066057766 @default.
- W2066057766 citedByCount "11" @default.
- W2066057766 countsByYear W20660577662013 @default.
- W2066057766 countsByYear W20660577662016 @default.
- W2066057766 countsByYear W20660577662021 @default.
- W2066057766 crossrefType "proceedings-article" @default.
- W2066057766 hasAuthorship W2066057766A5051117311 @default.
- W2066057766 hasConcept C41008148 @default.
- W2066057766 hasConceptScore W2066057766C41008148 @default.
- W2066057766 hasLocation W20660577661 @default.
- W2066057766 hasOpenAccess W2066057766 @default.
- W2066057766 hasPrimaryLocation W20660577661 @default.
- W2066057766 hasRelatedWork W2093578348 @default.
- W2066057766 hasRelatedWork W2350741829 @default.
- W2066057766 hasRelatedWork W2358668433 @default.
- W2066057766 hasRelatedWork W2376932109 @default.
- W2066057766 hasRelatedWork W2382290278 @default.
- W2066057766 hasRelatedWork W2390279801 @default.
- W2066057766 hasRelatedWork W2748952813 @default.
- W2066057766 hasRelatedWork W2766271392 @default.
- W2066057766 hasRelatedWork W2899084033 @default.
- W2066057766 hasRelatedWork W3004735627 @default.
- W2066057766 isParatext "false" @default.
- W2066057766 isRetracted "false" @default.
- W2066057766 magId "2066057766" @default.
- W2066057766 workType "article" @default.