Mockingjay Studio — Adelaide, Australia

External security assessments
for Australian MSPs

Penetration testing and white-labelled security reports that MSPs hand to their clients. You send me a domain, I send you back a branded PDF. No setup, no subscription, no learning curve.

Work with me See what I do
12
Security checks per scan
39s
Average scan time
46
AU domains researched
85%
Had no enforcing DMARC

White-labelled security reports for MSPs

12 checks across 6 categories. Each scan produces a branded PDF with an A-F grade, executive summary, detailed findings, and remediation roadmap. Your branding, your client relationship — I'm invisible.

Email Security
SPF, DMARC, DKIM, MTA-STS, TLS-RPT — can anyone impersonate this domain?
Web Security
SSL certificates, CAA records, 6 HTTP security headers
Technology Risks
Fingerprint running software, match to known CVEs (CVSS 7.0+)
Breach Exposure
Active infostealer credentials and historical breach database checks
Network Exposure
Open RDP, SMB, SSH, databases — the #1 ransomware entry points
Compliance Alignment
Mapped to ISM controls and Essential Eight. Honestly states what needs internal review.

How the white-label model works

1

You send me a domain

Your client's domain and your branding config — logo, colours, contact details. One-time setup per MSP partner, reused for every scan.

2

I send you a branded PDF

Professional report with your branding. A-F grade, executive summary, detailed findings, ISM mapping, remediation roadmap. Under 40 seconds.

3

You hand it to your client

Your client sees a report from their MSP. You look like you have in-house security assessment capability. I stay invisible.

Penetration testing

Automated tools catch the obvious. Manual testing catches the dangerous — the logic flaws, the privilege escalation paths, the access control gaps that only surface when a human is thinking like an attacker.

🛡

Access Control Testing

Can a low-privilege user read admin data? Can one user access another's records? I test vertical and horizontal privilege escalation using multiple accounts at different permission levels, comparing what each role can see and do.

🔐

Authentication & Sessions

Password policies, account lockout, session timeout, logout invalidation, concurrent session handling, MFA bypass attempts. I test whether your authentication layer holds under pressure, not just whether the login page works.

💥

Input Validation

Cross-site scripting (XSS), SQL injection, server-side template injection, command injection. I test every input the application accepts — search fields, form submissions, URL parameters, API endpoints.

📄

API & Business Logic

CSRF verification, mass assignment, IDOR, rate limiting, error handling. The kind of flaws that live in the logic layer — where the application does exactly what the code says, but the code says the wrong thing.

How an engagement works

1

Scoping

We define the target, agree on what's in and out of scope, and sign an engagement letter. I'll ask about your architecture so I can focus testing where it matters.

2

Reconnaissance

Passive information gathering — DNS records, technology fingerprinting, subdomain enumeration, public exposure analysis. Understanding the target before touching it.

3

Active Testing

Automated scanning followed by manual testing. I work through the OWASP Web Security Testing Guide systematically — every finding is verified by hand, not just flagged by a tool.

4

Reporting

Professional report with every finding rated by severity, mapped to OWASP Top 10 and ISM controls, with evidence and prioritised remediation. Executive summary for leadership, technical detail for developers.

5

Re-testing

After you've remediated, I re-test the affected areas to verify the fixes hold. The report gets updated to reflect the current state.

Methodology
OWASP WSTG v4.2
Standards
OWASP Top 10, ISM, CWE
Testing type
Grey-box (authenticated)
Approach
Non-destructive
Report format
PDF + machine-readable
Re-testing
Included

What we found scanning 46 Australian SMB domains

Real businesses — law firms, medical clinics, construction companies, financial planners. The results were consistent.

85%
No enforcing
DMARC policy
11%
CRITICAL
risk rating
20%
HIGH
risk rating
0%
Had all 6 security
headers configured
1
Domain with strong
marks — an MSP

Independent. Adelaide-based. Offensive security background.

I'm Jiae Black, the person behind Mockingjay Studio. My background is in offensive security — understanding how attackers think, how credential theft and social engineering work in practice, and how to surface the gaps that most businesses don't know they have.

I apply that perspective defensively — building tools and delivering assessments that make the invisible visible. Recent work includes a grey-box penetration test of an Australian ISM compliance platform and published research across 46 Australian SMB domains.

I work with MSPs because that's where the leverage is. Most Australian SMBs will never hire a security consultant directly. But they trust their IT provider. If that provider can hand them a professional security report with concrete findings and a remediation plan, the conversation changes.

Location
Adelaide, South Australia
Focus
External assessments & pentesting
Market
Australian MSPs serving SMBs
Methodology
OWASP WSTG, ISM, Essential Eight
Compliance
ISM control mapping, E8 alignment
Contact

Ready to talk?

Whether you're an MSP looking for security assessment capability or a business that wants to understand its external exposure — reach out.

jiae@mockingjay-studio.com