• Skip to primary navigation
  • Skip to main content
Cleared Cyber Security Jobs | CyberSecJobs.com

Cleared Cyber Security Jobs | CyberSecJobs.com

Cleared Cyber Security Jobs

  • Home
  • Search Cleared Cyber Jobs
  • Job Fairs
  • Career Resources
You are here: Home / Salary Guides / Cybersecurity Salary Data Sources You Can Actually Verify

Cybersecurity Salary Data Sources You Can Actually Verify

Verify cyber pay with BLS occupation data, OPM tables, public postings, and contract records—without mixing unlike measures.

7 min read October 21, 2026 Salary Guides
What’s inside
  1. What is the BLS Information Security Analysts median pay for 2025 and 2026?
  2. What claim are you actually trying to test?
  3. How do you read the occupation behind BLS data?
  4. Should you use national, state, or metro estimates?
  5. How should you use OPM pay tables?
  6. What can a public job posting prove?
  7. Why must bill rates stay separate from salaries?
  8. How should you publish a reproducible salary number?
  9. Frequently Asked Questions

The BLS Information Security Analysts median pay is $129,180 for May 2025. That remains the wage vintage shown on the BLS occupation page in 2026. The page’s update year is not the measurement year, and the figure is an occupation-wide national median, not a current offer or a cleared-cyber salary.

Definition: Confirm the occupation behind a salary claim before copying its number.

Vintage: Record the reference period, not merely the webpage’s update date.

Scope: Keep national, local, industry, federal-pay, posting, and contract measures separate.

Limit: State the source’s limits beside the figure.

For employers
Hiring cleared cyber professionals?
Post your cleared cyber req where security-cleared candidates already search.

Post a Cleared Job

For job seekers
Cleared and working in cyber?
Browse cleared cyber roles from employers hiring right now.

Browse Cleared Cyber Jobs

What is the BLS Information Security Analysts median pay for 2025 and 2026?

BLS reports $129,180 as the May 2025 national median annual wage for Information Security Analysts. Its page was updated in 2026, but that does not turn the observation into a 2026 wage estimate.

A page revision year can differ from the wage estimate’s reference period. Search results may label a page with the year it was revised, while the pay statement names an earlier period. Cite both when needed: source accessed in 2026; wage estimate for May 2025.

Use the BLS OEWS data application to reproduce occupation and area estimates. Preserve the occupation title, geography, measure, reference period, and retrieval date. A screenshot without those fields is hard to audit later.

Source What it can establish What it cannot establish alone
BLS OEWS Occupation wage estimates by defined geography Cleared-role premium, education effect, or your offer
OPM pay table Published pay for a covered grade, step, and area Private contractor pay or total federal compensation
Job posting The advertised range and conditions for a requisition Accepted pay or market average
Contract record Procurement scope, ceiling, award, or labor-rate evidence as stated An employee’s salary
Crowdsourced report A self-reported observation under its methodology A verified population estimate without supporting design

What claim are you actually trying to test?

Write the claim before opening a salary site. Name the role, geography, employer type, experience level, clearance condition, pay component, and date. Then choose a source that measures the same thing.

“What does cybersecurity pay?” is not reproducible. “What is the latest national occupational median for Information Security Analysts?” points to BLS. “What is the published General Schedule pay for this vacancy’s grade, step, and duty station?” points to the announcement and OPM. “What ranges are local employers advertising for cleared SOC roles?” requires a documented posting sample.

A good source cannot rescue a mismatched question. National Information Security Analyst data should not be relabeled as penetration-tester pay. A Washington locality table should not be applied to a duty station in another pay area. A senior requisition does not estimate junior compensation.

The cybersecurity salary overview can help identify variables, but any figure used in negotiation should be traced to a source whose population and date you can state in one sentence.

How do you read the occupation behind BLS data?

Open the occupation definition and duties, then decide whether they match the work being discussed. Record the occupation code and avoid forcing niche titles into a broad category without disclosing the proxy.

OEWS classifies workers by the tasks employees are paid to perform. Employer titles can be inconsistent. A “security engineer,” “ISSO,” “SOC analyst,” or “threat analyst” may or may not fit the Information Security Analysts occupation depending on duties and coding.

BLS states that OEWS produces employment and wage estimates for occupations at national, state, metropolitan, and nonmetropolitan levels, plus national industry estimates. The survey does not gather demographic information, and its tables are organized by occupation, industry, and area. They therefore cannot tell you what holders of a particular certification or degree earn.

Also check the pay concept. OEWS wages exclude employer benefit costs and several forms of premium or bonus pay. A base-salary offer plus benefits should not be declared below market merely because it differs from a wage estimate using another compensation definition.

Should you use national, state, or metro estimates?

Use the geography that matches the claim and has a published estimate. National data provide context; state and metro data better reflect a local labor market. Do not switch levels simply because one produces a more attractive number.

Record whether the estimate is cross-industry or industry-specific. Location and industry answer different questions. If a niche industry estimate exists only nationally, label it national rather than placing it beside a local cross-industry figure as if both dimensions matched.

