Cyber Security Operations Analyst

We need to output HTML fragment with sections only if real content. Need to extract sections: About the role? The posting includes "At Aristocrat, we are dedicated..." that's intro. Then "What You'll Do" list of abilities. Then "What We're Looking For" includes requirements. Then "Preferred Qualifications:" and "Preferred Certifications:" maybe combine. Then "About Us:" description. Then "Compensation Philosophy" mentions pay and benefits but no specific numbers. According to rules: do NOT create Pay/Schedule/Benefits sections unless posting actually states them. It mentions compensation philosophy but no specific pay or benefits details. So we should not create Pay, Benefits, Schedule sections. Also we should not create sections with filler like "commensurate with experience". So we will include sections: About the role (maybe "About the role" corresponds to intro?), Responsibilities (What You'll Do), Requirements (What We're Looking For), Qualifications (maybe Preferred Qualifications and Certifications?), Skills? Could combine. Benefits? Not specific. Pay? Not specific. Schedule? Not specific. About Us? Could be a section. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if we have content. We have About the role (intro). Responsibilities (list). Requirements (list). Qualifications (preferred qualifications and certifications). Skills? Could be part of requirements. But we can include Skills if we have specific skills list. The posting includes many abilities; maybe we treat them as responsibilities. For Skills we could extract specific skills: CrowdStrike, Palo Alto, Rubrik, SIEM, etc. But we risk inventing. Better to not create Skills unless we have explicit list. The posting does not have a separate "Skills" heading. So we skip Skills. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all bullet points from "What You'll Do", "What We're Looking For", "Preferred Qualifications:", "Preferred Certifications:", "About Us:", and maybe the intro paragraph. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes EEO statement about diversity and inclusion, also mention about AI-assisted tools. Those are boilerplate? The instruction says remove EEO/equal-opportunity boilerplate. So we should remove the diversity and inclusion paragraph. Also remove the line about AI-assisted tools. Also remove "Compensation Philosophy" maybe? It's not pay/benefits specifics but it's a section about compensation philosophy. Since we are not creating Pay/Benefits sections, we might still include the content under a generic section? But we should not create Pay/Schedule/Benefits sections unless posting actually states them. The posting does state compensation philosophy but not specific pay/benefits. Should we include it under a section like "About the role"? Probably not; it's more about compensation. Since we cannot create Pay/Benefits sections, we might omit that content? But we must preserve ALL substantive information. However the instruction says: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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 compensation philosophy but not specific pay/benefits. It's not filler like "commensurate with experience". It's a description of philosophy. Should we include it? The allowed headings list includes Pay, Benefits, Schedule. But we could also create a custom heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. Likely we should stick to those headings. So we cannot create a heading like "Compensation Philosophy". We could fold that content into a short

under maybe About the role or another existing section? But it's not about role. Could we put it under "About the role"? Might be misrepresenting. Better to omit? But we must preserve ALL substantive information. However the instruction also says: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Compensation philosophy is not boilerplate; it's substantive. But we lack a proper heading to place it. Perhaps we can include it under a generic

without a heading? The instruction says output ONLY the HTML fragment, no /. It didn't say every piece must be under a heading. So we can have a

for prose not under a heading. So we can include the compensation philosophy as a

after other sections, without a heading. That seems acceptable. Similarly, the "About Us:" description is substantive; we can make a section "About the role"? Actually About Us is separate. Could we use heading "About the role"? No, that's for role description. There's no heading for About Us in examples, but we could still use

for a custom heading like "About Us". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can use other headings like "About Us". Probably acceptable. We'll include

About Us

. Similarly, we could have

Preferred Qualifications

and

Preferred Certifications

or combine under Qualifications. We need to avoid creating sections with filler. We have real content for each. Let's extract content. Intro paragraph: "At Aristocrat, we are dedicated to crafting a world-class gaming experience and seek a skilled Cyber Security Operations Analyst to join our team. Our mission is to bring happiness to life through the power of play. Our culture focuses on innovation, collaboration, and excellence. This role is essential to maintaining the security and integrity of our modern gaming environment. If you want to make a meaningful impact and join an ambitious team, this opportunity is for you!" We'll put that under

About the role

as prose

. Next, Responsibilities: "What You'll Do" followed by a list of abilities each starting with "Ability to ..." or "Demonstrated ability..." etc. We'll convert each to

. List items: - Demonstrated ability to stay current on emerging cybersecurity threats, vulnerabilities, attack methods, and industry trends, while educating, coaching, and guiding the team as a subject matter expert. - Ability to define, communicate, and champion the cybersecurity vision and roadmap for the Technology Services Network Support environment, while supporting and coordinating implementation efforts from planning through execution. - Ability to evaluate and engage with vendors and OEMs, assessing products and solutions to ensure alignment with organizational cybersecurity requirements, with a focus on CrowdStrike, Palo Alto, and Rubrik platforms. - Ability to develop, track, and present meaningful performance metrics that demonstrate the effectiveness of cybersecurity strategies, controls, and policies through regular monthly reporting to leadership. - Ability to effectively present high-level cybersecurity strategies, risks, and outcomes to senior leadership while maintaining a detailed understanding of the underlying gaming infrastructure and related technologies at a granular level. - Ability to rapidly develop a deep understanding of the distinctions between the gaming network environment and core enterprise IT infrastructure, and apply that knowledge to security and operational decision-making. - Effectively Monitor alerts, logs, and platform health across endpoint, network, and backup systems and ensure alignment with best practice responses and business reporting. - Investigate, triage, advance, and document security incidents and operational issues with a focus on auditable deliverables. - Support WAN-connected gaming operations through issue isolation and technical response. - Build and maintain automation for monitoring, alerting, and reporting tasks for agile and proactive responsiveness. - Maintain runbooks, procedures, incident records, and audit-ready documentation. - Support compliance efforts in a highly regulated gaming environment. - Additional cyber security or infrastructure related tasks may be assigned as necessary Note: some start with "Ability to", some with "Demonstrated ability", some with verb like "Effectively Monitor". We'll keep as is. Next, Requirements: "What We're Looking For" list: - Bachelor’s degree or equivalent experience in Information Security, Computer Science, or a related field. - Minimum 3+ years of hands-on cybersecurity, security operations, or related technical experience. - Experience with CrowdStrike, Palo Alto, and Rubrik or comparable expertise in a production environment. - Knowledge of security monitoring, endpoint protection, firewall administration, and backup/recovery operations. - Experience in a true 24/7 operational environment. - Strong troubleshooting, documentation, and reporting skills. - Ability to work hybrid in Las Vegas with required in-office time. - Ability to acquire and maintain required gaming licenses. Next, Preferred Qualifications: list: - Experience in gaming, hospitality, or other regulated industries. - Experience with SIEM, centralized logging, and vulnerability management. - Scripting or automation experience with PowerShell, Python, or similar tools. - Experience partnering with corporate or enterprise security teams. Preferred Certifications: list: - CompTIA Security+ - CEH - GSEC - CISSP - Relevant Palo Alto certification - Relevant CrowdStrike certification or equivalent training We could combine under

Qualifications

with two sublists? Or separate headings. Simpler:

Qualifications

then

Preferred Qualifications:

... and

Preferred Certifications:

... But we must not create heading with filler. We have real content. Next, About Us: paragraph(s). We'll extract: "Aristocrat and Aristocrat Gaming Aristocrat is a world leader in gaming content and technology, and a top-tier publisher of free-to-play mobile games. Aristocrat has three operating business units, spanning regulated land-based gaming (Aristocrat Gaming), social casino (Product Madness), and regulated online real-money gaming (Aristocrat Interactive). Our team of over 7,400 employees worldwide is united by our company's mission of bringing joy to life through the power of play. Aristocrat Gaming is a part of Aristocrat and the world’s number one premium provider of casino games, innovative technology, and customer-experience solutions. We have over 70,000 electronic game machines and 10+ creative studios, and have been ranked as the #1 top game supplier for five consecutive years. Aristocrat Gaming supports every facet of gaming floor operations from product to sales, systems, and service. Our products are renowned for innovative hardware, vivid graphics, groundbreaking mechanics, and superior performance, and our creative and technical talent is the best in the industry. Diversity and inclusion are integral to our values of Talent Unleashed, Collective Brilliance, Good Business, Good Citizen, and It’s All About the Player. We celebrate diversity and do not discriminate based on gender, race, religion, colour, national origin, sex, sexual orientation, age, veteran status, disability status, or any other applicable characteristics protected by law. This job description may have been reviewed and enhanced using AI-assisted tools to improve clarity, consistency, and inclusivity. All final content, role requirements and hiring decisions remain subject to human review and approval by Aristocrat." We need to remove EEO/equal-opportunity boilerplate. The paragraph includes diversity and inclusion statement and non-discrimination. That's EEO boilerplate. So we must remove that. Also remove the line about AI-assisted tools. Also maybe remove the sentence about "This job description may have been reviewed and enhanced using AI-assisted tools..." as it's boilerplate? It's about AI-assisted tools; likely considered boilerplate. We'll remove that as well. Thus we keep the rest: description of Aristocrat