Where ASTRA Ready examination objectives relate to concepts in published frameworks. A crosswalk is our own mapping. It is not accreditation, endorsement, equivalence or proof that a credential holder implements the framework.
Crosswalk version 0.2 · reviewed 7 October 2026 · Issued by ASTRA Ready
ASTRA Tech Fundamentals objectives are not yet included.
How to read a row
Direct
— the assessed ASTRA task substantially matches the cited concept at the stated commercial-judgement boundary.
Supporting
— the objective develops judgement relevant to the concept but does not assess performance of the complete framework outcome.
Partial
— one defined aspect overlaps, while substantial professional or operational responsibilities remain outside the ASTRA assessment.
ASTRA Ready has mapped the published examination objectives to concepts in the FinOps Framework 2026 where a real relationship exists. The crosswalk covers areas such as cost units, licensing, forecasting, commitments, governance, architecture decisions and technology value. It helps learners, employers, partners and reviewers see where ASTRA Ready commercial-judgement objectives touch established FinOps practice. It does not mean ASTRA Ready programmes are FinOps Foundation certifications, that the Foundation has reviewed or endorsed ASTRA Ready, or that an ASTRA Ready credential shows full FinOps practitioner competence. Objectives with no FinOps row sit outside the Framework's scope. Labels show whether the connection is Direct, Supporting or Partial. ASTRA Ready records the Framework version and review date and will reassess affected rows when the Framework or the objectives change.
Given a scenario, classify a cloud offer by what its provider and customer actually operate.
The requirement to classify a cloud offer by what its provider and customer actually operate supports FinOps capability Architecting & Workload Placement; ASTRA assesses the related judgement, not full operational ownership.
AssociateAssociate D2.1Relationship: Direct
Given a scenario, compare cloud service boundaries against the customer’s ability to operate them before comparing prices.
The objective directly assesses whether the candidate can compare cloud service boundaries with the customer's operating capability; this corresponds to FinOps capability Architecting & Workload Placement within ASTRA's customer-decision scope.
Given a scenario, separate software rights, one-time delivery and recurring service commitments.
This objective directly assesses whether the candidate can separate software rights, one-time delivery and recurring service commitments; the task matches FinOps capability Licensing & SaaS within ASTRA's commercial scope.
AssociateAssociate D2.4Relationship: Direct
Given a scenario, compare alternative user quantities across an equivalent term.
This objective directly assesses whether the candidate can compare alternative user quantities across an equivalent term; the task matches FinOps capability Licensing & SaaS within ASTRA's commercial scope.
Given a scenario, derive a billable quantity under the specified usage rule.
The objective directly assesses whether the candidate can derive a billable quantity under the specified usage rule; this corresponds to FinOps capability Invoicing & Chargeback within ASTRA's customer-decision scope.
Given a scenario, calculate an in-scope first-year cost without omitting or double-counting included work.
The objective directly assesses whether the candidate can calculate an in-scope first-year cost without omitting or double-counting included work; this corresponds to FinOps capability Unit Economics within ASTRA's customer-decision scope.
AssociateAssociate D5.5Relationship: Direct
Given a scenario, calculate operational effort while separating modeled capacity from realised cash savings.
This objective directly assesses whether candidates can calculate operational effort while separating modelled capacity from realised cash savings; the task matches FinOps capability Unit Economics within ASTRA's scope.
Given a scenario, interpret commitment thresholds and identify unverified financial assumptions.
ASTRA directly assesses whether the candidate can interpret commitment thresholds and identify unverified financial assumptions; that decision matches FinOps capability Rate Optimization at the published assessment boundary.
Given a scenario, interpret commitment thresholds and identify unverified financial assumptions.
This objective supports FinOps capability Forecasting: candidates must interpret commitment thresholds and identify unverified financial assumptions, using related judgement within ASTRA's commercial scope.
Given a scenario, distinguish a spending notification from an enforced limit and sequence the approved response.
Requiring candidates to distinguish a spending notification from an enforced limit and sequence the approved response supports FinOps capability Budgeting; ASTRA tests the related decision rather than complete operational practice.
Given a scenario, recommend a conditional offer using operating fit, cost and documented gates.
The requirement to recommend a conditional offer using operating fit, cost and documented gates supports FinOps capability Planning & Estimating; ASTRA assesses the related judgement, not full operational ownership.
Attribution and reuse+
Framework used: FinOps Framework 2026, including the March 2026 update; reviewed 7 October 2026. The crosswalk uses selected Framework capability names and URLs. The FinOps Foundation licenses Framework content under Creative Commons Attribution 4.0 International (CC BY 4.0), which permits sharing and adaptation, including commercial use, with credit, a licence link and an indication of changes. Attribution: "FinOps Framework by FinOps Foundation." ASTRA Ready adapted selected capability references under CC BY 4.0 and made the mapping judgements independently. ASTRA Ready does not use FinOps Foundation trademarks to suggest endorsement. Mapping an objective to a capability does not make an ASTRA Ready programme or credential a FinOps Foundation programme or certification. Links: https://www.finops.org/framework/ · https://creativecommons.org/licenses/by/4.0/
NIST Cybersecurity Framework (CSF) 2.0
Version 2.0 · 2024 · Reuse: NIST publication (CSWP 29); U.S. Government work, not subject to copyright in the United States; source credit given · Reviewed 7 October 2026
ASTRA Ready has mapped the published examination objectives to concepts in the NIST Cybersecurity Framework (CSF) 2.0 where the assessed commercial judgement relates to a CSF outcome. The crosswalk uses CSF Functions and Categories covering governance, roles and authorities, risk, assets, identity, data security, resilience, incident response and recovery. It helps readers see how selected ASTRA Ready objectives connect to a widely used cybersecurity risk vocabulary. It is not a statement that NIST has reviewed, approved, accredited, certified or endorsed ASTRA Ready or its credentials, and passing an ASTRA Ready examination does not show implementation of the CSF or operation of a cybersecurity programme. Rows are omitted where the relationship would be stretched. ASTRA Ready records the framework version and review date so rows can be reassessed when objectives or CSF resources change.
Given a scenario, distinguish authentication from permission for a named operation.
Here ASTRA directly assesses whether the candidate can distinguish authentication from permission for a named operation; the assessed decision aligns with NIST CSF concept PR.AA at the stated boundary.
AssociateAssociate D3.2Relationship: Direct
Given a scenario, evaluate who is included in an identity-control test and identify coverage exceptions.
ASTRA directly assesses whether the candidate can identify identity-control test coverage and exceptions; that decision matches NIST CSF concept PR.AA at the published assessment boundary.
Given a scenario, translate a described security event into the customer consequence and a testable requirement.
Requiring candidates to translate a security event into customer consequence and a testable requirement supports NIST CSF concept ID.RA; ASTRA tests the related decision rather than complete operational practice.
Given a scenario, trace the actual location and access boundary for each relevant data store or path.
Requiring candidates to trace location and access boundaries across relevant data stores and paths supports NIST CSF concept PR.DS; ASTRA tests the related decision rather than complete operational practice.
Given a scenario, distinguish service restoration time from the point to which data can be restored.
The requirement to separate service restoration time from the recoverable-data point supports NIST CSF concept PR.IR; ASTRA assesses the related judgement, not full operational ownership.
Given a scenario, distinguish service restoration time from the point to which data can be restored.
This objective supports NIST CSF concept RC.RP because candidates must separate service restoration time from the recoverable-data point; the assessment stays within the published commercial task.
Given a scenario, match assurance evidence to the exact control, population, period and claim.
This objective supports NIST CSF concept GV.OV: candidates must match assurance evidence to the exact control, population, period and claim, using related judgement within ASTRA's commercial scope.
AssociateAssociate D8.3Relationship: Supporting
Given a scenario, classify exact questionnaire claims by support, contradiction or missing evidence.
The requirement to classify exact questionnaire claims by support, contradiction or missing evidence supports NIST CSF concept GV.OV; ASTRA assesses the related judgement, not full operational ownership.
Given a scenario, identify who can approve each business, technical and commercial decision.
The requirement to identify who can approve each business, technical and commercial decision supports NIST CSF concept GV.RR; ASTRA assesses the related judgement, not full operational ownership.
Given a scenario, sequence the authorised response to a reported incident without inventing impact findings.
Requiring candidates to sequence an authorised incident response without inventing impact findings supports NIST CSF concept RS.CO; ASTRA tests the related decision rather than complete operational practice.
Attribution and reuse+
Framework used: The NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29, 26 February 2024; reviewed 7 October 2026. The crosswalk maps selected objectives to CSF Functions and Categories (for example GV.RR, ID.RA, PR.AA, RS.CO, RC.RP). It is ASTRA Ready's interpretation and is not an official NIST Informative Reference. NIST Technical Series works authored by NIST employees are not subject to copyright protection in the United States; NIST asks for source credit. Source credit: "Based on The NIST Cybersecurity Framework (CSF) 2.0, National Institute of Standards and Technology, U.S. Department of Commerce." NIST has not reviewed, approved, certified, accredited or endorsed ASTRA Ready. The crosswalk is not CSF implementation evidence. Links: https://doi.org/10.6028/NIST.CSWP.29 · https://www.nist.gov/copyrights-disclaimers
NIST AI RMF 1.0
Version 1.0 · 2023; revision in progress as of 2026-10-07 · Reuse: NIST publication (AI 100-1); U.S. Government work, not subject to copyright in the United States; source credit given · Reviewed 7 October 2026
ASTRA Ready has mapped the published examination objectives to concepts in the NIST Artificial Intelligence Risk Management Framework (AI RMF) 1.0 where the learning and assessment address AI context, governance, measurement, oversight, provider risk or deployment decisions. The crosswalk uses the GOVERN, MAP, MEASURE and MANAGE functions and selected categories. It makes relationships transparent without presenting ASTRA Ready as an AI governance authority or technical AI assurance scheme. NIST has not reviewed, approved, accredited, certified or endorsed ASTRA Ready. Passing an ASTRA Ready examination does not establish organisation-wide implementation of AI RMF outcomes. NIST is revising AI RMF 1.0; ASTRA Ready marks the version used and will review affected rows after the revision is published.
Given a scenario, select a bounded AI use case consistent with approved inputs, reviewer availability and action authority.
This objective directly assesses whether candidates can select an authorised bounded AI use case; the task matches NIST AI RMF concept MAP 1.1 within ASTRA's scope.
Given a scenario, separate retrieved source evidence from model-generated content and unsupported assertions.
The requirement to separate retrieved source evidence from model-generated content and unsupported assertions supports NIST AI RMF concept MAP 2; ASTRA assesses the related judgement, not full operational ownership.
Given a scenario, choose task-sufficient inputs under the stated data-use contract.
Requiring candidates to choose task-sufficient inputs under the stated data-use contract supports NIST AI RMF concept MAP 4; ASTRA tests the related decision rather than complete operational practice.
Given a scenario, test an AI answer against the cited evidence rather than confidence language.
This objective supports NIST AI RMF concept MEASURE 2: candidates must test an AI answer against the cited evidence rather than confidence language; broader operational ownership is not assessed.
Given a scenario, calculate a measured workflow outcome after human review and rework.
Requiring candidates to calculate a measured workflow outcome after human review and rework supports NIST AI RMF concept MAP 3; ASTRA tests the related decision rather than complete operational practice.
Given a scenario, distinguish an instruction embedded in content from valid execution authority.
The requirement to distinguish an instruction embedded in content from valid execution authority supports NIST AI RMF concept GOVERN 2; ASTRA assesses the related judgement, not full operational ownership.
AssociateAssociate D8.4Relationship: Supporting
Given a scenario, apply version-bound human approval to a changed draft or high-impact action.
This objective supports NIST AI RMF concept GOVERN 2: candidates must apply version-bound human approval to a changed draft or high-impact action; broader operational ownership is not assessed.
Given a scenario, convert AI marketing claims into a bounded proposal with evidenced results and open release gates.
This objective directly assesses whether candidates can turn AI marketing claims into a bounded, evidence-based proposal; the task matches NIST AI RMF concept MANAGE 1.1 within ASTRA's scope.
Attribution and reuse+
Framework used: NIST Artificial Intelligence Risk Management Framework (AI RMF) 1.0, 26 January 2023; reviewed 7 October 2026. NIST has stated that AI RMF 1.0 is being revised; ASTRA Ready will re-review affected rows after the revision is published. The crosswalk maps selected objectives to GOVERN, MAP, MEASURE and MANAGE concepts. NIST's own crosswalk pages state that inclusion of a crosswalk does not imply NIST endorsement or comprehensive coverage; ASTRA Ready applies the same boundary. Source credit: "Based on the NIST Artificial Intelligence Risk Management Framework (AI RMF) 1.0, National Institute of Standards and Technology, U.S. Department of Commerce." NIST has not reviewed, approved, certified, accredited or endorsed ASTRA Ready. Links: https://www.nist.gov/itl/ai-risk-management-framework · https://airc.nist.gov/airmf-resources/playbook/
NICE Workforce Framework for Cybersecurity
Version SP 800-181 Rev.1; Components v2.2.0 · 2026 · Reuse: NIST publication (SP 800-181 Rev. 1, Components v2.2.0); U.S. Government work, not subject to copyright in the United States; source credit given · Reviewed 7 October 2026
ASTRA Ready has mapped the published examination objectives to concepts in the NICE Workforce Framework for Cybersecurity where ASTRA Cybersecurity Sales Specialist objectives and selected ASTRA Tech Sales Advisor objectives overlap established cybersecurity Work Roles or Competency Areas. The crosswalk uses NIST SP 800-181 Rev. 1 with NICE Framework Components v2.2.0. It describes occupational proximity; it does not turn ASTRA Ready credentials into NICE Work Roles, job qualifications or cybersecurity certifications. NIST and the NICE Program Office have not reviewed, approved, accredited, certified or endorsed ASTRA Ready. ASTRA Tech Sales Associate objectives are not mapped to NICE. ASTRA Ready will review the crosswalk when NICE Framework Components change.
Framework used: Workforce Framework for Cybersecurity (NICE Framework), NIST SP 800-181 Rev. 1, with NICE Framework Components v2.2.0 (28 April 2026); reviewed 7 October 2026. The crosswalk maps ASTRA Cybersecurity Sales Specialist objectives and selected ASTRA Tech Sales Advisor objectives to Work Roles and, where relevant, Competency Areas. ASTRA Tech Sales Associate objectives are not mapped to NICE. Work Roles describe areas of work, not job titles, and NIST notes that assessment typically occurs at the Task level; ASTRA Ready therefore records Work Role relationships as Partial unless a narrower relationship is stated. Source credit: "Based on the NICE Workforce Framework for Cybersecurity, National Institute of Standards and Technology, U.S. Department of Commerce." NIST and the NICE Program Office have not reviewed, approved, certified, accredited or endorsed ASTRA Ready. A mapping does not establish that a credential holder performs the full Work Role. Links: https://www.nist.gov/itl/applied-cybersecurity/nice/nice-framework-resource-center/nice-framework-current-versions
ASTRA Ready has mapped the published examination objectives to concepts in ESCO, the European classification of Skills, Competences, Qualifications and Occupations, where a defensible relationship exists to ICT sales occupations or skills. The crosswalk uses ESCO v1.2.1 and its concept URIs for occupations and skills such as ICT account management, ICT business development, presales, customer-needs analysis, business analysis, project management and ICT risk management. It makes the relevance of assessed activities easier to understand across roles and countries. It does not state that the European Commission has approved, accredited, certified or endorsed ASTRA Ready, and an ESCO relationship does not mean an ASTRA Ready credential qualifies a holder for an occupation. This publication uses the ESCO classification of the European Commission.
Given a scenario, trace the components supporting a customer-facing feature and distinguish their jobs.
This objective supports ESCO occupation "ICT presales engineer": candidates must trace the components supporting a customer-facing feature and distinguish their jobs, using related judgement within ASTRA's commercial scope.
AssociateAssociate D1.2Relationship: Supporting
Given a scenario, trace a user request to its confirmed business result and identify an unverified hand-off.
This objective supports ESCO occupation "ICT presales engineer": candidates must trace a user request to its confirmed business result and identify an unverified hand-off; broader operational ownership is not assessed.
AssociateAssociate D1.5Relationship: Supporting
Given a scenario, classify a cloud offer by what its provider and customer actually operate.
This objective supports ESCO occupation "ICT presales engineer": candidates must classify a cloud offer by what its provider and customer actually operate; broader operational ownership is not assessed.
Given a scenario, interpret the sending and receiving API contracts and identify necessary field or meaning translations.
This objective supports ESCO skill "interpret technical requirements": candidates must interpret the sending and receiving API contracts and identify necessary field or meaning translations; broader operational ownership is not assessed.
Given a scenario, distinguish authentication from permission for a named operation.
This objective supports ESCO skill "manage digital identity": candidates must distinguish authentication from permission for a named operation, using related judgement within ASTRA's commercial scope.
AssociateAssociate D3.2Relationship: Partial
Given a scenario, evaluate who is included in an identity-control test and identify coverage exceptions.
This objective partially overlaps ESCO skill "manage digital identity" through the need to identify identity-control test coverage and exceptions, while broader operational practice remains outside ASTRA.
Given a scenario, interpret freshness and response-time evidence without conflating display responsiveness with current data.
This objective supports ESCO skill "perform data analysis": candidates must interpret freshness and response-time evidence without conflating display responsiveness with current data; broader operational ownership is not assessed.
AssociateAssociate D2.3Relationship: Supporting
Given a scenario, derive a billable quantity under the specified usage rule.
Requiring candidates to derive a billable quantity under the specified usage rule supports ESCO skill "perform data analysis"; ASTRA tests the related decision rather than complete operational practice.
AssociateAssociate D2.4Relationship: Supporting
Given a scenario, compare alternative user quantities across an equivalent term.
The requirement to compare alternative user quantities across an equivalent term supports ESCO skill "perform data analysis"; ASTRA assesses the related judgement, not full operational ownership.
Given a scenario, compare cloud service boundaries against the customer’s ability to operate them before comparing prices.
Requiring candidates to compare cloud service boundaries with the customer's operating capability supports ESCO skill "perform business analysis"; ASTRA tests the related decision rather than complete operational practice.
AssociateAssociate D2.2Relationship: Supporting
Given a scenario, separate software rights, one-time delivery and recurring service commitments.
The requirement to separate software rights, one-time delivery and recurring service commitments supports ESCO skill "perform business analysis"; ASTRA assesses the related judgement, not full operational ownership.
AssociateAssociate D2.6Relationship: Supporting
Given a scenario, interpret commitment thresholds and identify unverified financial assumptions.
This objective supports ESCO skill "perform business analysis" because candidates must interpret commitment thresholds and identify unverified financial assumptions; the assessment stays within the published commercial task.
Given a scenario, translate a described security event into the customer consequence and a testable requirement.
This objective partially overlaps ESCO skill "implement ICT risk management": candidates must translate a security event into customer consequence and a testable requirement, while full framework practice remains outside ASTRA.
AssociateAssociate D3.4Relationship: Partial
Given a scenario, distinguish service restoration time from the point to which data can be restored.
Asking candidates to separate service restoration time from the recoverable-data point partially overlaps ESCO skill "implement ICT risk management", while full role or framework performance remains outside ASTRA.
AssociateAssociate D8.2Relationship: Partial
Given a scenario, sequence the authorised response to a reported incident without inventing impact findings.
This objective partially overlaps ESCO skill "implement ICT risk management": candidates must sequence an authorised incident response without inventing impact findings, while full framework practice remains outside ASTRA.
Given a scenario, trace the actual location and access boundary for each relevant data store or path.
This objective partially overlaps ESCO skill "manage ICT data classification": candidates must trace location and access boundaries across relevant data stores and paths, while full framework practice remains outside ASTRA.
AssociateAssociate D4.3Relationship: Supporting
Given a scenario, choose task-sufficient inputs under the stated data-use contract.
This objective supports ESCO skill "manage ICT data classification": candidates must choose task-sufficient inputs under the stated data-use contract, using related judgement within ASTRA's commercial scope.
Given a scenario, match assurance evidence to the exact control, population, period and claim.
This objective partially overlaps ESCO skill "manage IT security compliances": candidates must match assurance evidence to the exact control, population, period and claim, while full professional practice remains outside ASTRA.
Given a scenario, distinguish an instruction embedded in content from valid execution authority.
This objective supports ESCO skill "identify ICT security risks" because candidates must distinguish an instruction embedded in content from valid execution authority; the assessment stays within the published commercial task.
Given a scenario, construct a bounded integration or data-flow claim from the supplied component evidence.
This objective supports ESCO skill "propose ICT solutions to business problems": candidates must build a bounded integration claim from supplied component evidence, using related judgement within ASTRA's commercial scope.
AssociateAssociate D5.2Relationship: Supporting
Given a scenario, identify a test and delivery-scope decision before promising the customer an integrated outcome.
This objective supports ESCO skill "propose ICT solutions to business problems": candidates must identify the test and scope decision needed before promising integration; broader operational ownership is not assessed.
AssociateAssociate D5.3Relationship: Supporting
Given a scenario, recommend a conditional offer using operating fit, cost and documented gates.
This objective supports ESCO skill "propose ICT solutions to business problems": candidates must recommend a conditional offer using operating fit, cost and documented gates; broader operational ownership is not assessed.
Given a scenario, turn a vague customer request into a measurable acceptance criterion.
This objective supports ESCO skill "perform customers' needs analysis": candidates must turn a vague customer request into a measurable acceptance criterion, using related judgement within ASTRA's commercial scope.
AssociateAssociate D6.1Relationship: Supporting
Given a scenario, identify the highest-value unresolved discovery question behind a customer request.
Requiring candidates to identify the highest-value unresolved discovery question behind a customer request supports ESCO skill "perform customers' needs analysis"; ASTRA tests the related decision rather than complete operational practice.
AssociateAssociate D6.2Relationship: Supporting
Given a scenario, identify who can approve each business, technical and commercial decision.
This objective supports ESCO skill "perform customers' needs analysis" because candidates must identify who can approve each business, technical and commercial decision; the assessment stays within the published commercial task.
Given a scenario, distinguish reseller, referral and separately contracted service responsibilities.
This objective supports ESCO occupation "ICT business development manager" because candidates must distinguish reseller, referral and separately contracted service responsibilities; the assessment stays within the published commercial task.
AssociateAssociate D7.2Relationship: Supporting
Given a scenario, apply permission and approval limits to a partner claim or customer message.
This objective supports ESCO occupation "ICT business development manager": candidates must apply permission and approval limits to a partner claim or customer message; broader operational ownership is not assessed.
Given a scenario, prepare a conditional buyer/partner handover naming evidence, unresolved gates and next owners.
This objective supports ESCO skill "manage ICT project": candidates must prepare a conditional buyer/partner handover naming evidence, unresolved gates and next owners, using related judgement within ASTRA's commercial scope.
AssociateAssociate D8.4Relationship: Supporting
Given a scenario, apply version-bound human approval to a changed draft or high-impact action.
This objective supports ESCO skill "manage ICT project": candidates must apply version-bound human approval to a changed draft or high-impact action, using related judgement within ASTRA's commercial scope.
Attribution and reuse+
Classification used: ESCO v1.2.1, last updated 10 December 2025; reviewed 7 October 2026. The crosswalk uses selected ESCO occupation and skill concepts and their persistent URIs. ESCO is developed by the European Commission, which allows ESCO to be linked with other classifications for mapping purposes. Under Commission Decision 2011/833/EU the classification may be reused free of charge subject to acknowledgement and clear indication of adaptations. Acknowledgement: "This publication uses the ESCO classification of the European Commission." ASTRA Ready's relationship labels and rationales are ASTRA Ready's adaptations, not statements by the European Commission, which has not approved, accredited, certified or endorsed ASTRA Ready. An ESCO occupation mapping does not mean a credential qualifies a holder for that occupation. Links: https://esco.ec.europa.eu/en/use-esco · https://eur-lex.europa.eu/eli/dec/2011/833/oj
What this page is not
Not accreditation by any framework owner.
Not an informative reference accepted by NIST.
Not a FinOps Foundation programme.
Not a NICE work-role qualification.
Not an ESCO occupational qualification.
ASTRA Ready credentials are issued by ASTRA Ready and verified at /verify.
This publication uses the ESCO classification of the European Commission. FinOps Framework by FinOps Foundation, CC BY 4.0. Based on the NIST Cybersecurity Framework (CSF) 2.0, the NIST AI Risk Management Framework 1.0 and the NICE Workforce Framework for Cybersecurity, National Institute of Standards and Technology, U.S. Department of Commerce. NIST, the FinOps Foundation and the European Commission have not reviewed, approved or endorsed ASTRA Ready.