Hiya Kevin, First answer the question about blocks, the blocks are used to interact with the Network guys, i.e. for asking a block of an IP(s) or port in the network, so you will be able to keep tracking of the talks with NOC guys, and all the actions you take over the network to solve the incident. In case you see the block queue is not useful for you, you can deactivate in the RTIR config file.
About incidents, if you have two complaints in your incident reports queue related to two different IPs of your institution, or related to two different issues, you won't want to open only one single incident to handle everything, and mix the information you can receive, what you have to do is to open two different incidents, and each IR will be linked to its own incident, handling them separately, and launching investigations to fix the problems. You can be in front of cases where you have a incident report asking something, where you will have to open an incident, but an investigation won't be needed as you are acting as a security helpdesk team. I hope it clarify a bit more your workflow understanding, as James said the document is a bit basic, and I think it should be more complete, having use cases and more examples. Cheers, Carlos Sent from my iPad On 14/02/2013, at 21:12, Kevin Holleran <[email protected]> wrote: > Thanks again. I am not understanding some of the workflow. > > An incident can be defined. One (or more?) incident reports can be linked to > the incident. One or more investigations can be linked to the incident. > What are the blocks for? > > Thank you! > > > -- > Kevin Holleran > Master of Science, Computer Information Systems > Grand Valley State University > Master of Business Administration > Western Michigan University > SANS GCFA, SANS GCFE, CCNA, ISA, MCSA, MCDST, MCP > > "Do today what others won't, do tomorrow what others can't" - SEALFit > > "We are what we repeatedly do. Excellence, then, is not an act, but a habit." > - Aristotle > > > On Tue, Feb 12, 2013 at 10:33 AM, James Davis <[email protected]> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA256 >> >> On 12/02/2013 15:20, Kevin Holleran wrote: >> >> > I just set up RT 3.8 with RT/IR. I am new to this and need to ramp >> > up quickly. What is a good resource rather than just fumbling >> > around and learning through trial and error or stumbling through >> > bits and pieces of documentation? I noticed the RT Essentials book >> > but I was wondering if it was dated based on the publication date. >> > >> http://bestpractical.com/static/rtir/janet-workflow.pdf is a useful >> resource that explains the RTIR workflow[1]. >> >> James >> >> 1. I may be a little biased. >> >> - -- >> James Davis 0300 999 2340 (+44 1235 822340) >> Senior CSIRT Member >> Lumen House, Library Avenue, Didcot, Oxfordshire, OX11 0SG >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.11 (Darwin) >> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ >> >> iF4EAREIAAYFAlEaYL0ACgkQjsS2Y6D6yLyQWAEAlUIuiH+glbsOFXEQP45B9zXI >> SAK+txSS2PeVfWcESMIBANIJ5SNcMH+hxXEfKEEeY923XsgoxPEIBgIr8rbi7ryE >> =m8+Z >> -----END PGP SIGNATURE----- >> >> Janet(UK) is a trading name of Jisc Collections and Janet Limited, a >> not-for-profit company which is registered in England under No. 2881024 >> and whose Registered Office is at Lumen House, Library Avenue, >> Harwell Oxford, Didcot, Oxfordshire. OX11 0SG. VAT No. 614944238 >> >> _______________________________________________ >> Rtir mailing list >> [email protected] >> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rtir > > _______________________________________________ > Rtir mailing list > [email protected] > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rtir
_______________________________________________ Rtir mailing list [email protected] http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rtir
