Lawrence

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

Installed Splunk Enterprise on my Ubuntu VM today. Network was 45Kbps all day so the BOTS dataset download is still running, I wasnt able to finish it . But Splunk is up and running on localhost:8000. Tomorrow the actual queries start. #SOCAnalyst #Splunk

@MTNNG please nau😭😭😭

@dhruvkumar1805 github.com/DevSecLawrence

finally hit 50 followers 🎉 didn't go viral, didn't do anything special just showed up every day drop your GitHub below, let's connect there too👇

@prettycyb3rgirl Seriously

@only_Lawrence Jeez, no wonder they are hard to get rid of

Did you know: A bedbug can survive up to 6 months without feeding

@buildwithsid github.com/DevSecLawrence

kindly share your github profile i wanna judge you

@simply_eju As I see this thing, na once I burst 😂😂😂😭

See kolu😂😂

@cyber_razz Congratulations 🎉🥳

I’m baccccccckkkkkkkkkkkkkk

.@cyber_razz has been restored 🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥

@cyber_razz @elormkdaniel github.com/DevSecLawrence…

So when I generated a user.info message: Facility = 1, Severity = 6 PRI = (1 × 8) + 6 = 14 I also generated messages at all 8 severity levels using the logger command — from emergency (0) all the way to debug (7). All 8 showed up in /var/log/syslog including debug

Today I learned how syslog actually works under the hood. Every syslog message has a PRI value that encodes two things at once — the facility (what system sent it) and the severity (how serious it is). Formula: PRI = (Facility × 8) + Severity

Everyone talks about SIEMs. Nobody talks about how the logs actually get there. Windows doesn't speak syslog. Cloud doesn't push logs to you. Network devices lose logs if your collector goes down. The SIEM is just the end of a pipeline.

@Ozed385 @BlockchainUNN @remitano Nice