Research Security Systems Manager

We need to output HTML fragment with sections: About the role? Actually we have "About the University of Georgia", "About the College/Unit/Department", "Position Information", "Minimum Qualifications", "Preferred Qualifications", "Position Summary", "Knowledge, Skills, Abilities And/or Competencies", "Physical Demands", "Duties/Responsibilities" (multiple subparts). Also we have "Advertised Salary $92,000+, Commensurate with Experience" - we should not include Pay section if it's just "commensurate with experience" (the rule: never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", etc.). So we should not create a Pay section. Schedule: we have "Work Schedule Additional Schedule Information Monday through Friday, 8:00 am – 5:00 pm". That's specific schedule, so we can include a Schedule section. Benefits: we have "Employee Benefits Eligibility Benefits Eligible Full/Part time Full Time". Also "Retirement Plan TRS or ORP". That's benefits info. So we can include Benefits section. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, USG Core Values, etc. Also remove "Special Instructions to Applicants", "Location of Vacancy", "EEO Policy Statement", "USG Core Values Statement", etc. Also remove "Contact Information" maybe? It's not a section heading we need? It's metadata; we could fold into a short p or drop. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a short p for recruitment contact maybe? But they said "fold minor metadata into a short

or drop it." The recruitment contact is minor metadata; we could include a

with contact info. However they also said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Contact info is not exactly those, but it's minor metadata. We could include a

with contact details. We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use appropriate headings: About the University, About the Department, Position Summary, Minimum Qualifications, Preferred Qualifications, Knowledge, Skills, Abilities, Physical Demands, Duties/Responsibilities, Benefits, Schedule. We must not create sections with filler text. So we need to ensure each heading has substantive content. Let's extract substantive content: - About the University of Georgia: paragraph about charter, ranking, location, enrollment, etc. - About the College/Unit/Department: there is just "College/Unit/Department website" and maybe nothing else. Actually the posting shows "College/Unit/Department website" as a line but no description. That's likely filler. So we should not create a section for About the College/Unit/Department if no real content. The instruction: include a section ONLY when the posting has real, specific content for it. So we skip that. - Position Information: includes Classification Title, FLSA Exempt, FTE, etc. That's metadata; could be minor. Might fold into a short p or drop. Probably drop. - Minimum Qualifications: "Bachelor’s degree in a related field or equivalent and 2 years of professional experience". That's substantive. - Preferred Qualifications: multiple lines: Bachelor’s Degree (Masters preferred) in Computer Science, Cyber Security, or related field (work experience will be considered in lieu of a degree) At minimum of 4-5 years relevant experience in information security, risk management, or related fields in a DoD or Military Services related environment. Working knowledge and familiarity with DoD cybersecurity policy, requirements, and CUI handling. Currently hold or have the ability to obtain a U.S. Government Security Clearance. - Position Summary: paragraph about ISSM responsibilities. - Knowledge, Skills, Abilities And/or Competencies: list: IT knowledge – general networking and storage concepts, Microsoft Azure/365, authentication, security; Strong Project Management skills; Strong leadership and communication skills.; Analytical mindset with attention to detail.; Ability to balance security needs with business objectives. - Physical Demands: "Sitting at a desk and working on a computer for extended periods." plus series of Yes/No questions. Those are metadata; maybe we can include a short p summarizing? But we could drop as minor. However the physical demands description is substantive: sitting at a desk. The Yes/No are metadata; we could drop them. We'll include a

for physical demands: "Sitting at a desk and working on a computer for extended periods." - Duties/Responsibilities: multiple subparts with percentages. We need to combine into a single Duties/Responsibilities section with

