Learning and Technology Services: Information Security Officer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Key info: - Position Title: Learning and Technology Services: Information Security Officer (but we should not repeat job title as heading). So we start with maybe About the role. - Job Category: Academic Staff - Employment Type: Regular - Job Profile: Information Security Analyst IV (B) - POSITION: full-time professional academic staff position available beginning Nov 9, 2026. Working title: Information Security Officer, official title: Information Security Analyst IV. Renewable assignment contingent on performance. Salary range $75,000 to $85,000 annually based on qualifications and experience. - Minimum Qualifications: list bullet points. - Preferred Qualifications: list bullet points. - DUTIES: description. - Responsibilities: list bullet points (under "Responsibilities" heading in posting). Actually there is a "Responsibilities" section with bullet points. - THE UNIT: description. - UNIVERSITY and EAU CLAIRE COMMUNITY: description. - APPLICATION PROCEDURE: we should remove application instructions. - Key Job Responsibilities: another list (maybe duplicate). We need to preserve all substantive info but remove duplicated lines. There's duplication: "Key Job Responsibilities" list similar to responsibilities but maybe different items. We need to include them but avoid duplication. - Department Compensation: Required Qualifications Preferred Qualifications: Education How to Apply: Contact Information Special Notes: Institutional Overview (duplicate of earlier). Additional Information: background check etc. We need to produce sections: About the role (maybe summarizing position description). Responsibilities (list). Requirements (maybe Minimum Qualifications). Qualifications (maybe Preferred Qualifications). Skills (maybe combine abilities). Benefits (if any). Pay (salary range). Schedule (if any). The posting does not mention benefits explicitly besides maybe standard university benefits but not stated. So we should not create Benefits section unless stated. No schedule info besides full-time, regular, business hours, reachable off hours. Could include Schedule? It says "The ISO is expected to be available on campus during business hours and reachable during off business hours in case of a cyber related incident." That's schedule info. So we can include Schedule section with that detail. Pay: salary range $75,000 to $85,000 annually. Now we need to avoid boilerplate like EEO, etc. Also remove duplicated lines like repeated institutional overview. We need to preserve all substantive information. Let's extract substantive content. Let's list sections: About the role: Could include position title, working title, official title, start date, type, reporting line, renewable assignment, unit description maybe? But unit description could be separate? However we have no explicit "About the role" heading in source; we can create it summarizing. We need to avoid repeating job title as heading, but we can include it in paragraph. Let's craft:

About the role

This is a full‑time, professional academic staff position in Learning & Technology Services (LTS) beginning November 9, 2026. The working title is Information Security Officer; the official title is Information Security Analyst IV. The role reports directly to the Chief Information Officer (CIO) and is a renewable assignment contingent on performance.

Maybe also include unit description? Could be part of About the role or separate? There's no explicit unit heading; we could include under About the role or maybe under a separate "Unit" but not required. We'll keep it in About the role. Responsibilities: Use the Responsibilities section bullet points. From posting: Responsibilities (under heading "Responsibilities"): - Information Security Program Continuously develop, improve, and implement an information security program for the campus that will include but will not necessarily be limited to the following: Goals Scope Vision Mission Roles Workflows Tools Provide expertise and system administration for all information security program tools. Train, manage, supervise and mentor student information security analysts. Develop, implement, and manage the Incident Response Team (IRT), Disaster Recovery (DR) processes, tabletop exercises, and annual network penetration test process. Coordinate with LTS experts and other units to ensure disaster recovery strategies and COOP plan are documented, integrated, updated, and align with campus needs and priorities. Assess and track campus compliance to Universities of Wisconsin information security policies and audits. Develop plans to address compliance issues with Universities of Wisconsin information security policies, audits, and other cyber security requirements. Prepare, educate, and train campus for a cyber related incident. Develop annual budget for the overall information security program. - Cybersecurity Posture Work closely with LTS experts to identify cybersecurity risks. Develop and implement solutions to mitigate cybersecurity risks. Lead the process of establishing campus cybersecurity standards and best practices. Research hardware, software, and cybersecurity related issues. Provide risk assessment information associated with the procurement of software. Work congruently with Universities of Wisconsin information security policies. - Collaboration & Education Participate in LTS all staff meetings and other related meetings as requested. Collaborate with other information security experts from across Universities of Wisconsin. Communicate effectively with UW‑Eau Claire faculty, staff, and students. Represent UW‑Eau Claire at Universities of Wisconsin TISC meetings. Attend and participate in security related seminars, workshops, trainings, and conferences. Research and apply for grant funding associated with information security initiatives and priority needs. Perform miscellaneous duties as assigned by CIO. Also there is "Key Job Responsibilities" list: - Directs the development security awareness programming - Contributes to the development of policy and protocol related to security change requests and privilege access - Determines necessary technical changes to improve security - Leads forensic analysis and reporting for major and high-risk security breaches - Leads monitoring of daily system operations using intrusion detection and prevention systems and assesses findings - Leads project teams in the configuration, development, and testing of applications and security controls - Designs, develops, and implements developing security methodology and infrastructure for major systems These are somewhat overlapping but we should include them as part of responsibilities, maybe combine but avoid duplication. We can merge unique items. Let's list unique responsibilities: From Responsibilities section we have many items; from Key Job Responsibilities we have some that may not be covered: "Directs the development security awareness programming", "Contributes to the development of policy and protocol related to security change requests and privilege access", "Determines necessary technical changes to improve security", "Leads forensic analysis and reporting for major and high-risk security breaches", "Leads monitoring of daily system operations using intrusion detection and prevention systems and assesses findings", "Leads project teams in the configuration, development, and testing of applications and security controls", "Designs, develops, and implements developing security methodology and infrastructure for major systems". Some of these may be covered elsewhere but we can include them. We'll produce a

