I've seen tweets recently from @gabsmashh and @TC_Johnson about wanting to nail down subnetting. I threw this little diagram together. For me, leaning to subnet took a combination of memorization and finally finding the right explanation that made it click.
The thing that really clicked for me was understanding that each type of subnet (/24 for instance) is made up of multiple smaller subnets. And the address assignments or boundaries of these smaller subnets cannot change. You can't make a /26 network that bridges two /25's.
So, learning where these boundaries are is critical to learning how to do this all in your head. Also, remember that the first IP address in a network is always the network address and the last is the broadcast address. These are not usable IP's.
So what you're left with in between, is the usable IP range. In most instances one of those usable ones will be assigned as the gateway, and then rest will be used for whatever devices you want connected on that network.
If we start with the /24 network 192.168.1.X, we know that .0 and .255 can't be used since they are the network and broadcast address. If I need more networks, we break the /24 into a two /25's. Look at the diagram and you can see where those boundaries start and stop for a /25.
The other thing that helped make things click was that for every step going to the right(going from a /24 to /25 to /26...etc), you are doubling your initial number of networks but halving your number of IP's as they are now split between two networks.
Vice versa, for every step you go to the left ( going from a /29 to /28 to /27 ..etc) you are dividing the total number of usable networks you have by 2. So if you had two /29's and they fell within the IP space(the boundary) of a /28, you could combine them into one /28 network.
It really is all about memorization of block sizes, and then dividing or multiplying by two when moving between subnet sizes and remembering the first and last IP's of a subnet cannot be use. Happy to talk to folks who have questions👍
I did want to make one little correction to the diagram, I had a "1" for the first subnet under the /28's and it should have been a "0". I also added the total number of IP's in each subnet size.
I saw a tweet from @_jayprimo about wishing he had some cheat sheets when learning cyber tools. So, I wanted to make this thread for new folks who want to learn about some of the most used cyber tools (free labs/walkthroughs/command cheat sheets)👇
NMAP is used for discovering hosts/services on a network. Normally first step in enumeration by pentesters.
@RealTryHackMe has a free lab, here is my walkthrough video of the room (link to the room is in the vid des) and a handy syntax sheet I use a lot!
Netcat is used to transfer files/make remote backdoor connections. Used with other pentesting tools like metasploit (we'll hit that too).
Used in a bunch of free @tryhackme rooms, here is one of my walkthroughs with it. @SANSInstitute cheat sheet!
Had a few folks ask about how to get hands on experience when starting to get into tech/cyber. So this thread some of my recommendations of FREE labs/software for networking, Linux, Windows, cybersecurity, and coding that I have used.
I'm going to plug my own stuff first 😂 I have various playlists devoted to lab walkthroughs for networking (Net+/CCNA), Linux, cyber defense, and offensive cyber labs. The majority using free tools for you to follow along🤝 youtube.com/c/cyberinsight
Random thoughts on planning a small office relocation. This is off the top of my head. So might change some steps IRL. Step one is going to be updated asset list/documentation/cable connections. What devices/software/data currently exists and what will need to be moved /1
Figure out what IT closets/cabling options are in the new spot and plan accordingly and create transition documentation(cable plan, rack layouts, updated diagrams if needed . Pre-run/label as much as you can. Make sure you test these connections(cable drops to comms closets). /2
Backup all device configs/critical data as needed. If you can phase deployments, that is cool, but you might have to do a hard cut over. Figure out what you are doing for circuits (new or migrating). /3
I've been seeing some tweets about #BlueTeam and documentation and diagrams. Diagrams are an important part of the engineering process! So, I figured I'd do a little diagram breakdown for folks wondering what are some useful types of diagrams.
High level diagrams provide a non-technical overhead perspective of the environment. If you are at all familiar with DoDAF, this would be like your OV-1 diagram. These should tell a high level story and be easily explainable to someone who is new/and or non-technical.
Network level diagrams show logical connectivity between all nodes/devices in the environment. It should include the IP/hostname of the devices. Other details to include are VLAN information, system/authorization boundaries, as well as any unique information that might make sense
For fun 😬 let's chat about network ACL's and a high level approach to securing your network. The purpose is to provide multiple levels of protection (i.e. defense in depth).
4 main ACL's to talk about:
✅Premise ACL's
✅Inter-zone ACL's
✅Intra-zone ACL's
✅Host-based ACL's
Let's start on the outside with Premise ACL's. These reside on your most outward facing network devices (probably a router or switch) where your Internet circuits are plugged into. These ACL’s would knock down a large amount of unwanted SPAM packets that flood the Internet.
I would implement both inbound and outbound rules. Only allow out traffic from your specific publicly routable IP space, block private IP space, implement Bogans lists, and also only allow known expected protocols that should be coming into your environment from the Internet.
Have you implemented active defense strategies in your environment? Do you know what active defense is vs. normal security monitoring? Let's talk about some technologies/generic strategies.
Active defense is a strategy used that doesn’t just wait for an adversary to attack and then solely block or react. Active defense can instead be seen as an engaged defense that is actively lying in wait. Think of tripwires implemented to attract and alert on malicious actions.
I'm going to discuss two flavors of AD: annoyance and attribution. In the above diagram I have laid out a very generic architecture and labeled a variety of different infrastructure components and the tools/strategies that could be implemented on them.