• items. Each duty can be a list item, maybe include the percentage? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep the percentages. Could embed them in the li text. Thus we will create a

  Duties/Responsibilities

  then
  with each duty as
  • including the percentage. - Benefits: we have "Employee Benefits Eligibility Benefits Eligible Full/Part time Full Time", "Retirement Plan TRS or ORP". Also maybe "Benefits Eligible". We'll create a Benefits section with
    • Full-time benefits eligible
    • Retirement plan: TRS or ORP
    . Also maybe mention "Employee Benefits Eligibility". We'll keep. - Schedule: "Work Schedule Additional Schedule Information Monday through Friday, 8:00 am – 5:00 pm". We'll create Schedule section with

    Monday through Friday, 8:00 am – 5:00 pm

    . - Also we have "Advertised Salary $92,000+, Commensurate with Experience" - we should not create Pay section because it's just "commensurate with experience" plus a number? Actually it gives a number $92,000+. That's substantive. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state a salary: $92,000+, Commensurate with Experience. That's specific (a minimum). So we could include a Pay section with that info. However the phrase "Commensurate with Experience" is filler but combined with a concrete number maybe still okay. The rule says never create Pay section unless posting actually states them. It does state a salary range? It states $92,000+, which is a minimum. So we can include Pay section with that. But we must avoid filler like "commensurate with experience". We could include both: "$92,000+ (commensurate with experience)". That's still includes the phrase but it's not just filler; it's additional info. Might be okay. Safer to include Pay section with the salary info. But the examples of headings they gave include Pay as possible. So we can include Pay. Thus sections: About the University, Minimum Qualifications, Preferred Qualifications, Position Summary, Knowledge, Skills, Abilities, Physical Demands, Duties/Responsibilities, Benefits, Schedule, Pay. We also might include a short p for recruitment contact? Could fold minor metadata. We'll maybe include a

    with contact: "For questions, contact Gary Rachel at gcrachel@uga.edu." That's minor but okay. Now produce HTML fragment. We must not include or . Just the fragment. Let's craft.

    About the University of Georgia

    Chartered by the state of Georgia in 1785, the University of Georgia is the birthplace of public higher education in America and is the state’s flagship university. UGA is ranked among the top 20 public universities in U.S. News & World Report. The main campus is located in Athens, approximately 65 miles northeast of Atlanta, with extended campuses in Atlanta, Griffin, Gwinnett, and Tifton. UGA employs approximately 3,100 faculty and more than 7,700 full-time staff. Enrollment exceeds 41,000 students, including over 31,000 undergraduates and over 10,000 graduate and professional students. Academic programs reside in 19 schools and colleges, including the newly established School of Medicine.

    Minimum Qualifications

    Bachelor’s degree in a related field or equivalent and 2 years of professional experience.

    Preferred Qualifications

    • Bachelor’s degree (Master’s preferred) in Computer Science, Cyber Security, or a related field (work experience may be considered in lieu of a degree).
    • Minimum of 4‑5 years of relevant experience in information security, risk management, or related fields in a DoD or Military Services environment.
    • Working knowledge and familiarity with DoD cybersecurity policy, requirements, and CUI handling.
    • Currently hold or have the ability to obtain a U.S. Government Security Clearance.

    Position Summary

    The Information Systems Security Manager (ISSM) is responsible for managing system security plans, policies, training requirements, and other related aspects for information systems that manage regulated data types. This role safeguards sensitive information, manages risks, and maintains compliance with relevant Department of Defense (DoD) and United States Government (USG) regulations. The ideal candidate has experience working with or in the DoD and safeguarding Controlled Unclassified Information (CUI). The ISSM serves as a key contact for security plans and policies related to the cybersecurity of CUI/ITAR/EAR and HIPAA‑compliant computing environments within UGA.

    Knowledge, Skills, Abilities

    • IT knowledge – general networking and storage concepts, Microsoft Azure/365, authentication, security.
    • Strong project management skills.
    • Strong leadership and communication skills.
    • Analytical mindset with attention to detail.
    • Ability to balance security needs with business objectives.

    Physical Demands

    Sitting at a desk and working on a computer for extended periods.

    Duties/Responsibilities

    • Policy Development and Implementation, Coordination, Collaboration, and Communication – Develop, implement, and maintain security policies, procedures, and guidelines; work collaboratively with campus units (legal, compliance, research security & export control, central IT (EITS), unit IT, colleges, schools, departments); track project and administrative compliance with security standards, regulations, and best practices; report deficiencies; coordinate efforts to establish necessary physical and compute/network environments; collaborate with similar professionals at other institutions, federal funding agencies, and vendors; communicate security requirements, risks, and recommendations. (40% of time)
    • Risk Assessments, Security Audits and Assessments, and Incident Response and Investigation – Identify and assess risks related to information systems, networks, and data; work with relevant units to develop risk mitigation strategies and action plans; organize regular security audits and vulnerability assessments; share audit results and collaborate on improvement plans; evaluate effectiveness of security controls and recommend improvements; assist units in developing and maintaining incident response plans; investigate security incidents, breaches, and unauthorized access in cooperation with EITS InfoSec and other units; coordinate with relevant teams during incident handling. (30% of time)
    • Access Control and Authorization