Updated by
Hi, I'm Jack, the owner of Cybersecurity Jobs List and co-founder of Himalayas (himalayas.app) and Cavuno (cavuno.com). Across all my platforms, I work with application security daily: dependency vulnerability scanning, secure authentication, API security, and data protection across hundreds of thousands of users. My technical background is in computer science (UNSW). I studied security engineering and computer networks, and worked as a research assistant on VR experiments that were published in the Journal of Experimental Psychology. I also work with cybersecurity hiring data every day, tracking which companies are posting, what certifications actually appear in listings, how salaries differ by sub-discipline and clearance level, and where the talent gaps are widest. That combination of security practice, engineering at scale, and daily immersion in hiring data shapes the content on this site. I'm currently based in Sydney, Australia.

This is an archived record of Cybersecurity Jobs List's 31 July 2026 inventory snapshot. The original report recorded 5,181 published listings. Those figures describe what the board reported at that time, not jobs available today or a representative measure of cybersecurity employment.
Correction, 30 September 2026: the original work-arrangement counts add to 5,171, leaving a difference of 10 against the reported total. We cannot establish the cause from the retained summary. We have also withdrawn the role-level salary averages because we could not reproduce them from the original listing records and filtering rules available for this review. The historical counts below remain labeled as originally reported, rather than newly verified observations.
For opportunities you can assess now, browse current cybersecurity listings and check the employer's original posting. For preparation, use our SOC analyst career guide or guide to getting into cybersecurity.
What the July report recorded
The original summary described published listings captured on 31 July 2026 UTC. Published status is not independent confirmation that every employer was still accepting applications. The figures have not been replaced with today's inventory.
| Original measure | Originally reported count |
|---|---|
| Published listings | 5,181 |
| Listings included in the USD annual salary sample | 1,180 |
| Remote label | 596 |
| Hybrid label | 1,314 |
| On-site label | 3,261 |
| Senior label | 2,893 |
| Mid-level label | 1,488 |
| Entry or junior label | 310 |
The three work-arrangement rows total 5,171. We have not assigned the unexplained difference of 10 to a category. The three listed seniority rows total 4,691, leaving 490 outside those displayed rows; the retained summary does not explain their classification. An entry-level label does not establish that a role required no experience, and a remote label does not establish worldwide eligibility.
Role groups and salary sample counts
The original report said it assigned each listing to one primary group using its title. These role counts sum to 5,181, and the salary sample counts sum to 1,180. That arithmetic is consistent. It does not independently validate the classification, deduplication or individual salary records.
| Original role group | Reported listings | Reported salary sample |
|---|---|---|
| Security engineer | 870 | 278 |
| Security analyst | 524 | 138 |
| GRC / compliance / risk | 445 | 90 |
| SOC / cyber ops | 369 | 67 |
| Pentest / red team | 51 | 4 |
| IR / threat hunt / detection | 43 | 7 |
| Cloud security / DevSecOps | 15 | 5 |
| AppSec / product security | 12 | 2 |
| Other titles | 2,852 | 589 |
The large “Other” group limits any conclusion about which specialties dominated the board. We have removed the earlier explanation attributing its higher pay to leadership roles because that explanation was not demonstrated by the retained evidence. These counts should not determine which career you choose.
What we can and cannot establish about the method
The original method described employer-posted USD annual minimums and maximums, with extreme outliers removed. It did not provide enough detail in the retained report to reproduce the salary cohort: the exact outlier rules, geographic mix, duplicate treatment and row-level inputs are unavailable for this review. We cannot confirm the claimed exclusion of sales and go-to-market roles across the whole snapshot.
The old salary columns were described as separate arithmetic means of advertised minimums and maximums. Even if reproduced correctly, those two averages would not form a median wage, an overall minimum-to-maximum range, or the middle 50% of salaries. They would summarize the endpoints in that particular set of advertisements.
For comparison, the Bureau of Labor Statistics defines mean wages and percentile wages separately; the median is the 50th percentile. A job-ad endpoint average and an occupational wage estimate answer different questions. We have removed the old national wage figure from this archive rather than presenting it alongside unverified board averages.
A reproducible replacement would need the original records, capture time, inclusion rules, deduplication method, currency and pay-period handling, role assignments, geography and missing-data counts. A new snapshot cannot repair the historical calculations without those inputs.
How to compare salary information in your search
Use current, relevant postings to build a shortlist. Compare work you could accept in the same location and at a similar level, then keep the compensation terms visible. A high figure attached to a different geography, seniority or contract arrangement may tell you little about your own options.
- Record the currency and whether the amount is hourly, monthly or annual.
- Separate base pay from bonus, commission, equity and other compensation where the employer states them.
- Keep employment type, expected hours, shifts and on-call duties beside the pay.
- Check whether one advertised range covers several locations or levels.
- Mark an undisclosed salary as unavailable, not zero, and ask about the range when appropriate.
If you calculate a summary for your shortlist, name the measure and show the number of comparable postings. Do not label the midpoint of an advertised range as the salary a successful candidate will receive. The employer's offer and your circumstances determine that outcome.
Find current roles and practical career guidance
Open current SOC analyst jobs to compare duties, location requirements and compensation where supplied. Read the source description before treating a title or board label as proof of eligibility.
For a broader starting point, our cybersecurity entry guide helps you connect a target role with evidence of your skills. This July archive remains available to explain the historical report and its correction; it is not a current salary benchmark.


