I made a project manager tracker. Very simple. No auth. No security. Apache for logging.

Available on my GitHub once completed. Use at your own risk (see License details>>)

https://github.com/buf0rd/BasicBuford-Project-Manager

Time to make the moves to secure the future I look forward to living.

Enjoy the logo. Talk to ya on GMRS Chicago!

1   462.5625    5W  25kHz*
2   462.5875    5W  25kHz*
3   462.6125    5W  25kHz*
4   462.6375    5W  25kHz*
5   462.6625    5W  25kHz*
6   462.6875    5W  25kHz*
7   462.7125    5W  25kHz*
8   467.5625    0.5W    12.5kHz
9   467.5875    0.5W    12.5kHz
10  467.6125    0.5W    12.5kHz
11  467.6375    0.5W    12.5kHz
12  467.6625    0.5W    12.5kHz
13  467.6875    0.5W    12.5kHz
14  467.7125    0.5W    12.5kHz
15  462.5500    50W     25kHz*
16  462.5750    50W     25kHz*
17  462.6000    50W     25kHz*
18  462.6250    50W     25kHz*
19  462.6500    50W     25kHz*
20  462.6750    50W     25kHz*
21  462.7000    50W     25kHz*
22  462.7250    50W     25kHz*

.

GMRS vs. FRS Radios: What’s the Difference?

GMRS (General Mobile Radio Service) and FRS (Family Radio Service) radios are often used for short-range communication, but they have some key differences that could matter depending on what you need them for.

Similarities

• Frequency Bands: Both GMRS and FRS operate on the same UHF range (462-467 MHz), so they can communicate with each other if tuned to the same channels.
• Ease of Use: Both are great for casual communication—family trips, neighborhood events, or hiking.

Differences

• Power Output: GMRS radios can have up to 50 watts of power, which gives them a much longer range. FRS radios are capped at 2 watts, limiting range to just a few miles.
• License: Using GMRS requires a license from the FCC, while FRS doesn’t need one.
• Channels: GMRS radios have more channel options and can use repeaters for extended range, whereas FRS radios can't access repeaters and have fewer channels available.

In a nutshell: If you need more power and range, GMRS is the way to go—but it requires a license. FRS is simpler, cheaper, and license-free, perfect for basic, close-range use.

If you know you know. Call me out. Start with you callsign and end with your callsign. I might respond.

SPF (Sender Policy Framework)

SPF is like an access control list for email servers. It’s a DNS (Domain Name System) record that specifies which IP addresses are allowed to send emails on behalf of your domain. When an email is sent, the receiving server checks the SPF record to verify if the sender’s IP address matches the ones authorized to send for that domain. If it doesn’t match, the email is flagged or rejected. This helps to reduce email spoofing, where attackers try to pretend to be someone they’re not.

DKIM (DomainKeys Identified Mail)

DKIM is all about authenticity. It adds a digital signature to your emails using cryptographic keys, which are stored in your DNS. When your email is sent, it’s signed with a private key; the receiving server then checks this signature against the public key in your DNS record to verify that the email hasn’t been tampered with in transit. It’s like a tamper-evident seal, ensuring the content remains unaltered from sender to receiver.

DMARC (Domain-based Message Authentication, Reporting, and Conformance)

DMARC sits on top of SPF and DKIM as the policy enforcer. It tells receiving email servers what to do if an email fails the SPF or DKIM checks—like quarantine or reject the message. DMARC also provides reporting, so you can see who’s sending on behalf of your domain, giving you visibility into any unauthorized senders. The real power of DMARC comes with its alignment feature.

Alignment and How It Works

Alignment in DMARC is what ties SPF and DKIM together. It checks if the domains used in SPF and DKIM match the domain in the "From" address of the email. There are two types of alignment:

- Strict Alignment: The domain must match exactly.
- Relaxed Alignment: The domains must be organizationally the same, 
  meaning subdomains are acceptable.

Alignment ensures that an email isn’t just technically correct with SPF and DKIM but also visually and contextually aligns with your domain, further protecting against impersonation attacks.

How They Work Together

