Bug Report for Rae Version 1.0

Dear future-me, 
Authentication To prove it's really you opening this email, what was your first instinct when you heard Damilola drop the line "You must always have the mindset to find the vulnerability" [LINK placeholder with the intention to insert a "Bring it on!" GIF but not actually included] --- 

Bug Report for Rae Version 1.0 Subject: Self Upgrade Cycle - Ticket #2025-11-S3Lf Assignee: future-me Severity: High Priority: High Status: In Progress Environment: Object works from home M-F 9-5 GMT+4, studies from home, after hours. distractions include netflix bingewatching, overcooked on PS2 with spouse, and 3 needy dogs Visual Artifacts 
[POSTMAN_WORKSPACE_SNAPSHOT_PLACEHOLDER] // no image attached because I'm not paying FutureMe for that lol
[BURPSUITE_PROXY_SNAPSHOT_PLACEHOLDER] // image intentionally missing to avoid subscription fees
This was how your Postman workspace and Burp Suite looked today, 24th November 2025 — untainted, unseasoned, proto-you, naive, innocent, human-error prone, misconfigured, default.
DescriptionObject = Rae (present-me)Version = 1.0 Target Object (Intended Recipient) = Version 2.0 (future-me)
Properties 

• Initialized with baseline knowledge only, with minimal entropy. 
• API-security inexperienced, lacking domain awareness. 
• No prior exposure to offensive testing workflows. 
• Current state exhibits low context, no API threat-modeling capabilities, and limited to zero familiarity with HTTP workflows. 
• Lacks vulnerability-seeking mindset.  

Remediation Requires minimum **12-week structured training plan and iterative skill hardening 
Current Bugs

• Systemic Procrastinator (chronic) 
• Impostor Syndrome - known recurring bug Critical technical gaps in Cyber Security API domain knowledge

Planned Fixes

•  Master content and application from API Security Fundamentals Training 
• Take CASA Exam 
• Take all available courses on APISec University and validate knowledge 

Expected Features on next iteration

•  VT-01: Demonstrate knowledge with accountability (Advocate for API Security, Make learning public)

• RT-01: Offensive Operations Capability Feature (Red Team Validation - API checkup kit) 

Future object should be able to demonstrate operational proficiency with a curated toolset for API offensive testing. This includes intercepting, manipulating, fuzzing, enumerating, and exploiting API endpoints with controlled precision.

• BT-01: Defensive and Secure Design Competency (Blue Team Validation - Champion Secure Design Models) 

Future object should exhibit mature understanding of API security from a defensive and design-first perspective, informed by GRC knowledge and formal security frameworks. 

• BT-02: Governance, Risk and Compliance Integration (API-Sec-Specific GRC) 

Future object should be able to incorporate API-security knowledge into governance processes, bridging offensive findings with risk ratings and remediation planning 
QA Test to confirm success on expected features
VT-01 Validation 

• Continuous posting on Ghost blog about learning journey 

RT-01 Validation 

• Create and Maintain a documented master list of offensive tooling and can articulate when and why each is used (Burp Suite, Postman advanced flows, JWT tooling, auth bypass methods, recon suites, fuzzers, etc.) 
• Map list against MITRE's CAPEC (latest available version during review relevant to API attack patterns) 
• Can execute end-to-end attack chains (auth/authz testing, BOLA detection, misconfig exploitation) 
• Demonstrate the ability to validate security controls by recreating realistic attacker behavior, not just checklist testing 

BT-01 Validation 

• Can perform structured API security assessments at the design phase (threat modeling, data-flow review, etc.) 
• Understands how to embed secure patterns into development lifecycles 
• Applies requirements from the OWASP API Security Top 10 and broader secure-development standards as part of practical decision-making. 
• Can translate security findings into actionable, developer-friendly controls and governance requirements 

BT-02 Validation 

• Can produce structured reports that align real-world API vulnerabilities with governance frameworks 
• Demonstrates the ability to influence secure design decisions early, not after deployment  

Authorization 
If you're reading this and have successfully completed the course and can confirm the following conditions (similar to permissions), then you are authorized to proceed 

• All Planned Fixes 
• Expected Features 
  
