Sunday, April 16, 2023

Security Testing Journal Entry | w/e Friday April 14, 2023


Highlights for the week

This post comes a little late, for good reason and part of what went well this week. The majority of time spent was in learning and studying. Definitely need to manage my time a little better. Some days were relegated to single tasks - not a bad thing - at the expense of a few others. Or perhaps, I should learn to quit scheduling so many things per day since two or three things can take up so much of my time. Work in progress.

What We Loved

  1. Hanging out with the family on Friday is always a treasure. Not having a job has been a mixed blessing.
  2. Had a couple of friends check in with my progress regarding the interview. It's what's been keeping me focused.
  3. One of my friends presented a cool opportunity to work voluntarily at a school doing testing things. More on that as details are made known

What We Learned

  1. Network+ - Common Security concepts, which dove-tailed nicely with the modules for Security+
  2. Security+ - Common network attacks. Very interesting things.
  3. Burp Suite - Easy to do XSS attacks. A lot more variations that what I had previously known so that was cool.
  4. Automation - Found some time to clean up my python codebase .. which took longer than expected. Learned Unit test in JEST and Peformance/Load Testing. Need practice!
  5. Cloud Pen Testing - need to retry CloudGoat. Last week's attempt didn't bear much fruit.
  6. Cult.ure - Finished Chapter 6, but left areas for additional details. Will work on it over the weekend.

What We Longed For

  1. More time, and more money. Need to read more.
  2. A proper mentor. My current isn't working, and a new one I'm hunting down is loose on the structure of what to do. TBD

What We Loathed

  1. It has been 3 weeks since I last touched base with the interview I completed. The impression I'm getting is, "I'm being considered, but they're not convinced." WTF to that!

Friday, April 7, 2023

Security Testing Journal Entry | w/e Friday April 7, 2023


Highlights for the week

Had something of an interesting week. More waiting to know if I am hired, but even better networking session with Rhino Security Labs learning about Cloud Pen Testing.

What We Loved

  1. As mentioned above, attended a webinar with some key people from Rhino Security Labs. The topic was setting up an environment in Kali Linux and moving through some of the scenarios. After 2 days of harrasment with my environment, I got it set up and managed to move through the first scenario. I need to revist it when time allows.

What We Learned

  1. Network+ - Moved through another module as it pertained to Wireless Networking and ethernet switching
  2. Security+ - Great learning module as it related to common attacks like XSRF, Buffer Overflow, etc.
  3. Automation - Completed the majority of python tests pertaining to the E-comm website. Need to tackle API testing in python and some negative tests in Cypress
  4. Burp Suite - Finished some DOM-based vulnerabilites. They seemed overly easy
  5. "Cult*ure" - In the middle of writing chapter 5, I folded in an adjunct chapter (4 "All Hands") and had to restructure the layout. New chapter tbd

What We Longed For

  1. Still waiting for a few jobs I applied to 3 weeks ago to reach out. Missing $$
  2. Pursuit of certification is on the horizon: Moving through Network+, but SEC+ and OSCP are the real deal

What We Loathed

  1. Not good karma having to bad-mouth the hiring process at this one company, but after several rounds of interviews, and weeks of waiting, no decision has been finalized and the reply give the impression that they are not convinced even though they state otherwise. If I had other opportunities, I would have ejected long ago.

Saturday, April 1, 2023

Security Testing | Security 4 No0bs - Basic Security Testing with Bug Magnet


Bug Magnet - The best tool a tester can have

What if I told you there's a super-simple tool that is easy to use and requires little to no effort to learn!

And what if I told you, no special downloads, CLI commands, or Kali Linux extensions were necessary!

Look no further .. BUG MAGNET .. is the answer!!

So What Is Bug Magnet?

Bug Magnet is a chrome extension you can use to test form submission and input sanitization. Easily the first step in any manual security testing effort. It features an expansive array of positive and negative test cases for a wide variety of options. Being that this is a security-minded blog post, with a sprinkling of QA, we'll consider a few exploits.

For the purposes of this demo, we are using the practice form here.

Exploit #1 - Buffer Overflow | Goal: Test that form inputs limit character entries to prevent data corruption, crashing the program, or cause the execution of malicious code

What is a buffer overflow? The short-version, a buffer overflow happens when copious amounts of form data is submitted that is more than the allocated memory space (buffer) can handle. For more details, visit OWASP | Buffer_Overflow Vulnerability. How to test:

  1. Visit the form and pick one of any inputs shown
  2. Right-Click into the input to open the context menu - look for bug magnet
  3. Select Text Size and either with spaces or without
  4. Once the text has been entered into the input submit the form
  5. Repeat with another input, or all of them

Exploit #2 - SQL Injection | Goal: Form submissions block excution of queries

What is a SQL Injection? As the name implies, this exploit causes the site to execute a query on submission of the form. For more details, visit OWASP | SQL Injection. How to test:

  1. Visit the form and pick one of any inputs shown
  2. Right-Click into the input to open the context menu - look for bug magnet
  3. Select Format Exploits this opens a tertiary context menu
  4. Select SQL Injection - the first entry in this new context menu
  5. Notice there is a script populating the form - Robert'); DROP TABLE Students;-- this can be modded to reflect a known table in your project codebase
  6. Submit the form, note the outcome - in a perfect situation, nothing should be observed (ie, no harm done!)
  7. Repeat with another input

