Security Clearance Levels Australia: 2026 Reference Guide
Security clearance levels Australia: Baseline, NV1, NV2 and PV limits, typical requirements, and ICT job eligibility.

AGSVA completed a record 83,727 security clearances in 2024–25, according to its annual update. For Australian Government ICT recruitment, clearance isn't a niche administrative detail. It determines which classified work a person can undertake and can materially affect when a contractor is ready to start.
Understanding security clearance levels in Australia means separating access permission, candidate eligibility and delivery timing. A technically strong software engineer might not meet a role's security requirement, while a suitable applicant who needs vetting might not be available within the project's onboarding window. This reference explains how to make those distinctions when assessing government ICT jobs and contracts.
Table of Contents
- Security Clearance Levels Australia at a Glance
- Which Clearance a Government ICT Role Needs
- How Long a Clearance Lasts and What It Costs
- How to Get a Security Clearance in Australia
- Clearance Timelines and Planning Start Dates
- Clearance Status and ICT Candidate Eligibility
- Verifying Clearance Status Before You Present a Candidate
- Match Your Clearance Level to Open Government ICT Roles
Security Clearance Levels Australia at a Glance
Australia has four established security clearance levels, defined by the Australian Government Security Vetting Agency: Baseline, Negative Vetting Level 1 (NV1), Negative Vetting Level 2 (NV2) and Positive Vetting (PV). Their ongoing access ceilings are set out below.
- Clearance level — Ongoing access up to — Temporary access — Status note
- Baseline — PROTECTED — No higher-level temporary entitlement specified in the level definition — Minimum level for ongoing PROTECTED access
- Negative Vetting 1 (NV1) — SECRET — Limited temporary access to TOP SECRET in specified circumstances — Ongoing access up to SECRET
- Negative Vetting 2 (NV2) — TOP SECRET — Subject to the resource's access controls — Ongoing access up to TOP SECRET
- Positive Vetting (PV) — TOP SECRET, including some caveated resources — Subject to the resource's access controls — Described as being replaced by TS-PA
The table summarises AGSVA's clearance definitions, not an independent permission to access a particular system. Its temporary-access column shouldn't be read as a workaround for a role's stated ongoing clearance requirement.
What the levels actually mean
A clearance is an access-related security assessment, not another qualification on a CV. Unlike a certification in Microsoft Azure or Kubernetes, it relates to the sensitivity of government resources someone may be authorised to use.
That distinction matters when shortlisting ICT contractors. A candidate with Baseline clearance can't automatically satisfy an NV1, NV2 or PV requirement, regardless of their technical experience or previous government assignments.
Nor does the shared TOP SECRET ceiling make NV2 and PV interchangeable. PV includes access to some caveated resources, so a recruiter shouldn't collapse both into a single top-level clearance category.
Reading rule: Identify the classification of the work first, then identify the lowest clearance whose access ceiling meets it. Confirm any additional conditions before deciding that a candidate qualifies.
Where TS-PA fits
AGSVA separately describes Top Secret-Privileged Access (TS-PA) as the future replacement for the current PV model, managed by the Australian Security Intelligence Organisation's TS-PA Vetting Authority. Treat that as a transition requiring current guidance, not a reason to relabel a candidate's existing clearance.
For a role naming PV or TS-PA, confirm the exact requirement with the hiring entity. Don't assume that an older advertisement, a historical contract description and the current access requirement use equivalent terminology.
Across the established levels, the ordinary entry pathway involves government sponsorship or authorisation, Australian citizenship, completed pre-employment screening and a checkable background, subject to approved eligibility arrangements. These are entry conditions rather than a promise that clearance will be granted.
This 2026 reference reflects the publications available for this guide. Clearance definitions and transition arrangements can change, so check AGSVA's current guidance before making a hiring or access decision.
Which Clearance a Government ICT Role Needs
The classification of the information determines the minimum clearance, not the job title. The Protective Security Policy Framework classification policy sets the following requirements for ongoing access.
- Information classification — Minimum clearance for ongoing access — Also check
- OFFICIAL and OFFICIAL: Sensitive — None where entity employment screening is sufficient — Confirm the entity's screening requirement
- PROTECTED — Baseline — Need-to-know determination
- SECRET — NV1 — Need-to-know, and any caveats that may require more
- TOP SECRET — NV2 — Caveated or codeword information may need additional briefings and potentially PV
Read the row for the highest classification the worker must access, rather than the classification most frequently encountered. A role isn't suitable for a lower-cleared candidate because most of its daily tasks involve less sensitive material.
This also explains why government software developer jobs, cybersecurity jobs and technical architect jobs don't each have a universal clearance level. The same technical occupation can support different systems, information holdings and access arrangements.
What the table doesn't authorise
A clearance alone doesn't open every document or system at its classification. The entity must also establish need-to-know, meaning the person needs that information to perform their authorised work.
Temporary access requires supervision. Caveated or codeword information can introduce additional briefings and controls, and may require a different clearance arrangement from the classification-only minimum.
For recruiters, the practical distinction is between meeting a personnel-security threshold and receiving actual access. Keep those decisions separate in candidate notes and client conversations.
A government DevOps example
Say a cloud engineer will maintain deployment pipelines for a system handling SECRET information. The ongoing-access minimum is NV1, plus the appropriate need-to-know and any additional controls, even if the advertisement says only that applicants must be security cleared.
Strong Azure, Terraform or Kubernetes skills don't resolve an access mismatch. Equally, an NV1 holder shouldn't be described as authorised for the environment until the client confirms the relevant access conditions.
If the advertisement and contract notice disagree, ask the panel agency to resolve the discrepancy before presenting the candidate. Don't choose the lower requirement because it makes the shortlist easier to fill.
Record the requirement properly
Use structured fields rather than a single security-cleared checkbox:
- Classification: Record the highest classification the role touches.
- Minimum clearance: Capture the client's explicit personnel-security requirement.
- Access conditions: Note caveats, codewords, facility restrictions and required briefings.
- Access pattern: Distinguish ongoing access from a specifically authorised temporary arrangement.
- Confirmation owner: Identify who can resolve security questions for the hiring entity.
For a closer comparison of the most commonly confused entry requirements, use the NV1 versus Baseline clearance guide. The important recruiting habit is to translate the advertisement into an explicit access requirement before comparing CVs.
How Long a Clearance Lasts and What It Costs
A clearance works like a timed access pass, not a lifetime badge. The level follows the classification of the work. The revalidation cycle then decides how long that pass can support a placement before the evidence behind it has to be renewed, which is what sets a realistic start date.
AGSVA publishes maintenance intervals that sit apart from the first vetting decision. Those intervals are what recruiters should plan against. Fees change, so candidates and sponsors should check AGSVA's current fee schedule rather than treating an old dollar figure as the cost of the role.
- Clearance level — Revalidation interval
- Baseline — Every 15 years
- NV1 — Every 10 years
- NV2 — Generally every 5 to 7 years
- Positive Vetting (PV) — Generally every 5 to 7 years, plus an annual security appraisal
Higher clearances take more vetting effort. That extra time is a hiring constraint as well as an access rule. If a supplier needs a candidate to step up a level, the usable start date is the date access can be used, not the date the CV looked suitable.
Confirm the current AGSVA fee schedule, and confirm who pays with the sponsoring organisation. The candidate is not automatically the payer.
Revalidation is a placement-management issue
The level printed on a CV does not show whether that clearance will still cover the contract. You also need its current status and where it sits in the revalidation cycle, checked through the authorised verification process.
An approaching revalidation point is a reason to talk, not a reason to drop the person. Ask the responsible security contact what action is underway and whether it changes the proposed start.
A revalidation date is a planning checkpoint. It isn't, by itself, evidence that a clearance has already lapsed or that access will automatically stop.
On a longer ICT engagement, name one person who tracks maintenance milestones. If nobody owns that date, the recruitment team can finish the first check and leave delivery unaware that access may need action mid-contract.
Keep three facts separate in your records: historical clearance held, current clearance status, and maintenance required. A line that says "previously held" does not show present eligibility, and it does not show that the revalidation cycle still fits the engagement.
The budgeting question is wider than the first invoice. Does this placement have a confirmed security pathway that can be maintained for the whole piece of work? If that pathway cannot be maintained, the start date offered to the client is not a real start date.
How to Get a Security Clearance in Australia
A candidate usually doesn't apply alone. Under the PSPF personnel eligibility and suitability requirements, an Australian Government security clearance must be sponsored by a government entity or otherwise authorised by the Australian Government; individuals generally can't independently obtain one to improve their employability.
The pathway starts with a genuine requirement and an authorised sponsor.
Follow the sponsored pathway
- Confirm the role and sponsor. Establish why the role requires classified access and identify the sponsoring department, agency or authorised employer. A recruiter expressing interest in a candidate isn't the same as confirmed sponsorship.
- Complete the required pre-employment screening. The entity must confirm this before seeking a clearance, so treat it as a prerequisite rather than paperwork that can be left until after vetting.
- Confirm Australian citizenship. The sponsoring entity checks the citizenship requirement before submitting the request. Don't infer citizenship from where a candidate lives or where they previously worked.
- Establish that the applicant has a checkable background, unless the sponsoring entity has approved an eligibility waiver. Identify gaps in available records early, without trying to make the suitability decision yourself.
- The sponsor initiates the request, and the applicant completes the vetting application with the information and supporting documents AGSVA requires. Accurate, consistent records help the applicant respond clearly.
- AGSVA assesses the application. An application in progress isn't a granted clearance, so keep the candidate's recruitment status separate from their vetting status.
- If granted, maintain the clearance. Record the relevant maintenance arrangements and confirm access separately with the hiring entity.
Prepare records without promising an outcome
ICT contractors commonly enter this pathway through a sponsoring department or authorised employer connected to a role. A software professional doesn't become clearance-ready merely by deciding to pursue government work.
Before the application, candidates can organise their employment chronology and identify missing records. The StoryCV guide to employment history is a practical resource for reconstructing dates and employers, but it doesn't replace AGSVA's instructions or documentary requirements.
Candidates exploring entry-level classified work can also consult the Baseline security clearance guide. When discussing a potential role, ask explicitly whether the employer will consider applicants who need sponsorship rather than assuming every Baseline advertisement offers it.
Citizenship is an entry condition, not a guarantee of clearance. Non-citizens shouldn't assume routine eligibility; check AGSVA's current non-citizen sponsorship guidance before relying on an exception.
For a recruiter, a suitable candidate with no sponsor and no active clearance belongs in a developing pipeline. They aren't yet a placement with a dependable security-related start date.
Clearance Timelines and Planning Start Dates
An NV2 contractor is rarely free to start on the day a client names. AGSVA's published timeframes list the assessment targets and last-12-month medians in the table below, including an NV2 median above its target. That guidance also allows applicants up to 20 business days to complete an application, and it aims to assess completeness within a further 10 business days. Those two stages sit before assessment. The clearance level matches the classification of the work, and that level is what pushes a realistic start date out.
- Clearance level — Target assessment (business days) — Last 12-month median (days) — Planning implication
- Baseline — 20 — No median published — Target only; allow a buffer for the full pathway
- NV1 — 70 — 70 — Median matches target; add pre-assessment time
- NV2 — 100 — 104 — Median runs above target; forecast beyond 100 days
- Positive Vetting (PV) — 180 — 180 — Long lead time; prioritise existing holders
Neither the target column nor the median column is a guaranteed delivery date. Medians move, so recheck the live figures before you commit a placement date.
Build a forecast around the whole pathway
A clearance target works like a council assessment clock. It starts once the file is complete, not when the interview ends. Counting 70 business days forward from an NV1 interview, then promising that date, skips sponsorship confirmation, record gathering and the completeness check.
Document checks, referee replies and interviews can slow the file after that. The candidate's own calendar is a separate constraint. Notice periods and an existing contract do not pause because vetting has a published target.
Write the forecast as explicit assumptions:
- Security pathway: Is the required clearance already held, or does vetting still need to start?
- Application readiness: Are the supporting records available, and can the candidate respond promptly?
- Outstanding actions: Who owns each document, referee or interview dependency?
- Work availability: When could the candidate leave the current engagement?
- Client readiness: Has the hiring entity confirmed the remaining onboarding requirements?
Communicate uncertainty before submission
Where the work needs a prompt start, prioritise candidates who already hold an active clearance at the required level. That removes the vetting wait. It does not remove verification of the clearance, or the hiring entity's onboarding.
Planning advice: Describe an unconfirmed date as conditional, and state the unresolved dependency. Don't present a vetting target as a commitment from the hiring entity.
For a candidate who needs an upgrade, explain the timing risk before you request consent to represent them. The client should know whether they are filling a near-term seat or investing in a longer pathway.
Set a firm start date only when the security pathway and the other onboarding dependencies are confirmed. If the campaign slips, read AGSVA's current timeframes again rather than reusing a screenshot from an earlier search.
Clearance Status and ICT Candidate Eligibility
Clearance is an eligibility gate, not a substitute for technical assessment. At erecruit, if an opportunity requires NV1 and the CV doesn't demonstrate NV1 or higher, we don't recommend the role.
Passing that gate doesn't mean a candidate is the strongest engineer, architect or delivery manager. It means the recruitment process can proceed to assess their technical capability, experience, location and availability against the actual opportunity.
Apply the gate to the candidate's actual position
Use distinct recruitment outcomes rather than grouping every interested applicant into the same shortlist:
- Active clearance at or above the requirement: The candidate meets the clearance threshold, subject to verification and the opportunity's specific access conditions.
- Lower clearance than required: Keep the candidate in the pipeline if an upgrade pathway is available. Don't present them as meeting the current requirement.
- No clearance, but a potential sponsored pathway: Treat the candidate as timing-dependent and confirm that the client will consider this pathway.
- Background information that's difficult to verify: Flag the uncertainty early rather than promising routine processing.
- Claimed clearance without confirmation: Hold the recommendation until the appropriate verification is complete.
Say a Python data engineer has relevant government delivery experience but only a lower clearance than the opportunity requires. Their technical fit may justify a future conversation, but it doesn't make them eligible for the present classified assignment.
Ask useful intake questions
The AGSVA applicant guide identifies Australian citizenship and a checkable background as eligibility requirements, requires travel history and passport details for applications, and states that psychological assessment is mandatory for PV and may be required at other levels.
Recruiter intake should establish what needs authorised follow-up, not reproduce the vetting investigation. Ask about the candidate's current level, sponsor, citizenship, countries and periods of residence, document availability and revalidation timing.
Keep questions proportionate to the recruitment decision. Sensitive supporting material should go through the authorised vetting process rather than being collected unnecessarily in a general candidate database.
There is also a commercial eligibility question: most government ICT labour-hire contracts are invitation-only. A candidate meeting the security requirement doesn't establish that a particular supplier is entitled to respond.
A workable shortlist therefore distinguishes candidate clearance eligibility from supplier participation rights. Both need to be resolved before a recruiter treats an opportunity as actionable.
Verifying Clearance Status Before You Present a Candidate
A candidate's claimed clearance isn't evidence of role eligibility. Start with their intake answers, then obtain confirmation through the authorised security process before presenting them as meeting the requirement.
The PSPF direction on online disclosure of clearance and national security information treats disclosure that identifies or implies a person's clearance status online as a security risk. Verification must therefore be accurate without creating unnecessary exposure.
Work through the evidence in order
Use the following checklist before a submission:
- Confirm the required level. Reconcile the role notice, panel-agency instructions and hiring entity's requirement.
- Confirm the sponsor. Establish who supports the candidate's clearance and who can verify its current status.
- Confirm the access context. Check classification, need-to-know arrangements, caveats and facility restrictions with the responsible client contact.
- Confirm maintenance timing. Establish the relevant revalidation position rather than relying on the date shown in an old CV.
- Record the evidence. Note who confirmed each point, when they confirmed it and any unresolved condition.
Ask the candidate for documentary evidence of their level, sponsor and revalidation date where available, using approved secure channels. A candidate-supplied document can support the enquiry, but it shouldn't replace verification by the appropriate authority.
Clearance details are never published on erecruit, and the panel agency verifies the clearance level with the vetting authority. That division of responsibility prevents a CV statement or an automated match from being mistaken for official confirmation.
Keep verification records controlled
Store only the information needed for the recruitment decision in access-controlled records. Minimise clearance details in shared notes, email chains and exported shortlists.
Don't publish an individual's clearance status in public candidate profiles or public responses to job advertisements. Where colleagues need to know whether a submission can proceed, use a restricted workflow status rather than circulating supporting security material.
Verification should answer whether the candidate meets this role's requirement. It shouldn't create a publicly searchable record of their security status.
If verification fails, remove the candidate from the recommendation list and record the reason accurately. Distinguish missing evidence from a confirmed mismatch, because those require different follow-up.
Tell the candidate what authorised confirmation would be needed for reconsideration. Don't pressure them to disclose sensitive information through an insecure channel just to keep the recruitment process moving.
Match Your Clearance Level to Open Government ICT Roles
Use your clearance position to narrow the search before investing time in an application. A focused routine helps technology professionals find relevant work and helps recruiters avoid building shortlists around opportunities they can't progress.
- Confirm your current position. Establish the clearance you currently hold, its status and any relevant caveats through the appropriate security contact.
- Read the role or contract notice carefully. Separate the required clearance from desirable technical experience, and flag any unclear wording before applying.
- Check participation rights. Determine whether the procurement is open to all eligible respondents or limited to invited sellers. A public job advertisement and the underlying government procurement aren't the same participation pathway.
- Search eRecruit's Australian Government ICT jobs and procurement opportunities for a match between your clearance and skills. Use the role requirements, not just the headline, to assess relevance.
- Assess any upgrade pathway realistically. If the opportunity needs a higher clearance, establish whether sponsorship and the proposed delivery schedule make it worth pursuing.
Combine technology intent with access requirements
Be specific about the work you want. Searches for government DevOps jobs, Azure government jobs in Australia, .NET or C# development, cybersecurity, data engineering and technical architecture become more useful when paired with the relevant clearance requirement.
Don't assume that a technology implies a classification. Python, React, Microsoft 365 and Power Platform can appear in very different delivery environments, so read each opportunity on its own terms.
For a concrete agency example, we list 24 open ICT contracts and 26 contracts closed in the last 90 days for Services Australia, Australia-wide, at Baseline clearance. These are live opportunity counts rather than permanent market totals, so check the current listing before acting.
Follow the job and procurement context
Our guide to security clearance jobs in Australia provides a related starting point for a clearance-aware job search. Pair that reading with government ICT job listings, BuyICT procurement opportunities, agency activity and technology searches rather than treating each as a disconnected source.
A role's listed clearance is a minimum requirement, not something strong skills can offset. Recheck it whenever a new advertisement appears or the hiring entity changes the scope.
For recruiters, the final question is practical: can this candidate meet this opportunity's access requirement, through this supplier, within a credible start window? Resolve those points before presenting a match as ready to progress.
erecruit connects Australian Government ICT procurement opportunities with live tender-panel agency job advertisements, helping you assess the role, clearance, location and timing together. Visit erecruit to find relevant government ICT opportunities and focus your next search on work that matches your clearance and technical skills.