Hello again! 

Today, I explored the essential network room of the network monitoring module, which is a good introduction to enterprise networks of all sizes.

Next, I reviewed the Metasploit, Reverse Shell, and SOC work for SEC1. I've almost finished the theory portion and will start practicing once I've completed the remaining modules.

Lastly, I solved the movie problem set and wrote complex queries to obtain the desired results from multiple tables. Tomorrow, I will finish the last problem and move on to the next section.

#Day66 #100DaysOfCybersecurity #Cybersecurity

Hello again! 

Today, I finished and reviewed the Carnage, and went through other concepts about display filtering.

Next, I have completed the songs problem set from CS50, and went through SQL queries.

Lastly, I have took back-up and then updated the BIOS. Not much to share today, but I'll work harder tomorrow.

#Day65 #100DaysOfCybersecurity #Cybersecurity

Hello again! 

Today, I finished the Carnage challenge room. After analyzing the various domains and IPs and going through VirusTotal to analyze malicious traffic and check for infections, I started to figure out how it was carried out.

Before I could move on to CS50, my PC suddenly crashed with a black screen and the message "Stop code: KERNEL SECURITY CHECK FAILURE (0x139)."

Since I had already replaced the faulty RAM with good RAM, I checked the .dmp files to see what could have caused it. All the evidence pointed to the Armory Crate.

So, I have completely uninstalled Armoury Crate and will use my PC as usual to see if the issue is resolved. I have narrowed the issue down to a few possibilities and am very close to figuring out the exact cause. For now, I suspect Armoury Crate because I found people online who reported similar issues due to Armoury Crate.

#Day64 #100DaysOfCybersecurity #Cybersecurity

Hello again! 

Today, I started the Carnage Room Challenge. In this challenge, the infection begins when a victim downloads a zip file containing a document with a macro. Once the machine is infected, it communicates with the domain with an encrypted. I am still halfway through.

Next, I reviewed the cryptography theory, and now I am looking at the practical part, which involves John the Ripper. I learned a lot about symmetric and asymmetric encryption and HMACs.

Then, I configured Obsidian to use Ollama. Since local models aren't powerful, I found a solid use case for them. I'm using them with Obsidian for proofreading technical articles. This boosts my productivity while keeping my data private. I'm using Harper for spell checking and Local GPT for model usage.

I finished the remaining lectures and started working on the SQL Week song problem set.

#Day63 #100DaysOfCybersecurity #Cybersecurity

Hello again! 

Today started off on the wrong foot because there was no power until noon. Despite this setback, I tried to salvage the day. I finished the NetworkMiner room. Then, I installed Wine on my Kali VM to run the NetworkMiner executable.

Next, I watched the CS50 lecture and practiced writing some SQL scripts. I have some experience with SQL from my computer science degree.

Lastly, I participated in the UTCTF and worked on Forensic Challenges involving PCAP files.

#Day62 #100DaysOfCybersecurity #Cybersecurity

Hello again! 

Today I reviewed tools like TCPdump and Nmap, both part of the Cybersecurity 101 networking module. I'm already comfortable analyzing packets with Wireshark, but combining it with the command-line tool TCPdump allows me not only to capture live traffic but also to read and analyze .pcap files directly from the terminal.

Starting tomorrow, I'll move into cryptography theory and begin working with tools like John the Ripper and Hashcat for password cracking practice.

For CS50, I completed the main lecture today. Tomorrow I'll finish the remaining lecture segments and then jump straight into the problem sets.

#Day61 #100DaysOfCybersecurity #Cybersecurity #CS50

Hello again! 

I am happy to announce that I have finally achieved a 100-day streak on TryHackMe! In addition, I reviewed some old concepts with the TryHackMe recap.

I have also reviewed basic networking protocols and practiced with them, such as Telnet, SMTP, and DHCP.

Lastly, I successfully solved the DNA problem set and figured out how to work with dictionaries, iterate through them, and use dictionary comprehension with the CSV module. Tomorrow, I will study and work on the SQL problem set.

#Day60 #100DaysOfCybersecurity #Cybersecurity #cs50

Hello again! 

Today, I reviewed Linux Terminal commands, Command Prompt commands, and finally, PowerShell. Understanding Powershell was extremely useful because I have had less exposure to it than to Terminal and CMD.

After reviewing the CLI material, I moved on to networking concepts with practical use cases. This will greatly boost my learning.

Lastly, I worked on a DNA problem set in the Python section of the CS50 course. I'm working with CSV files and trying to create a program that performs DNA profiling.

#Day59 #100DaysOfCybersecurity #Cybersecurity #cs50

Hello again! 

Started Monday by finishing the remaining Wireshark rooms, covering the last features and protocols. Tomorrow I'll move on to solving some traffic analysis challenges.

I also completed the Readability problem set from CS50 in Python. Next up is the DNA problem set, and after that I'll begin the SQL section.

Lastly, I tracked down the cause of the system instability. After running TestMem5, the issue appears to be RAM-related. I'm now testing each stick individually to determine whether the problem is a faulty module, an unstable stick, or a motherboard slot issue. Once I isolate the cause, I'll address it.

#Day58 #100DaysOfCybersecurity #Cybersecurity #cs50

Hello again! 

Usually, Sundays are more productive because I get extra practice in, but today I ran into an issue.

I started with some challenges from DiceCTF. Specifically, I did the misc challenge with the PCAP file, and then my PC froze.

I checked the event viewer and the disk for corruption, but there were no issues. I also ran the Windows Memory Diagnostic Tool, but it didn't help much.

My last option is to run MemTest86. I plan to run the tests soon. There is a high probability that the issue is caused by faulty or unstable RAM.

#Day57 #100daysofCybersecurity #cybersecurity