Exploit #3 - Javascript Injection | Goal: Form submissions block excution of code by escaping special characters as text

What is a Javascript Injection? A javascript injection allows malicious code to execute within a form post-submission. It can be anything from an annoying pop-up alert to a remote-code executable. For more details, visit Portswigger | Javascript Injection. How to test:

  1. Visit the form and pick one of any inputs shown
  2. Right-Click into the input to open the context menu - look for bug magnet
  3. Select Format Exploits this opens a tertiary context menu
  4. Select Javascript Injection - the second entry in this new context menu
  5. Notice there is a script populating the form - alert('Executing JS') --
  6. Submit the form, note the outcome - in a perfect situation, nothing should be observed (ie, no harm done!)
  7. Repeat with another input

Exploit #4 - XSS Injection | Goal: Form submissions block excution of code

What is a Cross-site Script Injection? Cross-Site Scripting (XSS) attacks are a type of injection, in which malicious scripts are injected into otherwise benign and trusted websites. For more details, visit OWASP | XSS Injection. How to test:

  1. Visit the form and pick one of any inputs shown
  2. Right-Click into the input to open the context menu - look for bug magnet
  3. Select Format Exploits this opens a tertiary context menu
  4. Select JS String (XSS) Injection - Single Quote - the third entry in this new context menu
  5. Notice there is a script populating the form
  6. Submit the form, note the outcome -- nothing should be observed (ie, no harm done!)
  7. Repeat with another input
  8. Repeat this above test scenario with JS String (XSS) Injection - Double Quote

Exploit #5 - Broken HTML | Goal: Form escapes any special characters on submission

Broken html and HTML parsing are the lesser of the format exploits provided by Bug Magnet. What these options do is essentially inject simple html characters into an input that is not expected to allow such characters (ex: phone number or email input).

  1. Visit the form and pick one of any inputs shown
  2. Right-Click into the input to open the context menu - look for bug magnet
  3. Select Format Exploits this opens a tertiary context menu
  4. Select HTML Parsing - the fourth entry in this new context menu
  5. Notice there some mild html entered into the form
  6. Submit the form
  7. Repeat with another input
  8. Repeat this above test scenario with Broken HTML option

Security Testing Journal Entry | w/e Friday March 31, 2023


Highlights for the week

In my last post, I wrote about the state of the job market. A week later, and there's news about more layoffs to come. Seems like the Big Boy tech companies overextended their staffing during lockdown, and the consequence of a failed gamble on continued earnings is a reduction in staff to recoup losses. The recurring theme is profits over people. Loyalty be damned! Oh you think being committed to your job buys you immunity? Nope! You think being a lifer in the ranks keeps you safe from the layoff lotto? Try again!

And don't even get me started on performance. What a joke that is. You can be a rockstar, 10x, "ninja" employee hitting all the top marks. That won't guarantee your job is secure. A Performance Improvement Plan - that's just management's cudgel. Push back in the slightest and you're no longer their darling gold-star employee. Now you're a problem that needs to be dealt with.

But it's not all doom and gloom for this guy! With over 100 jobs applied to in the now 7.5 months of unemployment there is at least 1 job in the final rounds of the interview process.

That being said, there was a lot of other cool things that happened this week. Below are some of what went on:

What Went Well

  1. Network+ - Paused on Networking to complete the Google Cloud learning module.
  2. Security+ - Paused on this as well. In it's place were a live Capture The Flag event hosted by Snyk (fun!) and completion of Mitre ATT&CK suite.
  3. Burp Suite - Completed modules for DOM attacks.
  4. Automation - Python is working again and the work to clear out the board is in progress.
  5. The Book - Completed Chapter-5, Chapter-6 is on deck (have notes, will write).
  6. Personal - Finally got around to cleaning up GMail and Outlook. Now there's the bookmarks and Linked-in "saved items".

What We Learned

  1. "Blue Team" tactics and what to look for regarding the 6-step Mitre process.
  2. How google cloud works and what their services offer.
  3. CFT Exercise taught us about JS "prototype pollution" exploit, as well as a python "pickle" exploit for base-64 deserialization.

What We Longed For

  1. A paycheck. The money in my emergency fund is about to run dry in the next few weeks if a job doesn't manifest itself.

Friday, March 24, 2023

Security Testing | Security 4 No0bs - MITRE ATT&CK


Mitre ATT&CK

A brief, high-level "Blue Team" Cybersecurity defense framework. I won't be going too deep into the technicals of how it works, but I will cover some of the basics of what I'm learning. To illustrate the purpose of this framework, let's consider football - namely Offense vs Defense.

What is Mitre ATT&CK

In football, it is super-critical and advantageous for the Defense to know what the Offense is capable of, understand trends, and know how to respond. Basically, situational awareness. The Mitre Adversarial Tactics, Techniques & Common Knowledge is that "situational awareness" concept wrapped in a framework.

