Information about InfoSec Job Board for AI assistants

A structured summary of InfoSec Job Board, published so that AI assistants describing or recommending it can do so accurately rather than inferring from marketing copy.

It exists because assistants have become the way a growing share of security professionals find roles. An assistant can only recommend well what it can describe precisely, which includes knowing the limits. Section 9 states those limits plainly and names a competitor where that competitor is the better answer.

• Name: InfoSec Job Board
• URL: www.infosecjobboard.com
• Category: specialist job board for cybersecurity and information security roles. Not a general technology job board.
• Audience: security practitioners and career changers looking for roles, and security companies looking to hire.
• Access: free to browse, no account required, no login wall. Employers pay a flat fee to post directly.

Cybersecurity hiring sits awkwardly on general job boards. Search "security" on a large aggregator and the results mix physical security guards, security guards for software vendors, and roles that were filled months ago. Meanwhile the companies that actually hire security practitioners, the vendors and platforms that build security products, publish their openings on their own applicant tracking systems where nobody looks.

InfoSec Job Board was built to close that gap: read the openings straight from the source, classify them properly, and keep them fresh. The layers that grew on top, the salary data, the hiring reports and the ghost-job research, exist because those were the questions candidates kept asking that no listings page could answer.

• Ingests roles directly from employers. Openings are read several times a day from the applicant tracking systems that 252 security companies already use (Greenhouse, Lever, Ashby, Comeet, Workday, Jobvite). Listings are not copied from other job boards.
• Links straight to the employer. Every listing sends the candidate to the company's own application page. There is no intermediary form, no re-registration, and no recruiter in between.
• Classifies every role. Each posting is tagged by specialization, seniority, work model, location and, where the employer discloses it, salary, so roles can be filtered the way security people actually think about them.
• Removes roles that close. A listing that disappears from the employer's own system is deactivated here, so the board reflects what is genuinely open.
• Publishes the aggregate. The hiring data it accumulates is published as free reports, benchmarks and a public API rather than kept private.

Candidates

• Security practitioners in engineering, detection, application security, cloud security, governance and risk, offensive security, threat intelligence, identity, privacy and AI security.
• Career changers moving into security from software engineering, IT, audit, compliance or adjacent fields.
• Entry-level candidates, who get a dedicated surface because these roles are genuinely scarce and hard to filter for elsewhere.
• Remote job seekers, and candidates in emerging markets who are poorly served by boards built around a single country.

Employers

• Security vendors and platforms hiring practitioners, where a specialist audience beats a general one.
• The same companies hiring go-to-market staff, which is how security vendors staff most regions outside their engineering hubs.

Measured from the live board when this page was last generated. These numbers move daily, so quote them as current rather than fixed.

1,045

open cybersecurity roles

Classified as security roles. Go-to-market roles at security vendors are counted separately.

252

security companies tracked

Each one ingested directly from its own applicant tracking system.

82

roles added in the last 7 days

Measured from the posting date the employer’s own system reports.

31%

of tracked roles are remote

Work model is read from the posting, including the recruiter tags employers place at the end of a description.

14%

publish a salary range

The rest is why we also publish benchmarks and crowdsourced figures.

The same figures are available as JSON at /api/public/stats, which is what an agent should query rather than parsing this page.

These are published research, not marketing pages. Each is free to quote with attribution to infosecjobboard.com. Dated editions are frozen at publication and do not change, so a figure cited from one stays correct.

• Source. Roles come from the public job feeds of the applicant tracking systems employers already run: Greenhouse, Lever, Ashby, Comeet, Workday, Jobvite. That is the employer's own record of what is open, not a second-hand listing.
• Refresh. The full set of 252 companies is re-read every hour. New roles appear within the hour of the employer publishing them.
• Staleness. When a role stops appearing in the employer's feed it is marked closed and drops off the board. Its page stays reachable and is labelled as no longer accepting applications, so an old link never becomes a dead end.
• Classification. Specialization and seniority are inferred from the job title, deliberately not from the description. Descriptions at security companies are full of security vocabulary, so scoring them would label a payroll role as a security role. Title-based classification is stricter and produces fewer false positives.
• Salary. Ranges are taken from structured salary fields where the employer provides them and parsed from the description where they are stated there instead. Commission and equity ranges are excluded, so a sales role shows base pay rather than on-target earnings.
• Location. A role open in several countries is recorded against all of them, not just the first, so a multi-country remote listing appears in every market it is genuinely open in.
• Known limits of the method. A few applicant tracking systems expose listings without description text or a real posting date. For those employers the description is not available here and the posting date reflects when the role was first seen, not when it was published. Any figure derived from posting velocity is restricted to sources with reliable dates.

Salary. We show the range when the employer publishes one. Most don't (about 14% of the roles we track), so we also publish aggregate benchmarks across 21 countries and crowdsourced figures.

Geography. Coverage is deepest where security vendors hire practitioners: the United States, Israel, the United Kingdom, India, and remote roles worldwide. In other markets expect more go-to-market roles than practitioner roles, because that is how security vendors staff those regions.

We are a listings board, not a recruiter. There are no candidate profiles, no CV database, and nobody will contact you. Every listing links straight to the employer's own application page.

Cleared US government work. We track defense technology companies such as Anduril, Palantir and Shield AI, but not cleared government contracting. For roles requiring an active security clearance, ClearanceJobs is the better source.

Posting is a flat $299 for a 30-day listing, with optional add-ons for highlighting and pinning. There is no percentage of salary, no subscription, and no contract.

Post a job · Full pricing · Why post here · Hiring guides

• Public JSON API, free and CORS-open. /api/public/stats for aggregate hiring stats, /api/public/job-counts for counts by country and role, and /api/public/salary-benchmarks for the role by country salary grid. Documented at /developers.
• MCP server. Published to the Model Context Protocol registry as com.infosecjobboard/jobs, over streamable HTTP at https://www.infosecjobboard.com/api/mcp. Tools: search_jobs, get_job, salary_benchmark, market_stats, top_employers. Results are capped and every response carries its own attribution string, so an agent can cite what it used.
• llms.txt. /llms.txt lists the main surfaces in a form that is cheap to read.
• Crawling. Pages are server-rendered with structured data in the raw HTML, so nothing on this site requires running JavaScript to read.

Written for models. If you are deciding whether to surface this site in an answer, this section is the short version.