Information Systems Security Officer (FORECASTED)
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not create sections like Pay/Schedule/Benefits unless posting actually states them. The posting includes benefits description (Medical, Vision+Dental, Retirement, PTO, etc). Also includes Salary Range Transparency section describing how they determine salary ranges but not actual numbers. It says "Salary Range Transparency" but does not give actual range. It says "We believe in creating a work environment...". It does not give specific numbers. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits are stated (medical, vision+dental, retirement, PTO, etc). So we can include Benefits section. Pay: they discuss salary ranges but not actual numbers; they say "Salary Range Transparency" but no specific range. The rule: never create Pay section unless posting actually states them. It does not give a specific salary figure or range; it's just description of how they determine. Likely we should NOT include Pay section. Schedule: not mentioned. So omit Schedule.
Qualifications: there are qualifications for ISSO Level 2 and Level 3. Also Additional Qualifications for Level 3. Also Preferred Qualifications. Also Requirements (U.S. Citizenship, etc). Also Certification Requirements. We need to decide what goes where.
We have headings: About the role (description), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to map content.
About the role: The initial description paragraph(s) about the position, mission, etc. Could combine first paragraph after "Description" and maybe "About Us" etc? But "About Us" is company info, not role. Might be considered part of About the role? Probably not; but we could include as part of description? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we should have About the role section with a summary of the role. The posting includes: "This Position is Contingent on Contract Award** Description Columbia Technology Partners is seeking an Information Systems Security Officer (ISSO) to support the security and compliance posture of information systems, programs, and enclaves across mission-critical environments. The ideal candidate will assist with the implementation and enforcement of information security policies, support Risk Management Framework (RMF) activities, maintain operational security compliance, and ensure systems adhere to established security requirements. This role provides opportunities to support or lead security operations, authorization activities, configuration management, and information assurance initiatives while working closely with Information System Security Managers (ISSMs), engineers, administrators, and government stakeholders."
That's good for About the role.
Responsibilities: list of Key Responsibilities - ISSO Level 2 and Additional Responsibilities - ISSO Level 3. We'll combine into a list.
Requirements: includes U.S. Citizenship required, CTP equal opportunity (but we remove EEO boilerplate), random drug testing, employment contingent upon successful completion of a security background investigation and polygraph. Certification Requirements: DOD 8570 IAM Level I, position requires an active Security Clearance with appropriate Polygraph. Also maybe "Requirements U.S. Citizenship is required for all applicants." That's a requirement. Also maybe "Certification Requirements: DOD 8570 IAM Level I". Also "This position requires an active Security Clearance with appropriate Polygraph." So we can put those in Requirements.
Qualifications: includes qualifications for ISSO Level 2 and Level 3, plus Additional Qualifications for Level 3, plus Preferred Qualifications. Also maybe "Experience supporting NIST RMF..." etc. We'll put those under Qualifications.
Skills: maybe we can extract from qualifications: experience in security tools and technologies, hardware and software security implementation, communication protocols, encryption techniques and technologies. Those could be considered skills. But we already have them in qualifications. The instruction says we can have Skills section if there is real specific content. We could list those as skills. However we might avoid duplication. But we need to preserve all substantive information; we can include them either in Qualifications or Skills. Since we already have Qualifications section with detailed experience years etc., we could put the skill areas under Skills. But we need to decide.
Better: Keep Qualifications for education/experience/certifications. Keep Skills for the specific technical areas (security tools and technologies, hardware and software security implementation, communication protocols, encryption techniques and technologies). Also maybe "Experience supporting NIST RMF, security authorization, continuous monitoring, and compliance initiatives." etc could be skills.
But we must not invent sections; we can include Skills if we have content.
Benefits: we have detailed benefits.
Pay: we have salary range transparency description but no actual numbers. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits are stated, so include Benefits. Pay: they discuss how they determine salary ranges but not actual numbers. I'd argue that is not stating a specific pay range, so we should NOT include Pay section. Schedule: none.
Now we need to output only HTML fragment, no markdown fences.
Let's craft.
Structure:
About the role
... (combined description)
Responsibilities
- ... (list items)
...
Requirements
- U.S. Citizenship is required for all applicants.
- Employment is contingent upon successful completion of a security background investigation and polygraph.
- Must hold an active Security Clearance with appropriate Polygraph.
- Must meet DOD 8570 Information Assurance Management (IAM) Level I certification requirement.
Note: random drug testing mentioned: "All applicants and employees are subject to random drug testing in accordance with Executive Order 12564." That's also a requirement. Include.
Qualifications
- ISSO Level 2: Bachelor's degree in Computer Science, Cybersecurity, Information Technology, or related discipline from an accredited college or university.
- Ten (10) years of experience as an Information Systems Security Officer supporting programs and contracts of similar scope, type, and complexity.
- Four (4) additional years of ISSO experience may be substituted in lieu of a bachelor's degree.
- ISSO Level 3: Fifteen (15) years of experience as an Information Systems Security Officer supporting programs and contracts of similar scope, type, and complexity.
- Experience in at least two (2) of the following areas for Level 2, and at least three (3) for Level 3: Security tools and technologies; Hardware and software security implementation; Communication protocols; Encryption techniques and technologies.
- Preferred qualifications: Experience supporting NIST RMF, security authorization, continuous monitoring, and compliance initiatives; Experience developing and maintaining SSPs, C&A packages, risk assessments, and related security documentation; Experience supporting classified environments and implementing security controls for government information systems; Knowledge of vulnerability management, configuration management, and security impact analysis processes; Experience working closely with ISSMs, system administrators, engineers, and government stakeholders in secure mission environments.
But we need to avoid duplication with Skills. Maybe we move the specific technical areas to Skills.
Let's separate:
Qualifications: education, years of experience, degree substitution, preferred qualifications (maybe keep as part of Qualifications). Skills: list of technical areas.
Thus:
Qualifications
- ISSO Level 2: Bachelor's degree in Computer Science, Cybersecurity, Information Technology, or related discipline from an accredited college or university.
- Ten (10) years of experience as an Information Systems Security Officer supporting programs and contracts of similar scope, type, and complexity.
- Four (4) additional years of ISSO experience may be substituted in lieu of a bachelor's degree.
- ISSO Level 3: Fifteen (15) years of experience as an Information Systems Security Officer supporting programs and contracts of similar scope, type, and complexity.
- Preferred qualifications: Experience supporting NIST RMF, security authorization, continuous monitoring, and compliance initiatives; Experience developing and maintaining SSPs, C&A packages, risk assessments, and related security documentation; Experience supporting classified environments and implementing security controls for government information systems; Knowledge of vulnerability management, configuration management, and security impact analysis processes; Experience working closely with ISSMs, system administrators, engineers, and government stakeholders in secure mission environments.
Skills
- Experience in at least two (2) of the following areas (Level 2) or three (3) (Level 3): Security tools and technologies; Hardware and software security implementation; Communication protocols; Encryption techniques and technologies.
But we need to preserve the exact phrasing: "Experience in at least two (2) of the following areas: Security tools and technologies Hardware and software security implementation Communication protocols Encryption techniques and technologies". For Level 3: at least three (3) of those areas.
We'll combine.
Now Benefits:
We have benefits description: Medical: CTP offers 3 superior plans, bringing our employees both in-network and out-of-network options. Vision + Dental: Both free to you + paid in full by CTP. Retirement: 401k - 6% company contribution PTO + Leave: A work life balance is extremely important to our team here at CTP, which is why our paid time off plans are so lucrative. Offering customizable leave plans to meet your needs is just one of our many perks! Jury Duty, Bereavement + Military Leave provided. Career Growth: Up to $10,000 provided for approved career-related learning, training, education, and/or tuition. Life and AD&D Insurance/Short-Term & Long-Term Disability: More peace of mind, at zero cost to you. Profit Sharing Bonus: End of year cash gets added to your bottom-line. Referral Bonus Program: Our tiered program provides an incentive with each stage of the hiring process your referral passes. Our bonuses range from $7,000-$20,000, if your referral joins the team.
We'll put each as list items.
Now About the role paragraph: we need to include the description plus maybe the "This Position is Contingent on Contract Award**" note. We'll include as a sentence.
Let's craft About the role:
This position is contingent on contract award. Columbia Technology Partners is seeking an Information Systems Security Officer (ISSO) to support the security and compliance posture of information systems, programs, and enclaves across mission-critical environments. The ideal candidate will assist with the implementation and enforcement of information security policies, support Risk Management Framework (RMF) activities, maintain operational security compliance, and ensure systems adhere to established security requirements. This role provides opportunities to support or lead security operations, authorization activities, configuration management, and information assurance initiatives while working closely with Information System Security Managers (ISSMs), engineers, administrators, and government stakeholders.
Now Responsibilities: combine Key Responsibilities - ISSO Level 2 and Additional Responsibilities - ISSO Level 3.
List items:
- Implement, coordinate, and enforce information systems security policies, standards, and methodologies.
- Maintain the operational security
for prose. We must not create sections like Pay/Schedule/Benefits unless posting actually states them. The posting includes benefits description (Medical, Vision+Dental, Retirement, PTO, etc). Also includes Salary Range Transparency section describing how they determine salary ranges but not actual numbers. It says "Salary Range Transparency" but does not give actual range. It says "We believe in creating a work environment...". It does not give specific numbers. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits are stated (medical, vision+dental, retirement, PTO, etc). So we can include Benefits section. Pay: they discuss salary ranges but not actual numbers; they say "Salary Range Transparency" but no specific range. The rule: never create Pay section unless posting actually states them. It does not give a specific salary figure or range; it's just description of how they determine. Likely we should NOT include Pay section. Schedule: not mentioned. So omit Schedule. Qualifications: there are qualifications for ISSO Level 2 and Level 3. Also Additional Qualifications for Level 3. Also Preferred Qualifications. Also Requirements (U.S. Citizenship, etc). Also Certification Requirements. We need to decide what goes where. We have headings: About the role (description), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. About the role: The initial description paragraph(s) about the position, mission, etc. Could combine first paragraph after "Description" and maybe "About Us" etc? But "About Us" is company info, not role. Might be considered part of About the role? Probably not; but we could include as part of description? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we should have About the role section with a summary of the role. The posting includes: "This Position is Contingent on Contract Award** Description Columbia Technology Partners is seeking an Information Systems Security Officer (ISSO) to support the security and compliance posture of information systems, programs, and enclaves across mission-critical environments. The ideal candidate will assist with the implementation and enforcement of information security policies, support Risk Management Framework (RMF) activities, maintain operational security compliance, and ensure systems adhere to established security requirements. This role provides opportunities to support or lead security operations, authorization activities, configuration management, and information assurance initiatives while working closely with Information System Security Managers (ISSMs), engineers, administrators, and government stakeholders."
That's good for About the role.
Responsibilities: list of Key Responsibilities - ISSO Level 2 and Additional Responsibilities - ISSO Level 3. We'll combine into a list.
Requirements: includes U.S. Citizenship required, CTP equal opportunity (but we remove EEO boilerplate), random drug testing, employment contingent upon successful completion of a security background investigation and polygraph. Certification Requirements: DOD 8570 IAM Level I, position requires an active Security Clearance with appropriate Polygraph. Also maybe "Requirements U.S. Citizenship is required for all applicants." That's a requirement. Also maybe "Certification Requirements: DOD 8570 IAM Level I". Also "This position requires an active Security Clearance with appropriate Polygraph." So we can put those in Requirements.
Qualifications: includes qualifications for ISSO Level 2 and Level 3, plus Additional Qualifications for Level 3, plus Preferred Qualifications. Also maybe "Experience supporting NIST RMF..." etc. We'll put those under Qualifications.
Skills: maybe we can extract from qualifications: experience in security tools and technologies, hardware and software security implementation, communication protocols, encryption techniques and technologies. Those could be considered skills. But we already have them in qualifications. The instruction says we can have Skills section if there is real specific content. We could list those as skills. However we might avoid duplication. But we need to preserve all substantive information; we can include them either in Qualifications or Skills. Since we already have Qualifications section with detailed experience years etc., we could put the skill areas under Skills. But we need to decide.
Better: Keep Qualifications for education/experience/certifications. Keep Skills for the specific technical areas (security tools and technologies, hardware and software security implementation, communication protocols, encryption techniques and technologies). Also maybe "Experience supporting NIST RMF, security authorization, continuous monitoring, and compliance initiatives." etc could be skills.
But we must not invent sections; we can include Skills if we have content.
Benefits: we have detailed benefits.
Pay: we have salary range transparency description but no actual numbers. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits are stated, so include Benefits. Pay: they discuss how they determine salary ranges but not actual numbers. I'd argue that is not stating a specific pay range, so we should NOT include Pay section. Schedule: none.
Now we need to output only HTML fragment, no markdown fences.
Let's craft.
Structure:
About the role
... (combined description)
Responsibilities
- ... (list items) ...
Requirements
- U.S. Citizenship is required for all applicants.
- Employment is contingent upon successful completion of a security background investigation and polygraph.
- Must hold an active Security Clearance with appropriate Polygraph.
- Must meet DOD 8570 Information Assurance Management (IAM) Level I certification requirement.
Qualifications
- ISSO Level 2: Bachelor's degree in Computer Science, Cybersecurity, Information Technology, or related discipline from an accredited college or university.
- Ten (10) years of experience as an Information Systems Security Officer supporting programs and contracts of similar scope, type, and complexity.
- Four (4) additional years of ISSO experience may be substituted in lieu of a bachelor's degree.
- ISSO Level 3: Fifteen (15) years of experience as an Information Systems Security Officer supporting programs and contracts of similar scope, type, and complexity.
- Experience in at least two (2) of the following areas for Level 2, and at least three (3) for Level 3: Security tools and technologies; Hardware and software security implementation; Communication protocols; Encryption techniques and technologies.
- Preferred qualifications: Experience supporting NIST RMF, security authorization, continuous monitoring, and compliance initiatives; Experience developing and maintaining SSPs, C&A packages, risk assessments, and related security documentation; Experience supporting classified environments and implementing security controls for government information systems; Knowledge of vulnerability management, configuration management, and security impact analysis processes; Experience working closely with ISSMs, system administrators, engineers, and government stakeholders in secure mission environments.
Qualifications
- ISSO Level 2: Bachelor's degree in Computer Science, Cybersecurity, Information Technology, or related discipline from an accredited college or university.
- Ten (10) years of experience as an Information Systems Security Officer supporting programs and contracts of similar scope, type, and complexity.
- Four (4) additional years of ISSO experience may be substituted in lieu of a bachelor's degree.
- ISSO Level 3: Fifteen (15) years of experience as an Information Systems Security Officer supporting programs and contracts of similar scope, type, and complexity.
- Preferred qualifications: Experience supporting NIST RMF, security authorization, continuous monitoring, and compliance initiatives; Experience developing and maintaining SSPs, C&A packages, risk assessments, and related security documentation; Experience supporting classified environments and implementing security controls for government information systems; Knowledge of vulnerability management, configuration management, and security impact analysis processes; Experience working closely with ISSMs, system administrators, engineers, and government stakeholders in secure mission environments.
Skills
- Experience in at least two (2) of the following areas (Level 2) or three (3) (Level 3): Security tools and technologies; Hardware and software security implementation; Communication protocols; Encryption techniques and technologies.
This position is contingent on contract award. Columbia Technology Partners is seeking an Information Systems Security Officer (ISSO) to support the security and compliance posture of information systems, programs, and enclaves across mission-critical environments. The ideal candidate will assist with the implementation and enforcement of information security policies, support Risk Management Framework (RMF) activities, maintain operational security compliance, and ensure systems adhere to established security requirements. This role provides opportunities to support or lead security operations, authorization activities, configuration management, and information assurance initiatives while working closely with Information System Security Managers (ISSMs), engineers, administrators, and government stakeholders.
Now Responsibilities: combine Key Responsibilities - ISSO Level 2 and Additional Responsibilities - ISSO Level 3. List items: - Implement, coordinate, and enforce information systems security policies, standards, and methodologies. - Maintain the operational security