Joined December 2023
- Tweets 1,240
- Following 354
- Followers 253
- Likes 8,576
84 Photos and videos
Pinned Tweet
Feb 8
Finished Cisco Networking Basics today 🎉
Subnetting almost won… but we move 😅
Foundations locked in.@cyber_razz @elormkdaniel @T3chFalcon
Next step: applying this knowledge and going deeper into blue-team / SOC skills.
#Cybersecurity #Networking
11
8
66
1,714
God when 🤲
I have experienced seven years of uninterrupted power supply without praying for it. Pure bliss >>>>>>>>
1
17
Today i compared my skills to 10 junior SOC job descriptions.
Log analysis, phishing, detection rules — real foundations.
Then the gaps hit. EDR platforms came up in 7/10 JDs. I've never touched CrowdStrike or SentinelOne.
Not job-ready yet. But now I know exactly what to fix
2
1
5
26
Lawrence retweeted
Jun 12
Day 11of #JuneChallenge
Just finished Andrej Karpathy’s first video on Neural Networks.
The video gave me an intuitive-practical approach of concepts like MLP (Multi-Layer Perceptron), Manual gradient descent loop: forward pass → loss → backward → update parameterst
Jun 11
Day 7-10
Started Andrej Karpathy’s “Neural Networks: Zero to Hero” still on the first video where he builds autograd from scratch.
The way he explains micrograd is so clean, finally understanding the magic behind backward()
Slow progress > no progress. Let’s keep going!
1
3
5
81
Jun 12
Day 28: reviewed profiles of SOC analysts who are already working in the field.
Started noticing the same patterns over and over: specific skills, real projects, and clear proof of work.
Made a few updates to my own profile based on that.
linkedin.com/in/okoli-chieme…
#socAnalyst
3
39
Lawrence retweeted
git add
git commit -m ' '
2
1
8
370
Lawrence retweeted
Jun 10
Day 26 — no labs today.
Just cleaned up my GitHub so it actually makes sense to someone landing on it for the first time.
New repos:
→ sigma-rules-collection
→ yara-rules-collection
→ incident-reports
github.com/DevSecLawrence
@CyberRacheal @cyber_rekk @ireteeh
#BlueTeam
2
9
93
Lawrence retweeted
Jun 11
My fellow cyberpros, is it normal for me to have 6k foolowers on X and not even up to 500 subs on Youtube?
Ko da bayi, we can do better ejo
kindly subscribe to my youtube channel, make I no jones
youtube.com/@gabbytech01
7
3
17
1,424
Lawrence retweeted
Jun 4
Na because I no pay for X premium, X no dey push my posts 💔
1
1
1
25
Lawrence retweeted
Jun 9
Today wasn't about tools or labs.
Took yesterday's phishing incident and rewrote it 3 ways:
→ Technical report for SOC manager
→ Executive summary for CISO
→ Plain English email to the affected user
Same facts. Completely different language each time.
Full Analysis on github
2
4
54
Lawrence retweeted
Jun 9
Anyone studying for Security ?
Dropping a free 100 Questions & Answers practice PDF.
Those are real exam-style scenarios designed to teach how CompTIA expects you to think, not just memorize.
How it works:
• Questions are grouped in sets of 10
• Followed by 10 clear answers and explanations
• Easy to self-check and reinforce weak areas
Covers all Security domains, with extra focus on Security Operations, exactly how the exam is weighted.
Full practice questions PDF:
🔗 artempolynko.com/wp-content/…
1
11
363
Jun 9
Because they don't need to know the PIN itself.
When you create a PIN, the system usually stores a transformed version of it (called a hash), not the actual PIN. When you enter your PIN, it transforms it again and compares the result.
If the results match, it's correct.
3
47
Lawrence retweeted
Jun 8
Biggest lesson: always check attachments. The payload is usually one layer deeper than you expect.
Full analysis: github.com/DevSecLawrence/so…
1
1
31
Lawrence retweeted
Jun 8
Day 24 of my SOC Analyst journey 🔍
Completed BTLO Phishing Analysis — 10/10 points.
The attack had a twist:
→ Delivery failure lure (not a fake login page)
→ Malicious URL hidden inside a NESTED .eml attachment
→ Hosted on Blogspot to abuse Google's trusted domain reputation
1
1
5
106
Jun 8
Day 24 of my SOC Analyst journey 🔍
Completed BTLO Phishing Analysis — 10/10 points.
The attack had a twist:
→ Delivery failure lure (not a fake login page)
→ Malicious URL hidden inside a NESTED .eml attachment
→ Hosted on Blogspot to abuse Google's trusted domain reputation
1
1
5
106
Jun 8
Biggest lesson: always check attachments. The payload is usually one layer deeper than you expect.
Full analysis: github.com/DevSecLawrence/so…
1
1
31