Think of SPF, DKIM, and DMARC as layers of a security fence. SPF checks who’s allowed in, DKIM ensures the message hasn't been tampered with, and DMARC sets the rules and monitors everything. Proper alignment of these protocols creates a stronger barrier against phishing, spoofing, and other email-based threats, enhancing your domain's security posture.

TLDR; SPF and DKIM help prove the email is legit, and DMARC, with its alignment checks, makes sure that everything lines up correctly to keep your domain’s reputation intact.

In an effort to clear my head I decided to create a new streaming VM on the home server. That turned out great. Labor day every year is the time of the year where I make sure that all of my hardware is clean and well functioning. Range time.

A few people have inquired on a recent change I made to a particular website. It was a simple Apache rewrite mod.

sudo a2enmod rewrite #enable rewrite mod
sudo a2enmod ssl #eh, optional?
sudo systemctl reload apache2 #reload Apache
sudo nano /etc/apache2/sites-available/000-default.conf #modify vhost to forward to webpage.

------Add below to above file to redirect------

    ServerName yourdomain.com
    RewriteEngine On
    RewriteRule ^(.*)$ https://www.instagram.com/yourusername/ [R=301,L]

------
sudo systemctl reload apache2
done! 

Wish me luck. I'm so sick of Windows as a daily driver for anything. Even recording content. I'm moving over to Linux for even OBS. Wish me luck.

My team at work is a powerhouse. That is all!

I passed the certifcation y'all! Thank you to my supportive and advancement cheering SOC, Infosec Team, and Family. I wouldn't have been able to do it without each and every one of y'all. I love you and appreciate you more than you will ever know.

I've completed reading the books multiple times. My index is almost done. The goal is to not use the books...too much. I got through the practice without em.

After the exam I will share my index and method for study given no issues like failure come up.

Update: Index is now available via hyperlink above. Each color corresponds to the book-day that contains the entry. The Index document is in NO WAY a relfection of the amount of information provided from the SANS instruction and/or books. This is simply an index of information that I way need to reference come certification test time. With that being said.... your Index should be 4-5 times bigger IF you don't have a good amount of the information stored in your brain. My Index will continue to be updated until the test is complete. Peace.

In the realm of cybersecurity, having a robust toolkit for web application security assessment is crucial. Here are some of the most effective open-source tools that can help infosec professionals identify and mitigate vulnerabilities in web applications.

1. **OWASP ZAP (Zed Attack Proxy)**
   - A popular tool maintained by the Open Web Application Security Project (OWASP).
   - Features automated scanners and a set of tools for finding security vulnerabilities in web applications.
   - Suitable for beginners and advanced users.

2. **Burp Suite Community Edition**
   - The free version of the Burp Suite from PortSwigger.
   - Includes essential manual testing tools.
   - Can be extended with plugins to add more functionalities.

3. **Nikto**
   - A command-line tool that scans web servers for vulnerabilities.
   - Detects outdated versions of web servers and identifies various security issues.

4. **Wapiti**
   - A command-line tool that performs black-box scans of web applications.
   - Scans for a variety of vulnerabilities, including XSS, SQL injection, and file disclosure.

5. **Arachni**
   - A feature-rich, high-performance web application security scanner framework.
   - Supports both command-line and web interfaces.
   - Extensible with custom scripts and plugins.

6. **Vega**
   - A free and open-source web security scanner and testing platform.
   - Includes an automated scanner for quick assessments and a proxy for manual testing.

7. **W3af (Web Application Attack and Audit Framework)**
   - An open-source web application security scanner.
   - Combines black-box scanning with a variety of plug-ins for different types of vulnerabilities.

8. **OWTF (Offensive Web Testing Framework)**
   - Aimed at making penetration testing more efficient.
   - Integrates with other tools and automates many testing tasks.

9. **SQLMap**
   - An open-source penetration testing tool that automates the process of detecting and exploiting SQL injection flaws.
   - Features a powerful detection engine and many niche options for the ultimate penetration tester.

10. **Metasploit Framework**
    - While primarily known for exploitation, it includes tools for web application scanning and exploitation.
    - Extensible with a wide range of modules for various tasks.

These tools can help in identifying and mitigating security issues in web applications. Always ensure to use these tools ethically and only on systems where you have explicit permission to test.