Cyber Systems Security Engineering Stf - E4
Lockheed Martin · Las Vegas, NV · 3 wk ago
OTHR$121k–$224k/yrFull-time
We need to output HTML fragment with sections: h3 headings for sections present. Must not repeat job title. Must include only sections with real content. Remove boilerplate. Need to preserve all substantive info.
We have job description: first paragraph: "Standard Job Description Responsible for applying an interdisciplinary, collaborative approach to plan, design, develop, validate and verify Cyber solutions across the lifecycle. Conduct cyber risk assessment activities including threat modeling, vulnerability analysis and analysis of mitigation solutions. Coordinates and addresses Supply Chain risk management concerns. Develop, evaluate and analyze design constrains, trade-offs and detailed system and security design as they pertain to the Cyber domain. Coordinate with Cyber and system architects and developers to provide oversight in the development of solutions. Conduct cybersecurity test and evaluation of hardware and/or software designs to verify and validate compliance with defined specifications and requirements. Employs cyber security processes, methods, techniques and tools and assure their consistent application. Implements appropriate Assessment and Authorization activities as required by customers. *USE OF THIS CLASSIFICATION REQUIRES AUTHORIZATION FROM THE BUSINESS AREA CYBER DIRECTOR OR DELEGATE*"
That's the responsibilities/role description. Could be "About the role" or "Responsibilities". The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content.
We have Basic Qualifications: list items: Active Secret Clearance, IASAE Level II - IAW 8570 or higher certification (CASP+ CE, CISSP, CSSLP), Ability to travel as required (typically up to 20%). Those are qualifications.
Desired Skills: a long list of desired skills/requirements. Could be "Skills" or "Qualifications". Since we already have Basic Qualifications, we could have "Qualifications" for basic, and "Skills" for desired. Or combine.
We have Pay Information: Full-Time Salary Range: $120600.00 - $224000.00 plus description. So we need Pay section.
Benefits: list of benefits: Medical, Dental, Vision, Flexible work arrangements and schedules (e.g., 4x10), 401(k) match, Paid time off, Holidays, Parental Leave, EAP, Flexible Spending Accounts, Education Assistance, Life Insurance, Short-Term Disability, and Long-Term Disability. Also mention annual incentive programs. Also Washington state specifics. So Benefits section.
Schedule: Not explicitly given besides "Full-Time". Could infer schedule but not given. The instruction: only include section if posting has real specific content. No explicit schedule details besides full-time. Might not include Schedule.
We also have "About the role" maybe we can put the initial paragraph under "About the role" or "Responsibilities". Since we have responsibilities list, we could use "Responsibilities". The initial paragraph is more of a summary. Could treat as "About the role". Let's decide: Use "About the role" for the summary paragraph, and "Responsibilities" for the bullet list of duties? But the paragraph already includes many responsibilities. Could just have one section "Responsibilities" containing the paragraph as prose (maybe bullet list not needed). The instruction: Use
- for any list of duties/requirements/benefits. So if we have a list, we should use ul. The responsibilities are in a paragraph with sentences separated by periods, not a list. Could keep as
. That's fine. Basic Qualifications: list items -> use
- .
Desired Skills: many items, could be a list under "Skills". Use
- .
Pay: we have salary range and some prose. Could be
Pay
thenwith salary range and explanation. Benefits: list ->
- .
We must not include boilerplate like EEO etc. Already removed.
We must not repeat job title as heading. Not include Job ID etc.
We must preserve all substantive information. Ensure we don't lose any details.
Let's extract details precisely.
Responsibilities paragraph: "Standard Job Description Responsible for applying an interdisciplinary, collaborative approach to plan, design, develop, validate and verify Cyber solutions across the lifecycle. Conduct cyber risk assessment activities including threat modeling, vulnerability analysis and analysis of mitigation solutions. Coordinates and addresses Supply Chain risk management concerns. Develop, evaluate and analyze design constrains, trade-offs and detailed system and security design as they pertain to the Cyber domain. Coordinate with Cyber and system architects and developers to provide oversight in the development of solutions. Conduct cybersecurity test and evaluation of hardware and/or software designs to verify and validate compliance with defined specifications and requirements. Employs cyber security processes, methods, techniques and tools and assure their consistent application. Implements appropriate Assessment and Authorization activities as required by customers. *USE OF THIS CLASSIFICATION REQUIRES AUTHORIZATION FROM THE BUSINESS AREA CYBER DIRECTOR OR DELEGATE*"
Note there is a stray "Standard Job Description" at start. Might be part of heading but we can ignore as it's not substantive? It's basically label. We could keep it as part of paragraph but maybe remove as it's redundant. The instruction: preserve ALL substantive information; do not invent or summarize away detail. "Standard Job Description" is not substantive; it's just a label. Might be safe to drop. But we could keep it as part of paragraph; it's not harmful. However it's not really needed. I'd drop it to keep clean.
Thus responsibilities paragraph: "Responsible for applying an interdisciplinary, collaborative approach to plan, design, develop, validate and verify Cyber solutions across the lifecycle. Conduct cyber risk assessment activities including threat modeling, vulnerability analysis and analysis of mitigation solutions. Coordinates and addresses Supply Chain risk management concerns. Develop, evaluate and analyze design constrains, trade-offs and detailed system and security design as they pertain to the Cyber domain. Coordinate with Cyber and system architects and developers to provide oversight in the development of solutions. Conduct cybersecurity test and evaluation of hardware and/or software designs to verify and validate compliance with defined specifications and requirements. Employs cyber security processes, methods, techniques and tools and assure their consistent application. Implements appropriate Assessment and Authorization activities as required by customers. *USE OF THIS CLASSIFICATION REQUIRES AUTHORIZATION FROM THE BUSINESS AREA CYBER DIRECTOR OR DELEGATE*"
Now Basic Qualifications list:
- Active Secret Clearance
- IASAE Level II - IAW 8570 or higher certification (CASP+ CE, CISSP, CSSLP)
- Ability to travel as required (typically up to 20%)
Note there's a typo: "Acitve" but we should preserve as is? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Should we keep the typo? Probably yes, we should keep exactly as written. So "Acitve Secret Clearance". Keep typo.
Desired Skills list: Let's extract each bullet (they are separated by line breaks). The text:
"Desired Skills B.S. degree in a technical discWine such as Computer Science, Computer Engineering, Electrical Engineering, Computer Security, or Information Technology — or equivalent applied experienceExperience utilizing Joint Special Access Program (SAP) Implementation Guide (JSIG), Committee on National Security Systems Instruction (CNSSI) 1253, and NIST sp 800-37 Risk Management Framework (RMF) to design and harden information systems commensurate with customer needsOwnership of, or ability to acquire and maintain, a CAC Card is strongly desiredExperienced with ACAS software (Nessus and Tenable. SC)Ability to troubleshoot ACAS software (Nessus and Tenable.SC)Experienced with SCC SCAP tool to conduct compliance assessmentAbility to troubleshoot SCC SCAP toolHave knowledge of Group Policy ManagementSTIG experienceWork alongside software team to find common ground on STIGsExperience analyzing, decomposing, and allocating security controls into executable security requirements at the system, sub-system and component levelExperience with secure software development concepts (e.g. static code analysis, dynamic code analysis, STIG/SRG hardening, etc.) as applied to high-level programming languages (C, C++, Java)Experience with engineering change processes and/or configuration control processes Extensive experience developing and maintaining core security documentation artifacts for A&A Packages including Security Control Traceability Matrix (SCTM), System Security Plan (SSP) and/or Information Assurance Standard Operating Procedures (IA SOP), Plan of Action & Milestones (POA&M), and Risk Assessment Report (RAR)Extensive knowledge of DoD Security Technical Implementation Guides (STIGs) and Security Requirements Guides (SRGs)Background/knowledge working with information systems/environments that utilize the Open Mission Systems (OMS) standard and Universal Command and Control Standards Initiative (UCI) message setExpertise/knowledge in both compliance testing and penetration testing methodologies.Experience with Real-Time Embedded Operating Systems (e.g. GreenHills INEGRITY, LynxOS, VxWorks, Yocto)Experience with Agile project management tods (JIRA, VersionOne, etc.)Experience conducting technical trade studies and assessmentsMust be willing to mentor junior-level team membersExperience with creating and presenting technical information to senior-level executives and customersDemonstrated problem-solving and troubleshooting skillsProficient technical writing skillsStrong analytical and organizational skills with excellent communication skills (written and verbal communications) and have the ability to work in a dynamic work environmentExperience working in an aerospace design environment with exposure to DOD customers and their accrediting authorities."
We need to split into sensible items. The text is messy with missing spaces and punctuation. We should preserve the content as is but maybe we can add line breaks for readability. However we must not invent or summarize away detail. We can keep as a single paragraph but better to make list items. The original likely had bullet points but got mangled. We can attempt to split by capital letters after periods? Might be risky. Safer to keep as a single
preserving the exact string. However instruction: Use
- for any list of duties/requirements/benefits. This is a list of desired skills, so we should use list. But we risk mis-splitting. Perhaps we can keep as
and note it's a list but not using ul. The instruction says "Use
- for any list of duties/requirements/benefits". If we don't use ul, we might violate. But we could still use ul with each item as a sentence; we need to ensure we don't lose any content. We could manually split based on obvious delimiters: each item starts with a capital letter after a period? Let's try to parse. Original text after "Desired Skills": "B.S. degree in a technical discWine such as Computer Science, Computer Engineering, Electrical Engineering, Computer Security, or Information Technology — or equivalent applied experience" Note "discWine" likely typo for "discipline". We'll keep as is. Then "Experience utilizing Joint Special Access Program (SAP) Implementation Guide (JSIG), Committee on National Security Systems Instruction (CNSSI) 1253, and NIST sp 800-37 Risk Management Framework (RMF) to design and harden information systems commensurate with customer needs" Then "Ownership of, or ability to acquire and maintain, a CAC Card is strongly desired" Then "Experienced with ACAS software (Nessus and Tenable. SC)" (note space after Tenable.) Then "Ability to troubleshoot ACAS software (Nessus and Tenable.SC)" Then "Experienced with SCC SCAP tool to conduct compliance assessment" Then "Ability to troubleshoot SCC SCAP tool" Then "Have knowledge of Group Policy Management" Then "STIG experience" Then "Work alongside software team to find common ground on STIGs" Then "Experience analyzing, decomposing, and allocating security controls into executable security requirements at the system, sub-system and component level" Then "Experience with secure software development concepts
- for any list of duties/requirements/benefits. This is a list of desired skills, so we should use list. But we risk mis-splitting. Perhaps we can keep as
- .
We must not include boilerplate like EEO etc. Already removed.
We must not repeat job title as heading. Not include Job ID etc.
We must preserve all substantive information. Ensure we don't lose any details.
Let's extract details precisely.
Responsibilities paragraph: "Standard Job Description Responsible for applying an interdisciplinary, collaborative approach to plan, design, develop, validate and verify Cyber solutions across the lifecycle. Conduct cyber risk assessment activities including threat modeling, vulnerability analysis and analysis of mitigation solutions. Coordinates and addresses Supply Chain risk management concerns. Develop, evaluate and analyze design constrains, trade-offs and detailed system and security design as they pertain to the Cyber domain. Coordinate with Cyber and system architects and developers to provide oversight in the development of solutions. Conduct cybersecurity test and evaluation of hardware and/or software designs to verify and validate compliance with defined specifications and requirements. Employs cyber security processes, methods, techniques and tools and assure their consistent application. Implements appropriate Assessment and Authorization activities as required by customers. *USE OF THIS CLASSIFICATION REQUIRES AUTHORIZATION FROM THE BUSINESS AREA CYBER DIRECTOR OR DELEGATE*"
Note there is a stray "Standard Job Description" at start. Might be part of heading but we can ignore as it's not substantive? It's basically label. We could keep it as part of paragraph but maybe remove as it's redundant. The instruction: preserve ALL substantive information; do not invent or summarize away detail. "Standard Job Description" is not substantive; it's just a label. Might be safe to drop. But we could keep it as part of paragraph; it's not harmful. However it's not really needed. I'd drop it to keep clean.
Thus responsibilities paragraph: "Responsible for applying an interdisciplinary, collaborative approach to plan, design, develop, validate and verify Cyber solutions across the lifecycle. Conduct cyber risk assessment activities including threat modeling, vulnerability analysis and analysis of mitigation solutions. Coordinates and addresses Supply Chain risk management concerns. Develop, evaluate and analyze design constrains, trade-offs and detailed system and security design as they pertain to the Cyber domain. Coordinate with Cyber and system architects and developers to provide oversight in the development of solutions. Conduct cybersecurity test and evaluation of hardware and/or software designs to verify and validate compliance with defined specifications and requirements. Employs cyber security processes, methods, techniques and tools and assure their consistent application. Implements appropriate Assessment and Authorization activities as required by customers. *USE OF THIS CLASSIFICATION REQUIRES AUTHORIZATION FROM THE BUSINESS AREA CYBER DIRECTOR OR DELEGATE*"
Now Basic Qualifications list:
- Active Secret Clearance
- IASAE Level II - IAW 8570 or higher certification (CASP+ CE, CISSP, CSSLP)
- Ability to travel as required (typically up to 20%)
Note there's a typo: "Acitve" but we should preserve as is? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Should we keep the typo? Probably yes, we should keep exactly as written. So "Acitve Secret Clearance". Keep typo.
Desired Skills list: Let's extract each bullet (they are separated by line breaks). The text:
"Desired Skills B.S. degree in a technical discWine such as Computer Science, Computer Engineering, Electrical Engineering, Computer Security, or Information Technology — or equivalent applied experienceExperience utilizing Joint Special Access Program (SAP) Implementation Guide (JSIG), Committee on National Security Systems Instruction (CNSSI) 1253, and NIST sp 800-37 Risk Management Framework (RMF) to design and harden information systems commensurate with customer needsOwnership of, or ability to acquire and maintain, a CAC Card is strongly desiredExperienced with ACAS software (Nessus and Tenable. SC)Ability to troubleshoot ACAS software (Nessus and Tenable.SC)Experienced with SCC SCAP tool to conduct compliance assessmentAbility to troubleshoot SCC SCAP toolHave knowledge of Group Policy ManagementSTIG experienceWork alongside software team to find common ground on STIGsExperience analyzing, decomposing, and allocating security controls into executable security requirements at the system, sub-system and component levelExperience with secure software development concepts (e.g. static code analysis, dynamic code analysis, STIG/SRG hardening, etc.) as applied to high-level programming languages (C, C++, Java)Experience with engineering change processes and/or configuration control processes Extensive experience developing and maintaining core security documentation artifacts for A&A Packages including Security Control Traceability Matrix (SCTM), System Security Plan (SSP) and/or Information Assurance Standard Operating Procedures (IA SOP), Plan of Action & Milestones (POA&M), and Risk Assessment Report (RAR)Extensive knowledge of DoD Security Technical Implementation Guides (STIGs) and Security Requirements Guides (SRGs)Background/knowledge working with information systems/environments that utilize the Open Mission Systems (OMS) standard and Universal Command and Control Standards Initiative (UCI) message setExpertise/knowledge in both compliance testing and penetration testing methodologies.Experience with Real-Time Embedded Operating Systems (e.g. GreenHills INEGRITY, LynxOS, VxWorks, Yocto)Experience with Agile project management tods (JIRA, VersionOne, etc.)Experience conducting technical trade studies and assessmentsMust be willing to mentor junior-level team membersExperience with creating and presenting technical information to senior-level executives and customersDemonstrated problem-solving and troubleshooting skillsProficient technical writing skillsStrong analytical and organizational skills with excellent communication skills (written and verbal communications) and have the ability to work in a dynamic work environmentExperience working in an aerospace design environment with exposure to DOD customers and their accrediting authorities."
We need to split into sensible items. The text is messy with missing spaces and punctuation. We should preserve the content as is but maybe we can add line breaks for readability. However we must not invent or summarize away detail. We can keep as a single paragraph but better to make list items. The original likely had bullet points but got mangled. We can attempt to split by capital letters after periods? Might be risky. Safer to keep as a single
- .
Pay: we have salary range and some prose. Could be
- .
Desired Skills: many items, could be a list under "Skills". Use