Do not treat a percentile as an experience band. A lower percentile is not formally “entry level,” and an upper percentile is not automatically “senior.” The wage distribution describes workers in the occupation, not standardized career stages.

The cleared cybersecurity salary guide offers market context across roles. For a claim you intend to defend, preserve the original table or posting and document every adjustment rather than relying on a secondary label.

How should you use OPM pay tables?

Use OPM tables only when a federal position is covered by that pay system. Match the announcement’s grade, step assumptions, duty station, locality area, special-rate information, and effective year. Do not apply General Schedule tables to contractor salaries.

OPM’s 2026 General Schedule page publishes a base table and locality tables by geographic area. The actual vacancy may cite a range spanning grades or steps. Read the announcement for promotion potential, appointment type, and duty location.

Base pay and locality-adjusted pay are not interchangeable. Nor is salary the entire value of a federal offer. Benefits, leave, retirement, incentives, work schedule, and employment protections require separate evidence and personal valuation.

If a vacancy uses a different pay system or a special rate, follow the announcement’s references. Never select the ordinary General Schedule row because it is familiar. The covered agency and position determine the applicable table.

What can a public job posting prove?

A posting proves that an employer advertised a range for a defined requisition under stated conditions. It does not prove what the selected candidate accepted, what incumbents earn, or what another employer will offer.

Collect postings with discipline. Save the URL, employer, requisition identifier, title, location, remote status, date, range, pay period, experience, clearance, shift, and duties. Remove duplicates and expired reposts that represent the same seat.

For federal roles, start at USAJOBS search results and open the full announcement. For contractors, use the employer’s own career page to verify an aggregator lead. A range without the posting’s location and seniority is barely usable.

Do not average posted minima and maxima and call the result market pay. Wide ranges can cover levels, locations, or candidate variation. Report the distribution of posted bounds separately and disclose the collection method.

Why must bill rates stay separate from salaries?

A contract price or labor rate is not an employee’s wage. It may include overhead, benefits, paid leave, management, facilities, profit, risk, and other costs. Use contract records to understand procurement, not to infer take-home pay.

SAM.gov Contract Opportunities describes its records as federal procurement notices, including solicitation and award notices. Those documents may reveal labor categories, requirements, ceilings, or evaluated rates. Read the exact schedule and unit before quoting anything.

A ceiling rate is not necessarily the amount billed. An amount billed is not the amount paid to a worker. A total award is not annual payroll. Each conversion adds assumptions, so stop at the measure the document actually supports unless you have primary evidence for the next step.

How should you publish a reproducible salary number?

Put the number beside its source, reference period, population, geography, pay concept, and limitation. Save enough detail that another reader can retrieve the same table and understand why you selected it.

A defensible note might read: national median annual wage for the Information Security Analysts occupation, May 2025 OEWS estimate; not specific to cleared work, experience level, education, or total compensation. Include that limitation with the figure and keep the original export with your research notes.

For a posting sample, document search terms, sites, collection dates, inclusion rules, deduplication, and sample size. For federal pay, name the table, year, grade, step, locality, and any special rate. For a contract record, name the notice or award and the field quoted.

The cleared job salary estimator can structure candidate-specific questions. Keep its output separate from directly observed source data, and treat assumptions as assumptions rather than verified pay.

Take one salary figure from your current job search and write its source card now: claim, measure, role, geography, reference date, retrieval date, and limitation. If any field is blank, do not use the number in negotiation yet.

CyberSecJobs.com and ClearedJobs.NET connect cleared cyber talent with the employers who need it.
Whether you are hiring for a cleared cyber req or holding a clearance and looking, start here.

Post a Cleared JobBrowse Cleared Cyber Jobs

Frequently Asked Questions

Is $129,180 the 2026 BLS median for Information Security Analysts?

No. BLS identifies $129,180 as the May 2025 national median annual wage. The occupation page was updated in 2026, but the update date does not change the estimate’s reference period.

Does BLS publish pay specifically for cleared cybersecurity roles?

OEWS published tables are organized by occupation, industry, and area, not clearance status. Any use for cleared work is a broader occupational proxy and must be labeled that way.

Can I treat a posted salary range as the accepted salary?

No. It documents the range advertised for that requisition and its stated conditions. Accepted pay, incumbent pay, and total compensation require different evidence.

Can an OPM table estimate contractor pay?

No. OPM pay tables apply to covered federal positions and pay systems. A contractor employee is paid by the employer under separate compensation arrangements, even when working beside federal employees.

What should I verify first when I see a salary claim?

Check the occupation or role definition and the measurement date. Then verify geography, pay concept, population, and source methodology before comparing it with another figure.

Salary Guides

  • Facebook
  • Instagram
  • LinkedIn
  • Twitter
  • YouTube

Cleared Cyber Security Jobs | CyberSecJobs.com

  • Contact
  • About
  • Privacy Policy