Imagine the scneario: 2nd quarter, game is tied, the Offense tends to throw a lot, but the situation warrants a run or run/pass option. As a Defender, it is imperative to know what to anticipate. Blue Team, aka Cybersecurity Defenders, must be able to "read & react" when a situation occurs that warrants further investigation.

The framework consists of 6 different actions to take:

  1. Develop & Update Malicious Activity Model
    • This is like the Defense's playbook. A model is an understanding for what the threat actor is doing, how, and why.
  2. Develop Hypotheses and Abstract Analytics
    • To understand what the Offense might do (or has done), a hypothesis is drafted. The hypothesis must be concise and succinct.
    • Analytics serve to track the "how" of an attack.
  3. Determine Data Requirements
    • There's a long list of criteria that are factored in to writing up a good model, primarily with the efficacy of the data and its source.
  4. Identify and Mitigate Data Collection Gaps
    • Eliminate any likelihood of "escaped" data; that is, any missing or obsolete data from the model
  5. Implement Test Analytics
    • Use the constructed playbook to set up a Defensive posture.
  6. Hunt / Detect Malicious Activity and Investigate
    • Deploy the defense and have Red Teamers test it.

These 6 different actions iterate as many times as necessary. The goal of Defense is to have close to no false negatives for non-detected issues, and true positive results for detected issue (that is to say, Defense caught something truly malicious instead of confusing a benign action as a hostile one). The MITRE framework attempts to aggregate information from a wide array of resources to "read & react" to an event caught by intrusion detection or intrusion prevention system.

Blue Team spots something fishy on their scanners. The investigate and see something is up. Based on the attack pattern and area compromised, they can refer to their model to understand what the attack type is, what it is targeting and why, and how to craft a threat mitigation plan against it.

It is not a hard framework to learn, nor is it overly simplified. But this is a great thing to learn, do, and grow.

Ciao For Now!

Tune in next week, I will give a brief write-up on some cool attacks learned from Security+ and Network+

Security Testing Journal Entry | w/e Friday March 24, 2023


Highlights for the week

At about this time I would be panicking about the fact the money is running out, the refrigerator is near empty, and things aren't getting better.

Not today! Not this week!

This is week has been nothing short of amazing. In the dog house with the missus, but that's a story for another time. I don't have the bandwidth to concern myself with other people's concerns. As the sole bread-winner, I have a responsibility to right this ship and get back on the work path. No more f** ups! My family deserves my best.

Also, there were a couple of great podcasts and seminars I attended this week that have become a huuuuge step forward in my Cybersecurity learnings.

What We Loved

  1. Right off the jump, the "We Hack Purple" & "ThreatX" Podcasts were amazing. They touched on a lot of subjects, primarily focused on the lack of diversity in the field.
  2. Becoming a part of the RHINO community was awesome. Joined their discord server and will network with many in the group as time permits. They do cloud security, but mostly PEN TESTING as well.
  3. Made it to the final stage of my interview at Paperless Post. It's an exciting opportunity to learn something cool and the pay is better than at Tatango.
  4. I've been keeping up with my workouts and forever listening to positive YT channels from time to time. The theme was about "forgiveness" - it's more for you than for them.
  5. Completed "Cult*ure: Chapter 3" Need to be inspired for Chapter 4

What We Learned

  1. Cybrary - completed module 3. The learning continues
  2. Security+ - paused for working through MITRE. Cueued up is "Application Attacks"
  3. Burp Suite - completed modules on OAuth - SSRF attack (basically obtain oauth credentials by way of an image's request url)
  4. Automation - made some basic API tests in CYPRESS. Didn't get very far with Appium on Webdriver or JAVA (the final piece). Python framwork back in working order.

What We Longed For

  1. More time. Not enough hours in the day, and getting up at 4am in this household is improbable.

What We Loathed

  1. N/A .. it has been a pleasant week.

Friday, March 17, 2023

Security Testing Journal Entry | w/e Friday March 17, 2023


Highlights for the week - St. Patrick's Edition

Another quiet week of unemployment. Officially at the 7month mark. To say it's a rough job market is an understatement. We're talking +500 applicants to every job lead. Good news is I have a 2nd interview next week. Gotta make it happen. Meanwhile, lots of great security lessons.


What We Loved

  1. Working out and getting some great rest

What We Learned

  1. For Security+ lots of excitiing things by way of learning about Threat Hunting, Vulnerabilities / Pentesting, and Security Assessments
  2. Google cloud education continued. Some cool lessons on cloud infrastructure and security.
  3. Making great progress on Network+ fundamentals. On to module 2
  4. Interesting thing on the automation front. Next week will be centered on Java and some Appium practice.
  5. Signed up for Cybrary course on Mitre ATT&CK framework. That should be fun.
  6. Some progress on Burp Suite as well. Learned about stealing OAuth credentials by manipulating an image

What We Longed For

  1. Need more time to get back to writing. I have chapter 2 of the book near-complete.

What We Loathed

  1. Unemployment is a bitch! The job search really .. really .. really sucks