Information Security Assurance Analyst I

We need to produce HTML fragment with sections for headings where there is real content. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, EEO, etc. Keep substantive info. We need to parse the posting. Key sections: - Intro: "Ready to take your career global? Make your mark at one of the biggest names in payments. We are seeking a candidate who can provides technical guidance on information security policies, procedures, technologies, and compliance-related activities through execution of First Line Assurance assessments. Works with stakeholders across Information Security and Technology organizations to validate security control implementation and effectiveness, identify vulnerabilities and control gaps, support remediation activities, and contribute to certification, continuous monitoring, and automation programs. Automation emphasis: This First Line Assurance role supports an automation-first model for control audits, evidence collection, reporting, certification, and continuous monitoring. Experience with Power Automate, Power BI, dashboards, and workflow automation is highly desirable." That's about the role. Could be "About the role" heading. - "What You’ll Own": list of duties. That's responsibilities. - "What You’ll Bring": qualifications, requirements, skills, certifications. We need to split into sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include if real content. We have no explicit Benefits, Pay, Schedule mentioned. So we should not create those sections. We have "About The Team" section: could be part of About the role or maybe separate but not in allowed headings. Could be included under About the role or maybe we can ignore as not required heading. The instruction: Prefer a few substantive sections over many thin ones. So we can combine team description into About the role. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list we need bullet list. For qualifications we can also list. We must preserve all substantive information, not invent or summarize away detail. Must not omit details like specific frameworks, certifications, etc. We need to avoid boilerplate like "Not an exhaustive list; other duties as assigned." That's okay to keep? It's substantive? It's a generic statement; maybe we can keep but it's not boilerplate. It's okay. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove the EEO statements, diversity statement, LinkedIn link, visa sponsorship text, apply now link, etc. Also remove "Applicant must be authorized to work in the U.S...." That's visa sponsorship boilerplate; remove. Remove "Does this sound like you? Then you sound like a Globalpayer. Apply now to take your career global. https://jobs.globalpayments.com/en/why-global-payments/benefits/" Remove. Remove "linkedin.com/in/shonali-r-66744622 -SB" etc. Now produce HTML. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...
  Maybe also

  Qualifications

  but we can combine requirements and qualifications. The instruction says use headings for those categories if content exists. We have both "What You’ll Bring" includes education, experience, knowledge, certifications, skills. Could split into Requirements (experience, education) and Qualifications (certifications, skills) but we can keep one section Requirements covering all. Better: Use Requirements for education/experience, Skills for technical skills, Qualifications for certifications? But we have limited headings. Let's decide: - About the role: intro paragraph. - Responsibilities: bullet list from "What You’ll Own". - Requirements: bullet list from "What You’ll Bring" covering education, experience, knowledge of frameworks, ability to work with stakeholders, etc. - Skills: bullet list for technical skills: Power Automate, Power BI, dashboards, workflow automation, cloud environments, etc. - Qualifications: bullet list for certifications: CRISC, CGRC, CISM, CISSP, CISA, CySA+, etc. We must ensure we don't create headings with filler text. All have content. We must not repeat job title. Good. Now extract details. Intro paragraph: combine first paragraph plus automation emphasis sentence. Let's craft: "Ready to take your career global? Make your mark at one of the biggest names in payments. We are seeking a candidate who can provide technical guidance on information security policies, procedures, technologies, and compliance-related activities through execution of First Line Assurance assessments. Works with stakeholders across Information Security and Technology organizations to validate security control implementation and effectiveness, identify vulnerabilities and control gaps, support remediation activities, and contribute to certification, continuous monitoring, and automation programs. Automation emphasis: This First Line Assurance role supports an automation-first model for control audits, evidence collection, reporting, certification, and continuous monitoring. Experience with Power Automate, Power BI, dashboards, and workflow automation is highly desirable." Now Responsibilities: from "What You’ll Own" bullet points. List: - Collaborates with Information Security, Technology, Risk, Audit, and business stakeholders to support First Line Assurance objectives. - Aligns assessment activities with business priorities and communicates findings in a clear, actionable manner. - Performs targeted control assessments, operational assurance reviews, post-deployment security validations, and certification activities. - Evaluates security control implementation and effectiveness, identifies control weaknesses and compliance gaps, assists with remediation tracking, and provides detailed findings and recommendations to stakeholders. - Supports the automation of control audits, evidence collection, control testing, reporting, remediation tracking, certification, and continuous monitoring. - Contributes to workflows, dashboards, data collection, and repeatable assessment processes that reduce manual effort and increase assurance coverage. - Uses automation and reporting tools to streamline evidence collection, control validation, assessment execution, remediation tracking, and recurring assurance activities. - Experience with Power Automate, Power BI, or similar workflow and reporting technologies is desirable. (maybe this is more skill) - Supports continuous monitoring, assurance, and validation activities by reviewing technical, administrative, and operational security controls. - Analyzes assessment results, assists in development of automation opportunities, tracks remediation efforts, and contributes to recurring certification and reporting activities. - Reviews business requests, assurance findings, and control exceptions to determine level of risk and appropriate remediation path. - Informs management of security policy variances and control gaps. - Not an exhaustive list; other duties as assigned. We should keep the "Experience with Power Automate..." maybe as skill but it's in responsibilities; we can keep there. Now Requirements: from "What You’ll Bring" education/experience/knowledge. List: - Bachelor's and/or Master’s Degree in Computer Science, Information Security, or related information technology field, and/or a combination of equivalent and relevant work experience. - Minimum 7+ years relevant experience in information security, security assurance, audit, risk, compliance, security architecture, security engineering, or related technology functions. - Knowledge of industry standard security and compliance programs and frameworks including PCI, FFIEC, FISMA, SOX, GLBA, HIPAA, ISO-87001, NIST 800-53, NST CSF, NIST RMF, and/or related security control frameworks. - Ability to work with stakeholders at multiple levels to identify risk, collect and evaluate evidence, document findings, and communicate practical remediation options. Now Skills: technical skills. List: - Experience performing information security assessments, security control assessments, technical control testing, control design testing, control effectiveness testing, KPI/KRI testing & validation, operational assurance reviews, or post-deployment validation activities. - Experience designing, implementing, or supporting automated security control validation processes, tooling, and infrastructure, to include strategic and continuous monitoring, audit resiliency, and/or evidence collection processes. - Experience with Microsoft Power Apps Platform, including Power Automate and Power BI, or other metric and reporting data structures. - Experience developing dashboards, metrics, assessment reports, or recurring assurance reporting from multiple data sources. - Familiarity with workflow automation platforms such as ServiceNow and assessment or evidence tracking platforms such as Optro (fka AuditBoard), Archer, or similar audit / GRC tools. - Knowledge of continuous monitoring, control validation, compliance automation, evidence collection, and remediation tracking concepts. - Strong familiarity with on-prem, cloud, and hybrid environments, across connected and disconnected environments, in a complex and diverse Fortune 500. - Familiarity with multiple cloud hosting environments is preferred, or at least strong familiarity in one of the three main cloud provider environments such as GCP, AWS, or Azure. - Strong analytical, communication, and stakeholder management skills, with the ability to translate technical evidence into business-focused recommendations. Now Qualifications: certifications. List: - Required Certification(s) / Licensing - Professional certifications such as CRISC, CGRC, CISM, CISSP, CISA, CySA+, or equivalent experience are preferred. - It’s a bonus if you have Strong familiarity with on-prem, cloud, and hybrid environments... (already in skills). Actually that's not certification. We could also include "Having broad yet in-depth expertise..." but that's fluff. We'll keep certifications. Now ensure we don't include any boilerplate like "Having ownership of a function..." that's generic fluff but maybe considered substantive? It's a bit generic but still part of posting. Might keep but could be considered filler. The instruction: Prefer a few substantive sections over many thin ones. Could include but it's vague. I'd omit that fluff. Also remove "Job Complexity - Works on issues that impact security assurance, technology risk management, control effectiveness, automation, reporting, and future concepts, products, or technologies. Creates formal networks with key decision makers and serves as a trusted partner to Information Security, Technology, Risk, Audit, and business stakeholders. Supervision - Exercises wide latitude in determining objectives and approaches to critical assignments." That's also generic but maybe substantive. Could keep under Responsibilities? Might be too generic. I'd omit. Also remove "About The Team" paragraph; could be included under About the role but it's generic fluff. Might omit. We need to preserve ALL substantive information; not invent or summarize away detail. The fluff might be considered substantive? It's still part of posting but not specific. The instruction says prefer few substantive sections over many thin ones. So we can omit fluff to keep sections thin? Actually we want few substantive sections, not many thin ones. So we should combine fluff into existing sections if it's not specific. But we can also omit if it's not adding value. However instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep all substantive info. Fluff might be considered substantive? It's still info from posting. But we can decide to keep it as part of About the role or Responsibilities as a paragraph. But we must not create sections with filler/placeholder text like "commensurate with experience". The fluff is not placeholder but still generic. I'd keep it as a paragraph under About the role. Let's include About the role paragraph plus maybe a short paragraph about team. But we already have About the role paragraph; we can add another paragraph about team: "Our inclusive and global teams win together every day. We’re proud to have the best minds in the industry, who you can learn from as you grow your career. The people, the energy, the connections – it’s unmatched. Come and be part of an ever-evolving company and get dynamic opportunities that go beyond borders." That's substantive but generic. Keep. Now "What makes a Globalpayer? Globalpayers think like a client, act like an owner and win as one team. We’re curious and innovative – always finding better ways to deliver impact. We empower each other to make decisions, and it’s our passion that drives excellence