🇺🇦🇳🇴🇨🇦 | Cybersecurity Advisor | Outspoken | Speaker | Veteran | Diver | Currently #NAFO | Used to be here for #infosec – now I’m here for #Ukraine
2 subscribed
May 18 • 16 tweets • 6 min read
I know that some people that know me from a professional setting – I am a senior cyber security advisor with about ten years of experience fighting Russian espionage – may find the language of my trench-style disinformation fighting a bit much.
For posterity I want to say: 1/14
We are living in dangerous times. Russia is like a scorpion and is just being Russia as it has been for 500 years. But our leaders have ignored that and completely failed us and are still failing us and are slow-walking us towards WWIII. And I will not sit quietly and watch. 2/14
Apr 6, 2023 • 18 tweets • 3 min read
This Norwegian essay on #Russia by officer Gunnar Gabrielsen should get an international audience, so I translated it. Here we go. 1/18
nrk.no/ytring/naive-o…
2/18 Apologies to Poland, the Baltics, Finland, and all Central and Eastern Europeans who warned us about Russia - its nature and what it has always been: expansive, unforgiving, aggressive, and uncompromising. You warned us for years, but we didn't listen.
Feb 27, 2023 • 5 tweets • 2 min read
I see people say “don’t engage the trolls”, but I will.
#NAFO playbook:
1. Ridicule 2. Report 3. Block 4. Move on (!!)
5. And for every bonk, amplify a pro-Ukrainian voice.
6. And for very 10th cycle, donate to a Ukrainian cause.
Rinse and repeat. This is the way. #WeAreNAFO 2/ Context (one of many tweets). Read up, and also check Chris’ quoted tweet (which I absolutely think has merit).
dsb.no/reportasjearki…
(2/14) I den forbindelse avholder @DSB_no i dag et gratis webinar som i følge arrangøren per nå har over 900 påmeldte, men det er fremdeles mulig å melde seg på og se det her:
@willoram@smoothimpact 1) Make sure the company has good grasp of the actual risk the intrusion (or breach) posed, and what could have happened had the attacker had more time or succeeded with stuff they initially failed at.
@willoram@smoothimpact 2) Agree with the company on what is and isn’t acceptable risk with regard to this particular attacker, and under any circumstance, should your attacker profiling be wrong.