Security Operations Analyst

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove disclaimer about image capture, work authorization, etc? Those are legal/EEO? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove legal disclaimer about image capture, work authorization, equal opportunity, etc. Also remove the "About Capgemini" paragraph? That's not a section heading but it's substantive? It's about company description; maybe we can keep as part of "About the role"? The instruction: "Prefer a few substantive sections over many thin ones." We can include About the role (maybe a paragraph summarizing role). Responsibilities: list bullet points. Requirements: maybe combine Required Qualifications and Nice to have? But we have separate headings: Requirements, Qualifications, Skills. We need to decide what goes where. The posting has "Required Qualifications:" list and "Nice to have skills/qualifications:" list. Also there is a paragraph about role at start. Could map: - About the role: introductory paragraph describing role and opportunity. - Responsibilities: bullet list under "Job Responsibilities". - Requirements: maybe the Required Qualifications (must-haves). - Qualifications: maybe the Nice to have? Or we could treat Qualifications as the Nice to have? But better: Requirements = Required Qualifications; Qualifications = Nice to have skills/qualifications; Skills = maybe technical skills list? However the Nice to have includes many technical skills and certifications. Could split: Skills = technical proficiencies (tools, programming languages). Qualifications = certifications? But we need to follow instruction: include a section ONLY when posting has real, specific content for it. So we can include sections that have content. We have content for: - About the role: yes (first paragraph). - Responsibilities: yes (list). - Requirements: yes (Required Qualifications). - Qualifications: maybe Nice to have skills/qualifications (could be considered qualifications). We'll include. - Skills: maybe we could extract technical skills from both Required and Nice to have, but that would duplicate. Better to put technical skills under Skills section, and certifications under Qualifications? But we already used Qualifications for Nice to have. Let's think. We could structure: - About the role: intro paragraph. - Responsibilities: bullet list. - Requirements: bullet list of Required Qualifications. - Skills: bullet list of technical proficiencies (tools, protocols, programming languages) from both Required and Nice to have. - Qualifications: bullet list of certifications and nice-to-have items like Cloud security experience, experience with vulnerability assessment platforms, change control, etc. - Benefits: we have info about benefits: "Full time regular employees are eligible for paid time off, medical/dental/vision insurance, 401(k), and any other benefits to eligible employees." Also maybe variable compensation etc. That's benefits. So we can include Benefits section. - Pay: we have salary range: "$80K-$95k". Also mention variable compensation, bonus, commission. So we can include Pay section. - Schedule: we have "Participate in weekly SOC analyst on-call rotation, with availability to work after hours in the event of an escalation outside normal business hours." That's schedule info. Also maybe full-time regular. So we can include Schedule section. We must not include placeholder text like "commensurate with experience". We have specific content. We must not repeat job title as heading. Not include Job ID etc. We must not include boilerplate like "Disclaimer", "Equal Opportunity Employer", etc. So we will omit those paragraphs. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting that are not boilerplate. Let's extract substantive content: Intro paragraph: "Capgemini Government Solutions (CGS) LLC is seeking highly motivated Security Operations Analyst to join our team in Indianapolis, IN to support our government clients. The successful applicant will work closely with our clients to provide technical support in information security response, security monitoring, and supports audit/compliance activities in our Security Operations Center (SOC).The successful applicant will have the opportunity to apply and grow their skill set, work with a motivated and entrepreneurial team, engage with a wide range of stakeholders, and build CGS’ capabilities to serve our clients." That's substantive. Responsibilities list (under "Job ResponsibilitiesAs a Security Operations Analyst (Mid-Level), you will:"): - Work as part of a team of Information Security professionals supporting a global enterprise. - Perform daily operational 'eyes on glass' real-time monitoring and analysis of security events from multiple sources including but not limited to events from Security Information Event Monitoring tools, network, and host-based intrusion detection systems, firewall logs, and system. - Communicate and escalates issues and incidents as required by process or management. - Contribute to the design and implementation of Security Event Analysis and Incident Management processes and procedures. - Create incident response reports and documentation as required to communicate findings, outcomes and lessons learned. - Participate in weekly SOC analyst on-call rotation, with availability to work after hours in the event of an escalation outside normal business hours. Note: some grammar issues but we keep as is. Required Qualifications: - U.S. Citizenship is required. - Eligible to obtain and maintain a Government Security Clearance. - 2+ year experience working in SOC environment as a Security Analyst - Experience supporting a large global enterprise environment - Solid and demonstrable comprehension of Information Security including malware, emerging threats, attacks, and vulnerability management. - Proficient knowledge and understanding of IP protocols and ports. - Technical proficiency of industry standard security tools such as Crowdstrike, ExtraHop, Netskope, Cisco Suite (Secure Endpoint-AMP, Secure Malware Analytics, Secure Cloud Email and Web Manager-IronPort); Microsoft Sentinel - An understanding of incident response methodologies and technologies. - Familiar with key security models and regulations such as ISO 2700X, SOX and PCI. - Customer service including the resolution of customer escalations, incident handling, and response. Nice to have skills/qualifications: - Cloud security experience. - Technical proficiency of industry standard security tools such as, Darktrace, Netskope, Cisco Suite (Secure Endpoint-AMP; Secure Malware Analytics-ThreatGrid; Umbrella; Secure Cloud Email and Web Manager-IronPort) ; Sentinel - Programming and/or scripting language experience (C, .NET, Python, Perl, etc). - Technical certifications considered an asset are: CISSP, GCIH, GCIA, GCFA, GPEN , GCCF, CISA, CWSP, CCSP, CCNP, MSCE or, other relevant certification in vulnerability analysis, ethnical hacking techniques or penetration testing. - Experience with vulnerability assessment platforms and manual validation. - Experience in the areas of change control, problem management, incident management and troubleshooting of security solutions. - Technical proficiency in at least one enterprise SIEM platform (i.e. ArcSight, Envision, Q1 Radar, Nitro Security), and at least one enterprise Network Intrusion Detection System (i.e. HP Tipping Point, Sourcefire, McAfee) About Capgemini paragraph: "Capgemini is a global business and technology transformation partner, helping organizations to accelerate their dual transition to a digital and sustainable world, while creating tangible impact for enterprises and society. It is a responsible and diverse group of 340,000 team members in more than 50 countries. With its strong over 55-year heritage, Capgemini is trusted by its clients to unlock the value of technology to address the entire breadth of their business needs. It delivers end-to-end services and solutions leveraging strengths from strategy and design to engineering, all fueled by its market leading capabilities in AI, generative AI, cloud and data, combined with its deep industry expertise and partner ecosystem. The Group reported 2024 global revenues of €22.1 billion.Get the future you want | www.capgemini.com" This is substantive about company; could be included under About the role or maybe a separate section? But we only have headings list; we could put it under About the role as additional paragraph. That's fine. Benefits: "Full time regular employees are eligible for paid time off, medical/dental/vision insurance, 401(k), and any other benefits to eligible employees." Also maybe variable compensation etc is under Pay. Pay: "The disclosed range represents the lowest to highest salary we, in good faith, believe we would pay for this role at the time of this posting, although we may ultimately pay more or less than the disclosed range, and the range may be modified in the future. The disclosed range takes into account the wide range of factors that are considered in making compensation decisions including, but not limited to, geographic location, relevant education, qualifications, certifications, experience, skills, seniority, performance, sales or revenue-based metrics, and business or organizational needs. At Capgemini, it is not typical for an individual to be hired at or near the top of the range for their role. The base salary range for the tagged location is $80K-$95k.This role may be eligible for other compensation including variable compensation, bonus, or commission." We need to keep substantive info: base salary range $80K-$95k, variable compensation, bonus, commission. The rest is explanation; we can keep but it's somewhat boilerplate? It's about pay transparency; maybe considered legal? It's part of pay disclosure; but instruction says remove legal/EEO/equal-opportunity/scam-warning boilerplate. This is pay transparency legal text; might be considered legal boilerplate. However it's part of the pay info; but we could keep the core: base salary range $80K-$95k, variable compensation, bonus, commission. The rest is explanation; we could keep but it's not required. To be safe, we can keep the salary range and mention variable compensation, bonus, commission. The rest could be considered boilerplate; but it's not explicitly EEO. I'd keep minimal: base salary range and note variable compensation, bonus, commission. Schedule: we have on-call rotation and after-hours availability. Also maybe full-time regular. We'll include that. Now we need to output HTML fragment with sections. Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We must not include / or markdown. We need to decide which sections to include: About the role, Responsibilities, Requirements, Skills, Qualifications, Benefits, Pay, Schedule. We must ensure we don't create empty sections. Let's draft content: About the role: combine intro paragraph and About Capgemini paragraph? Could be two

  elements. Responsibilities:

  with each responsibility. Requirements:
  of Required Qualifications. Skills: maybe list technical proficiencies from Required and Nice to have (tools, protocols, programming languages). But we already have Required Qualifications includes technical proficiency of tools etc. To avoid duplication, we could put technical skills under Skills, and keep Requirements as the non-technical must-haves (citizenship, clearance, experience, comprehension, customer service). But the instruction says preserve ALL substantive information; we can split but must not lose any info. So we need to ensure all info appears somewhere. Let's parse Required Qualifications items: 1. U.S. Citizenship is required. 2. Eligible to obtain and maintain a Government Security Clearance. 3. 2+ year experience working in SOC environment as a Security Analyst 4. Experience supporting a large global enterprise environment 5. Solid and demonstrable comprehension of Information Security including malware, emerging threats, attacks, and vulnerability management. 6. Proficient knowledge