Senior Cybersecurity Engineer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes a long fraud warning at end; we must remove that. Also remove "This job description is not designed to cover..." maybe considered boilerplate? It's a disclaimer; might be considered boilerplate but it's part of job description. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The disclaimer about duties may be considered legal boilerplate; but it's not EEO. Might be okay to keep? Safer to remove? The instruction says remove legal boilerplate. That line is a typical disclaimer; could be considered legal. I'd remove it. Also remove the fraud warning entirely.
We need to include sections only when posting has real specific content. So we will have sections: About the role (maybe from Position Summary), Responsibilities (Essential Functions), Key Performance Indicators, Internal ANSI/ANAB Information Security Responsibilities, Education And Experience, Other Qualifications, Pay (Starting compensation). Possibly also Qualifications? But we have Education And Experience and Other Qualifications; we could combine into Qualifications? But instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: About the role = Position Summary. Responsibilities = Essential Functions (maybe split into subparts but we can keep as list). Requirements = Education And Experience + Other Qualifications? Could separate but we have limited headings. Could make Qualifications = Education And Experience + Other Qualifications combined. Skills maybe not explicit. We'll include Pay.
We must not create sections with filler. So we will output:
About the role
...position summary...
Responsibilities
- ... each essential function bullet ...
We need to break essential functions into list items. The essential functions have subheadings: Security Architecture and Design, Engineering, Deployment and Control Assurance, Supervision and Technical Leadership. We could keep those as subheadings? But only allowed headings are those specific; we could embed them as within list items or separate . Probably better to keep as list items with the subheading text included.
We need to preserve all substantive information. So we need to include each bullet from essential functions.
Let's extract essential functions text:
Essential Functions
Security Architecture and Design Support the CISO in producing security architecture and design work: reference architectures, design patterns, security requirements and target-state designs for ANSI / ANAB [cloud] infrastructure, applications and cloud environments.Develop tactical-level technical requirements, architectural designs and procedures for the deployment of security tools and solutions, including tool selection, placement, integration with existing tooling, configuration and testing.Design, develop, engineer and implement security solutions from requirements through production.Ensure the soundness of the integrated security solution as a whole, identify gaps, and adapt reference architectures to the local environment rather than deploying them unchanged.Develop end-to-end programs and service offerings for new and existing security tools and technologies, including alignment to reference architectures, configuration guides, tool applications, health status checks, management guides and test plans.Lead the evaluation and introduction of new methodologies or tooling that measurably improve the security of platforms, infrastructure or access to data.Develop comprehensive plans, goals and objectives covering the full cybersecurity lifecycle of a project. Engineering, Deployment and Control Assurance Configure security tools and solutions for deployment, and assess tool capability, performance and effectiveness after deployment not only at selection.Administer security controls and review their application, confirming that controls, policies and procedures operate as effectively in practice as their design assumes.Enforce compliance with security policies and standards across systems, projects and third parties.Drive down risk: identify systemic risk and non-compliance issues, define action plans and track them through closure.Contribute to improvements in information security KPIs and KRIs.Create and maintain technical documentation, processes and procedures for security tools and systems, and actively review existing SOPs and documentation for areas of improvement.Stay informed on attack trends, zero-day vulnerabilities, adversary methodologies and emerging risks, and translate them into concrete design and configuration changes. Supervision and Technical Leadership Review output of the Junior Cybersecurity Engineer (Junior Security Analyst), before it is escalated or published, and give structured feedback.Provide technical mentorship to the junior role.Act as the technical escalation point for security investigations, incident response and overall security matters.Represent security’s interests in technical forums, change advisory boards, project design reviews, and deputize for the CISO on technical matters when required.
We need to split into sensible list items. Could break by sentences. But we must preserve all info; we can keep as one long paragraph per subsection? But instruction: Use
- for any list of duties/requirements/benefits. So we should make each duty a list item. Could break by each sentence after each period. That would be many items but okay.
Similarly for Key Performance Indicators: list items.
Internal ANSI/ANAB Information Security Responsibilities: list items.
Education And Experience: list? It's prose; could be
. But we could make list of requirements.
Other Qualifications: list.
Pay:
with range.
Let's craft.
We must not include boilerplate like "This job description is not designed to cover..." and fraud warning.
Now produce HTML.
Let's write:
About the role
The Senior Cybersecurity Engineer manages the development and deployment of ANSI and ANAB information security products and services, designs and implements the security tools, systems and procedures that sustain the confidentiality, integrity and availability of the organization's data. It is the senior hands-on security engineering role: the person who turns the security roadmap into working, verifiable controls. The position reports to the Chief Information Security Officer (CISO) and works under the CISO's direction on security architecture, translating policy, risk decisions and business requirements into reference architectures, design patterns and solutions that can actually be built and operated in the ANSI / ANAB environment.
Responsibilities
- Support the CISO in producing security architecture and design work: reference architectures, design patterns, security requirements and target-state designs for ANSI / ANAB [cloud] infrastructure, applications and cloud environments.
- Develop tactical-level technical requirements, architectural designs and procedures for the deployment of security tools and solutions, including tool selection, placement, integration with existing tooling, configuration and testing.
- Design, develop, engineer and implement security solutions from requirements through production.
- Ensure the soundness of the integrated security solution as a whole, identify gaps, and adapt reference architectures to the local environment rather than deploying them unchanged.
- Develop end-to-end programs and service offerings for new and existing security tools and technologies, including alignment to reference architectures, configuration guides, tool applications, health status checks, management guides and test plans.
- Lead the evaluation and introduction of new methodologies or tooling that measurably improve the security of platforms, infrastructure or access to data.
- Develop comprehensive plans, goals and objectives covering the full cybersecurity lifecycle of a project.
- Configure security tools and solutions for deployment, and assess tool capability, performance and effectiveness after deployment not only at selection.
- Administer security controls and review their application, confirming that controls, policies and procedures operate as effectively in practice as their design assumes.
- Enforce compliance with security policies and standards across systems, projects and third parties.
- Drive down risk: identify systemic risk and non-compliance issues, define action plans and track them through closure.
- Contribute to improvements in information security KPIs and KRIs.
- Create and maintain technical documentation, processes and procedures for security tools and systems, and actively review existing SOPs and documentation for areas of improvement.
- Stay informed on attack trends, zero-day vulnerabilities, adversary methodologies and emerging risks, and translate them into concrete design and configuration changes.
- Review output of the Junior Cybersecurity Engineer (Junior Security Analyst), before it is escalated or published, and give structured feedback.
- Provide technical mentorship to the junior role.
- Act as the technical escalation point for security investigations, incident response and overall security matters.
- Represent security’s interests in technical forums, change advisory boards, project design reviews, and deputize for the CISO on technical matters when required.
Key Performance Indicators
- Design Quality and Reuse: security designs and reference architectures are accepted by the CISO with minimal rework and are reused across subsequent projects rather than rebuilt each time.
- Documentation Quality: produces clear, well-structured and accurate technical documentation, standards and procedures that are published with minimal editing by the CISO.
- Solution Delivery: security tooling and solutions are deployed on schedule, fully configured, documented, and validated as effective after deployment.
- Risk Reduction: systemic risks and non-compliance items are identified, actioned and closed within agreed timeframes, with measurable movement in the agreed security KPIs and KRIs.
Internal ANSI / ANAB Information Security Responsibilities
- Attend/complete assigned information security training by the designated completion date.
- Read and adhere to published ISMS policies and procedures.
- Report timely any observed violations of ISMS policy - or known encroachments on information security - to your department leader and/or the Information Technology Department.
Education And Experience
Advanced degree in information security, computer science, engineering, mathematics or a related field of study, plus a minimum of 10 years of progressive and related information security work experience in regulated or standards-driven industries. A minimum of 8 to 10 years of hands-on experience in security engineering, cybersecurity architecture, host and network security, host and endpoint technologies, network detection, incident response or IT security tool deployment. Prior experience supervising or formally mentoring at least one junior engineer or analyst is strongly preferable. Professional security certification CISSP, CISM, CCSP, CCSK is preferred.
Other Qualifications
- Understands that ANSI and ANAB operate as a standards and accreditation body, where continuity of service and the trust of members and accredited bodies are the assets being protected.
- Able to present a design, its risk and its cost in terms an executive audience can act on, and to weigh security requirements against operational and budget constraints, recommending a defensible position rather than an absolute one.
- Knowledgeable in Secure / Cloud-based architecture design and management. Infrastructure security automation, infrastructure capacity monitoring and automated scaling.
- Knowledgeable with DevSecOps, automation of security integration with application code deployment (Jenkins, Maven, Git, Nexus or equivalents). Automation and configuration management frameworks.
- Understanding of main IAM concepts (PKI, certificate and key management best practice). Endpoint and network security, SIEM/SOC incident response processes.
- Working knowledge of security and risk frameworks preferred, NIST CSF, NIST SP 800-53, ISO / IEC 27001 and 27002, CIS Controls and the
for prose. We need to preserve all substantive information, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes a long fraud warning at end; we must remove that. Also remove "This job description is not designed to cover..." maybe considered boilerplate? It's a disclaimer; might be considered boilerplate but it's part of job description. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The disclaimer about duties may be considered legal boilerplate; but it's not EEO. Might be okay to keep? Safer to remove? The instruction says remove legal boilerplate. That line is a typical disclaimer; could be considered legal. I'd remove it. Also remove the fraud warning entirely. We need to include sections only when posting has real specific content. So we will have sections: About the role (maybe from Position Summary), Responsibilities (Essential Functions), Key Performance Indicators, Internal ANSI/ANAB Information Security Responsibilities, Education And Experience, Other Qualifications, Pay (Starting compensation). Possibly also Qualifications? But we have Education And Experience and Other Qualifications; we could combine into Qualifications? But instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: About the role = Position Summary. Responsibilities = Essential Functions (maybe split into subparts but we can keep as list). Requirements = Education And Experience + Other Qualifications? Could separate but we have limited headings. Could make Qualifications = Education And Experience + Other Qualifications combined. Skills maybe not explicit. We'll include Pay. We must not create sections with filler. So we will output:
About the role
...position summary...
Responsibilities
- ... each essential function bullet ...
. Probably better to keep as list items with the subheading text included. We need to preserve all substantive information. So we need to include each bullet from essential functions. Let's extract essential functions text: Essential Functions Security Architecture and Design Support the CISO in producing security architecture and design work: reference architectures, design patterns, security requirements and target-state designs for ANSI / ANAB [cloud] infrastructure, applications and cloud environments.Develop tactical-level technical requirements, architectural designs and procedures for the deployment of security tools and solutions, including tool selection, placement, integration with existing tooling, configuration and testing.Design, develop, engineer and implement security solutions from requirements through production.Ensure the soundness of the integrated security solution as a whole, identify gaps, and adapt reference architectures to the local environment rather than deploying them unchanged.Develop end-to-end programs and service offerings for new and existing security tools and technologies, including alignment to reference architectures, configuration guides, tool applications, health status checks, management guides and test plans.Lead the evaluation and introduction of new methodologies or tooling that measurably improve the security of platforms, infrastructure or access to data.Develop comprehensive plans, goals and objectives covering the full cybersecurity lifecycle of a project. Engineering, Deployment and Control Assurance Configure security tools and solutions for deployment, and assess tool capability, performance and effectiveness after deployment not only at selection.Administer security controls and review their application, confirming that controls, policies and procedures operate as effectively in practice as their design assumes.Enforce compliance with security policies and standards across systems, projects and third parties.Drive down risk: identify systemic risk and non-compliance issues, define action plans and track them through closure.Contribute to improvements in information security KPIs and KRIs.Create and maintain technical documentation, processes and procedures for security tools and systems, and actively review existing SOPs and documentation for areas of improvement.Stay informed on attack trends, zero-day vulnerabilities, adversary methodologies and emerging risks, and translate them into concrete design and configuration changes. Supervision and Technical Leadership Review output of the Junior Cybersecurity Engineer (Junior Security Analyst), before it is escalated or published, and give structured feedback.Provide technical mentorship to the junior role.Act as the technical escalation point for security investigations, incident response and overall security matters.Represent security’s interests in technical forums, change advisory boards, project design reviews, and deputize for the CISO on technical matters when required. We need to split into sensible list items. Could break by sentences. But we must preserve all info; we can keep as one long paragraph per subsection? But instruction: Use
- for any list of duties/requirements/benefits. So we should make each duty a list item. Could break by each sentence after each period. That would be many items but okay.
Similarly for Key Performance Indicators: list items.
Internal ANSI/ANAB Information Security Responsibilities: list items.
Education And Experience: list? It's prose; could be
. But we could make list of requirements. Other Qualifications: list. Pay:
with range. Let's craft. We must not include boilerplate like "This job description is not designed to cover..." and fraud warning. Now produce HTML. Let's write:
About the role
The Senior Cybersecurity Engineer manages the development and deployment of ANSI and ANAB information security products and services, designs and implements the security tools, systems and procedures that sustain the confidentiality, integrity and availability of the organization's data. It is the senior hands-on security engineering role: the person who turns the security roadmap into working, verifiable controls. The position reports to the Chief Information Security Officer (CISO) and works under the CISO's direction on security architecture, translating policy, risk decisions and business requirements into reference architectures, design patterns and solutions that can actually be built and operated in the ANSI / ANAB environment.
Responsibilities
- Support the CISO in producing security architecture and design work: reference architectures, design patterns, security requirements and target-state designs for ANSI / ANAB [cloud] infrastructure, applications and cloud environments.
- Develop tactical-level technical requirements, architectural designs and procedures for the deployment of security tools and solutions, including tool selection, placement, integration with existing tooling, configuration and testing.
- Design, develop, engineer and implement security solutions from requirements through production.
- Ensure the soundness of the integrated security solution as a whole, identify gaps, and adapt reference architectures to the local environment rather than deploying them unchanged.
- Develop end-to-end programs and service offerings for new and existing security tools and technologies, including alignment to reference architectures, configuration guides, tool applications, health status checks, management guides and test plans.
- Lead the evaluation and introduction of new methodologies or tooling that measurably improve the security of platforms, infrastructure or access to data.
- Develop comprehensive plans, goals and objectives covering the full cybersecurity lifecycle of a project.
- Configure security tools and solutions for deployment, and assess tool capability, performance and effectiveness after deployment not only at selection.
- Administer security controls and review their application, confirming that controls, policies and procedures operate as effectively in practice as their design assumes.
- Enforce compliance with security policies and standards across systems, projects and third parties.
- Drive down risk: identify systemic risk and non-compliance issues, define action plans and track them through closure.
- Contribute to improvements in information security KPIs and KRIs.
- Create and maintain technical documentation, processes and procedures for security tools and systems, and actively review existing SOPs and documentation for areas of improvement.
- Stay informed on attack trends, zero-day vulnerabilities, adversary methodologies and emerging risks, and translate them into concrete design and configuration changes.
- Review output of the Junior Cybersecurity Engineer (Junior Security Analyst), before it is escalated or published, and give structured feedback.
- Provide technical mentorship to the junior role.
- Act as the technical escalation point for security investigations, incident response and overall security matters.
- Represent security’s interests in technical forums, change advisory boards, project design reviews, and deputize for the CISO on technical matters when required.
Key Performance Indicators
- Design Quality and Reuse: security designs and reference architectures are accepted by the CISO with minimal rework and are reused across subsequent projects rather than rebuilt each time.
- Documentation Quality: produces clear, well-structured and accurate technical documentation, standards and procedures that are published with minimal editing by the CISO.
- Solution Delivery: security tooling and solutions are deployed on schedule, fully configured, documented, and validated as effective after deployment.
- Risk Reduction: systemic risks and non-compliance items are identified, actioned and closed within agreed timeframes, with measurable movement in the agreed security KPIs and KRIs.
Internal ANSI / ANAB Information Security Responsibilities
- Attend/complete assigned information security training by the designated completion date.
- Read and adhere to published ISMS policies and procedures.
- Report timely any observed violations of ISMS policy - or known encroachments on information security - to your department leader and/or the Information Technology Department.
Education And Experience
Advanced degree in information security, computer science, engineering, mathematics or a related field of study, plus a minimum of 10 years of progressive and related information security work experience in regulated or standards-driven industries. A minimum of 8 to 10 years of hands-on experience in security engineering, cybersecurity architecture, host and network security, host and endpoint technologies, network detection, incident response or IT security tool deployment. Prior experience supervising or formally mentoring at least one junior engineer or analyst is strongly preferable. Professional security certification CISSP, CISM, CCSP, CCSK is preferred.
Other Qualifications
- Understands that ANSI and ANAB operate as a standards and accreditation body, where continuity of service and the trust of members and accredited bodies are the assets being protected.
- Able to present a design, its risk and its cost in terms an executive audience can act on, and to weigh security requirements against operational and budget constraints, recommending a defensible position rather than an absolute one.
- Knowledgeable in Secure / Cloud-based architecture design and management. Infrastructure security automation, infrastructure capacity monitoring and automated scaling.
- Knowledgeable with DevSecOps, automation of security integration with application code deployment (Jenkins, Maven, Git, Nexus or equivalents). Automation and configuration management frameworks.
- Understanding of main IAM concepts (PKI, certificate and key management best practice). Endpoint and network security, SIEM/SOC incident response processes.
- Working knowledge of security and risk frameworks preferred, NIST CSF, NIST SP 800-53, ISO / IEC 27001 and 27002, CIS Controls and the