Systems Administrator
ARA · Albuquerque, NM · 3 wk ago
On-siteInformation TechnologyFull-time
We need to output only HTML fragment, using for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. Let's parse the posting.
Content:
- Intro paragraph: "The System Administrator supports the ISSM/ISSO in the management, operation, and compliance of classified information systems (IS) operating under the National Industrial Security Program (NISP). This role is governed by the requirements of 32 CFR Part 117 (NISPOM Rule) and the DCSA Assessment and Authorization Guide (DAAG), which implements the Risk Management Framework (RMF) for cleared contractor facilities. The SA serves as a hands-on security practitioner responsible for the day-to-day security posture of assigned systems, ensuring continuous compliance with DCSA authorization requirements and maintaining a valid Authority to Operate (ATO)."
That's about the role. So we can have
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. Let's parse the posting.
Content:
- Intro paragraph: "The System Administrator supports the ISSM/ISSO in the management, operation, and compliance of classified information systems (IS) operating under the National Industrial Security Program (NISP). This role is governed by the requirements of 32 CFR Part 117 (NISPOM Rule) and the DCSA Assessment and Authorization Guide (DAAG), which implements the Risk Management Framework (RMF) for cleared contractor facilities. The SA serves as a hands-on security practitioner responsible for the day-to-day security posture of assigned systems, ensuring continuous compliance with DCSA authorization requirements and maintaining a valid Authority to Operate (ATO)."
That's about the role. So we can have About the role
with that paragraph.
- Responsibilities: The posting lists many responsibilities after "Responsibilities". Let's extract bullet-like lines. The text after "Responsibilities" includes:
"Possessing sufficient experience and technical competence commensurate with the complexity of the systems to include patch management, account management, STIGs/SCAPs, application updates and installs, hardware configuration and troubleshooting
Ensure all hardware and software additions, removals, and modifications follow approved change management processes
Responsible for managing Windows and Linux environments user accounts, permissions, system services, storage resources, backups, and recovery operations.
Monitor the health of the classified systems by applying patches and security updates
Maintain accurate technical and configuration documentation.
Maintain configuration management documentation for all hardware and software changes to classified systems
Implement and validate security controls on classified systems per NIST SP 800-53, CNSSI 1253, and applicable STIGs.
Report all security-related incidents to the ISSM in accordance with 32 CFR Part 117 requirements
Assess changes to assigned systems that could affect authorization status and notify the ISSM
Assist and support the ISSM/ISSO in all the following tasks:
Executing all phases of the RMF lifecycle: Prepare, Categorize, Select, Implement, Assess, Authorize, and Monitor to include decommission
Development, maintenance, and continuous updating of Information Systems
Conducting periodic assessments and continuous monitoring of authorized systems and providing the corrective actions for all identified findings and vulnerabilities"
We need to put these as - items. Some lines are long sentences; we can treat each line as a list item. Ensure we preserve all substantive info.
- Required Qualifications: after "Required Qualifications" we have:
"Minimum 2-4 years of experience in information technology,
Demonstrated working knowledge of 32 CFR Part 11718, the DCSA Assessment and Authorization Guide (DAAG), and NIST 800-series publications
Active (or ability to obtain) Top Secret clearance with SCI eligibility or clearance commensurate with the highest classification level processed on facility systems
Strong technical knowledge of Windows and/or Linux security hardening, STIG application, network security fundamentals, and audit log management
Experience with classified system configuration management, media control, and sanitization/destruction procedures
Ability to work independently and as part of a team
Excellent troubleshooting and problem-solving skills
Strong communication and interpersonal skills"
We can put these as list items under a section. The heading could be "Required Qualifications". The instructions say we can use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave list of possible headings. "Qualifications" is allowed. "Requirements" also allowed. We need to decide which to use. The posting has "Required Qualifications". Could map to "Qualifications". Also there is "Preferred Qualifications". Could also be under "Qualifications" or maybe "Skills". The instructions: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use Qualifications for both required and preferred? Might be better to separate Required Qualifications and Preferred Qualifications under Qualifications heading with sub-lists? But we must not invent headings not listed. We could have two sections: "Qualifications" for required, and maybe "Skills" for preferred? However preferred qualifications are more like qualifications, not skills. Could put both under Qualifications with subheadings? But we cannot add extra headings beyond those listed; we could still have Qualifications
and then within that we could have paragraphs distinguishing required vs preferred. That's acceptable.
But we also have "Core Competencies" section. That could map to "Skills". The posting includes "Core Competencies" with bullet points. So we can put those under Skills heading.
Company Information: That's boilerplate about company; we should remove as per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company information might be considered boilerplate? It's not explicitly listed but likely considered "company information" which is not required to preserve? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Company info might be substantive but it's generic. However they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company info is not those. But they also said "Prefer a few substantive sections over many thin ones." Might still include but it's not a standard heading. Could we include under "About the role"? Probably not. Safer to omit company information as it's not directly about the job. The instruction says preserve ALL substantive information; but company info is not about the job. Might be considered not substantive for the job posting. I'd lean to omit.
Thus sections: About the role, Responsibilities, Qualifications (including required and preferred), Skills (core competencies). Possibly also Requirements? But we already have Qualifications. Could also include Requirements heading for required qualifications and Qualifications for preferred? But we have limited headings. Let's decide: Use "Requirements" for required qualifications, and "Qualifications" for preferred qualifications. Then Skills for core competencies. That uses three headings plus About the role and Responsibilities = 5 sections.
Check if any content for Benefits, Pay, Schedule: none. So omit those.
Now craft HTML.
We need to wrap each section: About the role
...
For lists: Responsibilities
- ...
...
Similarly for Requirements, Qualifications, Skills.
Make sure to preserve all details exactly as given, but we can adjust punctuation? Should not invent or summarize away detail. Keep the content verbatim.
Let's extract each bullet precisely.
Responsibilities lines:
1. "Possessing sufficient experience and technical competence commensurate with the complexity of the systems to include patch management, account management, STIGs/SCAPs, application updates and installs, hardware configuration and troubleshooting"
2. "Ensure all hardware and software additions, removals, and modifications follow approved change management processes"
3. "Responsible for managing Windows and Linux environments user accounts, permissions, system services, storage resources, backups, and recovery operations."
4. "Monitor the health of the classified systems by applying patches and security updates"
5. "Maintain accurate technical and configuration documentation."
6. "Maintain configuration management documentation for all hardware and software changes to classified systems"
7. "Implement and validate security controls on classified systems per NIST SP 800-53, CNSSI 1253, and applicable STIGs."
8. "Report all security-related incidents to the ISSM in accordance with 32 CFR Part 117 requirements"
9. "Assess changes to assigned systems that could affect authorization status and notify the ISSM"
10. "Assist and support the ISSM/ISSO in all the following tasks:" (this is a heading for sublist; but we can keep as a list item then sub-items? The instruction says use - for any list of duties/requirements/benefits. This line is a intro to sublist; we could keep as a list item and then nested list? But we cannot nest? Not prohibited. Could keep as a list item and then sublist. However to keep simple, we could treat it as a list item and then the following lines as sub-items. But we need to preserve all info. Let's do nested list.
Thus after that line, we have:
- "Executing all phases of the RMF lifecycle: Prepare, Categorize, Select, Implement, Assess, Authorize, and Monitor to include decommission"
- "Development, maintenance, and continuous updating of Information Systems"
- "Conducting periodic assessments and continuous monitoring of authorized systems and providing the corrective actions for all identified findings and vulnerabilities"
We'll embed those as a nested
inside the li.
Now Required Qualifications lines:
1. "Minimum 2-4 years of experience in information technology,"
2. "Demonstrated working knowledge of 32 CFR Part 11718, the DCSA Assessment and Authorization Guide (DAAG), and NIST 800-series publications"
3. "Active (or ability to obtain) Top Secret clearance with SCI eligibility or clearance commensurate with the highest classification level processed on facility systems"
4. "Strong technical knowledge of Windows and/or Linux security hardening, STIG application, network security fundamentals, and audit log management"
5. "Experience with classified system configuration management, media control, and sanitization/destruction procedures"
6. "Ability to work independently and as part of a team"
7. "Excellent troubleshooting and problem-solving skills"
8. "Strong communication and interpersonal skills"
Note there is a typo "32 CFR Part 11718" likely meant "32 CFR Part 117". We'll keep as given.
Preferred Qualifications lines:
1. "Security+"
2. "Prior cleared industry experience (DCSA, NSA, or IC)"
3. "Experience with eMASS or equivalent RMF workflow tools, vulnerability scanners, SIEM/Auditing and STIG Viewer / SCAP compliance tool"
Core Competencies lines:
1. "Technical understanding of classified system security controls, network architecture, and risk management"
2. "Knowledge of NISPOM and related CFRs, DAAG, NIST SPs, CNSSI directive"
3. "Effective collaboration with the ISSM, ISSO, FSO, ITPSO, IT staff, and program managers"
4. "Discretion and integrity in handling classified information and sensitive cybersecurity data"
5. "Commitment to continuous professional development and staying current with evolving cybersecurity threats and DCSA guidance"
Now craft HTML.
We'll output:
About the role
The System Administrator supports the ISSM/ISSO in the management, operation, and compliance of classified information systems (IS) operating under the National Industrial Security Program (NISP). This role is governed by the requirements of 32 CFR Part 117 (NISPOM Rule) and the DCSA Assessment and Authorization Guide (DAAG), which implements the Risk Management Framework (RMF) for cleared contractor facilities. The SA serves as a hands-on security practitioner responsible for the day-to-day security posture of assigned systems, ensuring continuous compliance with DCSA authorization requirements and maintaining a valid Authority to Operate (ATO).
Responsibilities
- Possessing sufficient experience and technical competence commensurate with the complexity of the systems to include patch management, account management, STIGs/SCAPs, application updates and installs, hardware configuration and troubleshooting
- Ensure all hardware and software additions, removals, and modifications follow approved change management processes
- Respons
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use Qualifications for both required and preferred? Might be better to separate Required Qualifications and Preferred Qualifications under Qualifications heading with sub-lists? But we must not invent headings not listed. We could have two sections: "Qualifications" for required, and maybe "Skills" for preferred? However preferred qualifications are more like qualifications, not skills. Could put both under Qualifications with subheadings? But we cannot add extra headings beyond those listed; we could still have Qualifications
and then within that we could have paragraphs distinguishing required vs preferred. That's acceptable.
But we also have "Core Competencies" section. That could map to "Skills". The posting includes "Core Competencies" with bullet points. So we can put those under Skills heading.
Company Information: That's boilerplate about company; we should remove as per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company information might be considered boilerplate? It's not explicitly listed but likely considered "company information" which is not required to preserve? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Company info might be substantive but it's generic. However they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company info is not those. But they also said "Prefer a few substantive sections over many thin ones." Might still include but it's not a standard heading. Could we include under "About the role"? Probably not. Safer to omit company information as it's not directly about the job. The instruction says preserve ALL substantive information; but company info is not about the job. Might be considered not substantive for the job posting. I'd lean to omit.
Thus sections: About the role, Responsibilities, Qualifications (including required and preferred), Skills (core competencies). Possibly also Requirements? But we already have Qualifications. Could also include Requirements heading for required qualifications and Qualifications for preferred? But we have limited headings. Let's decide: Use "Requirements" for required qualifications, and "Qualifications" for preferred qualifications. Then Skills for core competencies. That uses three headings plus About the role and Responsibilities = 5 sections.
Check if any content for Benefits, Pay, Schedule: none. So omit those.
Now craft HTML.
We need to wrap each section: About the role
...
For lists:Responsibilities
- ... ...
- for any list of duties/requirements/benefits. This line is a intro to sublist; we could keep as a list item and then nested list? But we cannot nest? Not prohibited. Could keep as a list item and then sublist. However to keep simple, we could treat it as a list item and then the following lines as sub-items. But we need to preserve all info. Let's do nested list.
Thus after that line, we have:
- "Executing all phases of the RMF lifecycle: Prepare, Categorize, Select, Implement, Assess, Authorize, and Monitor to include decommission"
- "Development, maintenance, and continuous updating of Information Systems"
- "Conducting periodic assessments and continuous monitoring of authorized systems and providing the corrective actions for all identified findings and vulnerabilities"
We'll embed those as a nested
- inside the li.
Now Required Qualifications lines:
1. "Minimum 2-4 years of experience in information technology,"
2. "Demonstrated working knowledge of 32 CFR Part 11718, the DCSA Assessment and Authorization Guide (DAAG), and NIST 800-series publications"
3. "Active (or ability to obtain) Top Secret clearance with SCI eligibility or clearance commensurate with the highest classification level processed on facility systems"
4. "Strong technical knowledge of Windows and/or Linux security hardening, STIG application, network security fundamentals, and audit log management"
5. "Experience with classified system configuration management, media control, and sanitization/destruction procedures"
6. "Ability to work independently and as part of a team"
7. "Excellent troubleshooting and problem-solving skills"
8. "Strong communication and interpersonal skills"
Note there is a typo "32 CFR Part 11718" likely meant "32 CFR Part 117". We'll keep as given.
Preferred Qualifications lines:
1. "Security+"
2. "Prior cleared industry experience (DCSA, NSA, or IC)"
3. "Experience with eMASS or equivalent RMF workflow tools, vulnerability scanners, SIEM/Auditing and STIG Viewer / SCAP compliance tool"
Core Competencies lines:
1. "Technical understanding of classified system security controls, network architecture, and risk management"
2. "Knowledge of NISPOM and related CFRs, DAAG, NIST SPs, CNSSI directive"
3. "Effective collaboration with the ISSM, ISSO, FSO, ITPSO, IT staff, and program managers"
4. "Discretion and integrity in handling classified information and sensitive cybersecurity data"
5. "Commitment to continuous professional development and staying current with evolving cybersecurity threats and DCSA guidance"
Now craft HTML.
We'll output:
- Possessing sufficient experience and technical competence commensurate with the complexity of the systems to include patch management, account management, STIGs/SCAPs, application updates and installs, hardware configuration and troubleshooting
- Ensure all hardware and software additions, removals, and modifications follow approved change management processes
- Respons
About the role
The System Administrator supports the ISSM/ISSO in the management, operation, and compliance of classified information systems (IS) operating under the National Industrial Security Program (NISP). This role is governed by the requirements of 32 CFR Part 117 (NISPOM Rule) and the DCSA Assessment and Authorization Guide (DAAG), which implements the Risk Management Framework (RMF) for cleared contractor facilities. The SA serves as a hands-on security practitioner responsible for the day-to-day security posture of assigned systems, ensuring continuous compliance with DCSA authorization requirements and maintaining a valid Authority to Operate (ATO).
Responsibilities