News for hackers. Stuff that matters.
Re:Incident Response Documentation by wil421 on Monday January 14, 2019 @01:13PM (#18904981)
Do your incidents have Priorites (Severity in the article)? At my company a printer would never be a P1 to P2 therefore no one gets paged at 3am due to printer issues.

It’s not full proof and my team did get a P1 due to a field length being too short but it was during normal business hours. It was quickly changed to a P4 and the person who opened it got a lesson on Incident priorities.

Re:Incident Response Documentation by sambull on Monday January 14, 2019 @01:27PM (#18905110)
Printing would be Sev 1, as our end users are 24/7 JIT manufacturers with big contracts. Without printers, no shipping labels, packaging, or inventory barcodes etc for their normal manufacturing shifts.
Re:Incident Response Documentation by C1sc0cat on Tuesday January 15, 2019 @04:24AM (#18909879)
So you need a 24/7 ops coverage to handle that and not rely on calling out an expensive M&P grade.
Re:Incident Response Documentation by flukus on Monday January 14, 2019 @07:30PM (#18907926)
Presumably there are multiple redundant printers and sev 1 would only be an outage effecting all of them?
Re:Incident Response Documentation by wil421 on Monday January 14, 2019 @02:03PM (#18905428)
I understand now. The company I used to work for was in manufacturing. Luckily my current employer is all services and software.