Pinned Tweet
@Ninadivall001 @cyber_razz @elormkdaniel @mcloxyventures @ireteeh @TemitopeSobulo Hey, start learning CISSP alongside this. It will really help you since it covers a bird’s-eye view of cybersecurity.
3
0
8
1,136
Danyal khan retweeted
A Deep Dive into Mobile Forensics
I recently completed a full mobile forensic analysis on an iPhone 13 Pro and it was a powerful reminder of how much a device actually remembers.
This was an advanced logical extraction with verified image integrity. Even without diving into lone told a story.
From location artifacts, I reconstructed where the device had been, the routes it traveled and the exact timestamps tied to those movements. But more importantly, I could see how those locations were generated.
Some coordinates were tied to ride activity such as uber and bolt. Others came from navigation searches. Some were linked to shared live locations inside messaging apps.
Each source leaves a different footprint. A searched address tells a different story than an active trip. A shared live location suggests intentional disclosure. The coordinates are only part of it, the behavior behind them is the real evidence.
The “most visited locations” view made patterns obvious. Certain coordinates appeared repeatedly, building a clear picture of routine and frequency over time.
On the communication side, interaction volume alone highlighted the primary contacts. Without even reading conversations, it was immediately clear who the highest frequency messaging relationships were. Volume builds pattern. Pattern builds context.
Call analysis went just as deep. Even when call entries were deleted, I could still determine whether interactions were audio or video, which platform they occurred on, how long they lasted, and whether they were answered, missed or rejected. Deleting a visible log doesn’t erase the underlying artifacts.
I was also able to recover delivered media, expired content, deleted messages and metadata tying everything to specific timestamps and user actions.
Here’s what stands out. Phones don’t just store content. They store behavior.
They store routine. They store intent.
Files can be deleted. Logs can be cleared. But the artifacts remain.
#digitalforensics #DFI #mobileforensics #cybersecurity
I recently completed a full mobile forensic analysis on an iPhone 13 Pro and it was a powerful reminder of how much a device actually remembers.
This was an advanced logical extraction with verified image integrity. Even without diving into lone told a story.
From location artifacts, I reconstructed where the device had been, the routes it traveled and the exact timestamps tied to those movements. But more importantly, I could see how those locations were generated.
Some coordinates were tied to ride activity such as uber and bolt. Others came from navigation searches. Some were linked to shared live locations inside messaging apps.
Each source leaves a different footprint. A searched address tells a different story than an active trip. A shared live location suggests intentional disclosure. The coordinates are only part of it, the behavior behind them is the real evidence.
The “most visited locations” view made patterns obvious. Certain coordinates appeared repeatedly, building a clear picture of routine and frequency over time.
On the communication side, interaction volume alone highlighted the primary contacts. Without even reading conversations, it was immediately clear who the highest frequency messaging relationships were. Volume builds pattern. Pattern builds context.
Call analysis went just as deep. Even when call entries were deleted, I could still determine whether interactions were audio or video, which platform they occurred on, how long they lasted, and whether they were answered, missed or rejected. Deleting a visible log doesn’t erase the underlying artifacts.
I was also able to recover delivered media, expired content, deleted messages and metadata tying everything to specific timestamps and user actions.
Here’s what stands out. Phones don’t just store content. They store behavior.
They store routine. They store intent.
Files can be deleted. Logs can be cleared. But the artifacts remain.
#digitalforensics #DFI #mobileforensics #cybersecurity
62
295
1,517
136,469
I just published Understanding the CIA Triad: The Foundation of Cybersecurity
medium.com/p/understandin…
medium.com/p/understandin…
0
0
0
11
I just published 𝐓𝐡𝐢𝐧𝐤𝐢𝐧𝐠 𝐚𝐛𝐨𝐮𝐭 𝐂𝐈𝐒𝐒𝐏? 𝐇𝐞𝐫𝐞’𝐬 𝐰𝐡𝐚𝐭 𝐈’𝐯𝐞 𝐥𝐞𝐚𝐫𝐧𝐞𝐝 medium.com/p/-e0019fd61dd…
0
0
0
6
Humans speak to ChatGPT.
ChatGPT talks to Python.
Python commands C.
C whispers to Assembly.
Assembly nudges Binary.
Binary bends Physics.
Physics drives the universe.
Abstraction all the way down.
ChatGPT talks to Python.
Python commands C.
C whispers to Assembly.
Assembly nudges Binary.
Binary bends Physics.
Physics drives the universe.
Abstraction all the way down.
1
0
5
69
Day 23/365
– Set up an Elasticsearch cluster and connected it to Kibana. Seeing it come alive was satisfying.
– Indexed sample data via Elasticsearch API, Kibana file upload, and Bulk API. Structured indexing = faster retrieval.
– Explored Kibana dashboards, visualizations, ogs into actionable insights.
#CyberSecurity #SOC #SIEM #Elasticsearch #Kibana #LogAnalysis #BlueTeam #InfoSec
– Set up an Elasticsearch cluster and connected it to Kibana. Seeing it come alive was satisfying.
– Indexed sample data via Elasticsearch API, Kibana file upload, and Bulk API. Structured indexing = faster retrieval.
– Explored Kibana dashboards, visualizations, ogs into actionable insights.
#CyberSecurity #SOC #SIEM #Elasticsearch #Kibana #LogAnalysis #BlueTeam #InfoSec
0
0
5
71
Day 22/365
– Learned what SOC Engineers really do: watch everything, all the time.
– Lots of logs, lots of threats, zero breathing room.
– Tools everywhere.... and they all look important.
– Analysts watch. Engineers build.
SOC feels like sysadmin work... but with alarms that actually mean danger. 😅
– Learned what SOC Engineers really do: watch everything, all the time.
– Lots of logs, lots of threats, zero breathing room.
– Tools everywhere.... and they all look important.
– Analysts watch. Engineers build.
SOC feels like sysadmin work... but with alarms that actually mean danger. 😅
0
0
6
40
>NASA runs Linux.
>Servers at Google run Linux.
>Amazon’s cloud runs Linux.
>Netflix streaming backend runs Linux.
>Most supercomputers run Linux.
>IoT devices run Linux.
>Android phones run Linux.
>Web servers, databases, >containers, Docker - all mostly Linux.
- still not convinced to learn Linux?
>Servers at Google run Linux.
>Amazon’s cloud runs Linux.
>Netflix streaming backend runs Linux.
>Most supercomputers run Linux.
>IoT devices run Linux.
>Android phones run Linux.
>Web servers, databases, >containers, Docker - all mostly Linux.
- still not convinced to learn Linux?
>NASA uses JavaScript
>Figma is JavaScript
>VS Code is JavaScript
>Slack is JavaScript
>Discord is JavaScript
>Notion is JavaScript
>Google Docs is JavaScript
>Trello is JavaScript
>Chrome Extensions are JavaScript
>Uber frontend is JavaScript
>Airbnb frontend is JavaScript
>Netflix UI is JavaScript
>Every major web framework is JavaScript
>Every browser speaks JavaScript
-still, you are not convinced to learn JavaScript?
0
0
5
67
Day 21/365
– Started Elasticsearch for SOC Engineers today.
– Learned how clusters + shards keep data scalable.
– Filebeat/Metricbeat made log collection feel effortless.
– Real-time threat detection finally makes sense.
Funny thing:
I used to chase logs. Now Elastic chases them for me.
– Started Elasticsearch for SOC Engineers today.
– Learned how clusters + shards keep data scalable.
– Filebeat/Metricbeat made log collection feel effortless.
– Real-time threat detection finally makes sense.
Funny thing:
I used to chase logs. Now Elastic chases them for me.
0
0
4
116
One Advice to My Younger Self
– Start building earlier.
– Stop waiting for "perfect".
– Nobody cares if it’s messy - they only care if it exists.
What’s the one thing you’d tell your younger self before starting?
– Start building earlier.
– Stop waiting for "perfect".
– Nobody cares if it’s messy - they only care if it exists.
What’s the one thing you’d tell your younger self before starting?
1
0
4
45
Day 20/365
– Revised CIA triad concepts
– Got started with Python (basic syntax stuff)
– Installed Nginx + set it up as a reverse proxy
– Write some Python notes for GitHub
Funny thing: Python feels friendly.....until the tabs betray you.
– Revised CIA triad concepts
– Got started with Python (basic syntax stuff)
– Installed Nginx + set it up as a reverse proxy
– Write some Python notes for GitHub
Funny thing: Python feels friendly.....until the tabs betray you.
1
0
3
60
Day 19/100
– Studied SCADA in more depth
– Solved a DSA question
– Still waiting for the universe to send me a "You're doing great" notification.
#100DaysOfCyberSecurity #DSAJourney #ConsistencyWins
– Studied SCADA in more depth
– Solved a DSA question
– Still waiting for the universe to send me a "You're doing great" notification.
#100DaysOfCyberSecurity #DSAJourney #ConsistencyWins
0
0
1
46
Day 18/100
Explored SCADA/ICS further, digging into the Purdue model
Practiced DSA patterns
Worked on firewall configurations in RHEL 7
Wrapped the day ticking off 3/3 tasks
Explored SCADA/ICS further, digging into the Purdue model
Practiced DSA patterns
Worked on firewall configurations in RHEL 7
Wrapped the day ticking off 3/3 tasks
0
0
1
45