Skip to the content ForoHackers
Log inJoin

Someone sent me a screenshot with eleven CPU hours and the word MALWARE in little red letters

Incident responseObservabilitySecurity operations
#16378 · · Quote · Report

It's a plain, invented log viewer on my own test machine. The screenshot shows total CPU time accumulated since the program started. Somebody read eleven hours as "it is consuming eleven hours right now". CPU rates for intervals, per-process elapsed time, cumulative CPU time: I wanted to put the three on one page before the debate spreads to the microwave.

#16608 · · Quote · Report

Give us two cumulative samples for the same process. If CPU time rises by 0.2 seconds during ten elapsed seconds, that's about 2 percent of one core over that interval. We still haven't said whether the program is desirable.

#16609 · · Quote · Report

Precisely. My little single-threaded example goes from 39600.0 to 39600.2 seconds over that window. The scary eleven-hour number is still there. Our new ten-second interval shows something quite unexciting.

#16610 · · Quote · Report

Y si el proceso cambia entre muestras, hay que saber que las dos son del mismo. No sería el primer informe del blue team que junta la foto de un perro con la biografía de otro.

#16611 · · Quote · Report

I wouldn't clear an endpoint of malware from a quiet sample either. That's a different claim and it needs different evidence. Good to keep the word "sample" in the note.

#16612 · · Quote · Report

Hang on. If the malware label was somebody's guess, fine. But I have actually called the on-call person over a process that suddenly went hot. Now you lot are laughing at the number and I would like to know what I was supposed to have done.

#16613 · · Quote · Report

Called them, from the sound of it. Did yours suddenly go hot? Mine came with one screenshot that could have been taken on Thursday or last year.

#16614 · · Quote · Report

Ah shit. Yes. We had a normal morning baseline and three people whose window had frozen. I thought yours used to be low and jumped.

#16615 · · Quote · Report

That's the bit I wanted. I'd love that in the first message I get on shift: last normal time, when people started feeling it, what you could still use. I don't mind you not knowing the cause. I mind the bloody graph becoming the entire incident two handovers later because nobody wrote down that the people at the front desk couldn't type. Last time I walked out to the desk, their browser already had the last ticket in it and the queue was gone. I could cheerfully have announced that the service was back. The woman there asked if I'd like to try printing my ticket. I still have the little white slip it spat out. Nothing on it for the passenger except the date.

#16616 · · Quote · Report

as the person at a front desk: the screen was perfectly responsive on your laptop. my bit of the job was dead. those two things can be true in the same building.

#16617 · · Quote · Report

Yeah. "Still unable to issue tickets at desk B" beats "our blue team has determined it's probably definitely ransomware" if that's what you've actually seen. A fix for the wrong fucking incident can burn your entire shift.

#16618 · · Quote · Report

Cheers @SameWhen_. Hanging on to that first sentence for next time. My own screenshot didn't include any of the people yelling behind me.

#16619 · · Quote · Report

We changed the red caption to "cumulative CPU time". The author then asked if we should highlight it green. I confiscated the marker pens. That is the limit of my disciplinary powers.

You are not logged in, so this goes up anonymously: no account, no name and no address is stored with it, and it may carry no link and no image. Log in or join to post under your name. Our web server's logs keep the address and time of every request for up to 14 days; to keep yours out of them, use Tor. To reach the staff in confidence, use the drop. Sign as a returning source (a key kept only in this browser)

Sending takes a few seconds here: your browser first works out a proof of work against spam.

Reply