• Pass on all QA Tests 

Complete Success -> Change request with comments Rae Version 2.0 achieved 

“On success, emit a mental webhook to past-you (version 1.0) confirming the upgrade was applied.”
MENTAL_WEBHOOK:
  Rae v1.0 → Rae v2.0
  API-sec baseline: ACHIEVED
  API Journey Milestone #1: COMPLETED
  XP: <enter total accumulated XP here – confirm with Precious (Success Advisor)>
// XP field intentionally left blank – complete this when you read this, Object v2.0.

Next update Object version 3 

• Take ACP 

Version 2.0 is achieved automatically upon successful completion of all Planned Fixes, Expected Features, and QA Tests. 
Version 3.0 represents the next scheduled upgrade cycle. 
------------------------------------------------------
Failure to upgrade
If you’re reading this and nothing changed, consider this email a SIEM alert. (Object didn't behave as expected, life is out of compliance, and anomalous signature detected).
Corrective Actions

• Open a ticket and explain why you're still the same version and have not deviated from the baseline v1.0 state.
• Lack of progress is anomalous behavior, please investigate yourself.
• If you still procrastinate, that's a major incident, fix immediately 24–48 hours SLA, to remain compliant with strict and self imposed and demanding standards.
• RCA is due in under 30 minutes or this will be escalated to your conscience.

Severity Classification: P1 – Human Regression  
Congratulations, you just became the incident. 
Add a checksum: "Future me: if you’re reading this, hash your current feeling; if it matches being overwhelmed as a beginner, then something went wrong.  If hash mismatch → proceed with upgrade verification.”
Roll Back Process 

• Risk consideration - initiate mitigation plan (no acceptance of failure).
• Business Impact Severity - Threat to employability.
• Impact: High if issue remains unresolved.

Fallback Action 

• Have a classic autistic meltdown, recharge your spoons,lift your chin and hyperfocus on different passion, maybe AI cybersecurity? LOL
• Become a dog walker

Disclaimer 
_“If you found this message intact after the duration of the training, your archive policy needs review. Retention: 6 months minimum.”_ 
“This document complies with self-inflicted audit standards.”

------------------------------------------------------ MONITORING AND LOGS

[24-NOV-2025 09:12:03] INITIAL_COMMIT_LOGGED
Present-me initialized future-me bug report.
Status: OK
Notes: Formatting questionable.

[25-NOV-2025 10:48:54] UNAUTHORIZED_FORMATTING_MODIFICATION
Object re-opened asset and modified content.
Behavioral drift detected: "QA engineer with emotional damage" mode activated.

[25-NOV-2025 11:02:17] EXCESSIVE_VERIFICATION_LOOP
Object re-opened the asset again to "check alignment."
Flagged: SEVERITY=MEDIUM | Category=ADHD Behavior | Code=OCD-001

[25-NOV-2025 11:15:41] ALERT_FATIGUE
Multiple system alerts ignored.
Message ignored: "Stop tweaking, it's perfect!"

[25-NOV-2025 12:04:20] AUDIT_TRAILS
Observation: "80% of edits were emotional, not functional."

[25-NOV-2025 12:23:58] SIEM_NOISE
19 formatting events detected within 45 minutes.
Correlation: OBSESSIVE_COMPULSIVE_HEURISTIC triggered.

[25-NOV-2025 13:01:09] ANOMALY_DETECTION
Overconfidence spike followed immediately by regret.
Pattern matched: 27 previous incidents.

[25-NOV-2025 14:44:36] FALSE_POSITIVE
Reported indentation error was not real.
RCA: PECBAK (Problem Exists Between Chair And Keyboard).

[25-NOV-2025 15:22:11] HEALTH_CHECK
Memory Leak detected.
Thought loop: "Why are my standards calibrated for gods?"

[25-NOV-2025 16:03:55] RATE_LIMITING
Resource capacity boundaries enforced.
System: Stabilized.

# Locate FutureMe tab
PID=$(ps aux | grep "Web Content" | grep -v grep | awk '{print $2}')

# K i l l that emotional support tab
sudo /k/i/l/l -9 $PID

# Log the object out gracefully
Object="present-me"
loginctl terminate-user $Object