• list. Requirements: Minimum Qualifications bullet list. Minimum Qualifications: - A bachelor’s degree from an accredited institution. - Excellent written and verbal communication skills. - Knowledge and experience of information security best practices, policies, tools, and services used in securing an enterprise-wide technology infrastructure and environment. - Possess strong ability to troubleshoot, analyze, and develop solutions for cyber security related events and concerns. - Possess strong ability to quickly learn new tools as technology changes. - Ability to independently work through and understand advanced information technology concepts. - Ability to establish priorities and work under time constraints. - Ability to work as a part of a team collaborating with colleagues on solutions to technical issues. - Authorized to work in the United States. Qualifications: Preferred Qualifications bullet list. Preferred Qualifications: - A master’s degree in computer science, information systems, business, or related field. - Certifications and accreditations in the field of information security or cybercity. (Note: "cybercity" seems typo but keep as is.) - Experience supervising students or other employees. - Experience in preparing and managing a fiscal budget associated with an information security program. - System administration experience with Windows, Linux, Unix, or Mac operating systems. - Experience with virtualization, networking, software installation and/or software distribution in a large environment. - Possess an in-depth understanding of the computer field with a focus on Microsoft Server operating systems. - Understand the complexities involved in the design, implementation, and administration of domains. Skills: Could combine abilities like troubleshooting, communication, etc. But we already have those in qualifications. Could create Skills section for abilities like troubleshooting, analysis, learning new tools, independent work, prioritization, teamwork. However we might avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we can merge Skills into Qualifications or Responsibilities. But we need to include a Skills section only if posting has real specific content for it. The posting does not have a separate "Skills" heading, but we could extract skills from qualifications. However that would be duplicative. Better to not create a Skills section unless there is explicit skills list. There isn't. So we omit Skills. Benefits: Not stated explicitly. Omit. Pay: Salary range $75,000 to $85,000 annually based on qualifications and experience. Schedule: The ISO is expected to be available on campus during business hours and reachable during off business hours in case of a cyber related incident. Also full-time regular. So we can put schedule: Full‑time, regular; expected to be available during business hours and reachable off hours for incidents. Now we need to ensure we don't include boilerplate like "Current Employees: If you are currently employed..." etc. Remove that. Also remove "APPLICATION PROCEDURE", "Key Job Responsibilities" heading (we already used content). Remove "Department Compensation: Required Qualifications Preferred Qualifications: Education How to Apply: Contact Information Special Notes: Institutional Overview" etc. Remove "Additional Information" about background check etc? That is substantive? It mentions background check, references, confidentiality, etc. That could be considered part of application process or conditions; but instruction says remove application instructions and boilerplate. Background check etc might be considered part of hiring process, not job description. Likely we should remove it as it's not about role responsibilities/qualifications. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Background check is not exactly application instruction but could be considered legal/HR boilerplate. Safer to remove. Also remove "THE UNIT:" description? That is substantive about unit; we could keep as part of About the role or maybe separate section "Unit". But we don't have a heading for Unit; we could incorporate into About the role. Similarly "UNIVERSITY and EAU CLAIRE COMMUNITY:" description is substantive about institution and location; could be part of About the role or maybe a separate "About the institution". But we don't have a heading for that; we could include in About the role as extra paragraph. But we must not invent sections; we can include About the role covering all that. Let's craft About the role paragraph(s) to include: - Position details (title, start date, type, reporting line, renewable). - Unit description: LTS consists of approx 40 full-time staff and 40 part-time students, subunits, primary centralized IT organization, goal etc. - University and community description: UW-Eau Claire approx 9k students, 1.2k faculty/staff, recognized as top comprehensive university, leader in faculty-undergraduate research, etc. City of Eau Claire details. We need to preserve all substantive information; we must not omit any. So we need to include the unit description and university/community description somewhere. Thus About the role may become long but okay. Now Responsibilities: we need to include all bullet points from Responsibilities and Key Job Responsibilities, ensuring no duplication. Let's compile unique responsibilities: From Responsibilities section (I'll