Information Security Advisor - Data Protection
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting and extract sections.
The posting includes:
Location: Indianapolis IN, Mason OH, Atlanta GA, Grand Prairie TX, Tampa FL
Hours: Standard Working hours
Travel: This role requires associates to be in-office 1 - 2 days per week, fostering collaboration and connectivity, while providing flexibility to support productivity and work-life balance. This approach combines structured office engagement with the autonomy of virtual work, promoting a dynamic and adaptable workplace. Alternate locations may be considered if candidates reside within a commuting distance from an office. Please note that per our policy on hybrid/virtual work, candidates not within a reasonable commuting distance from the posting location(s) will not be considered for employment, unless an accommodation is granted as required by law.
Position Overview: Maintains enterprise information security policies, technical standards, guidelines, procedures, and infrastructure necessary to support information security in compliance with established company policies, regulatory requirements, and generally accepted information security controls pertaining to data protection. Responsible for the delivery of strategic protection of data at rest. Ensures security solutions involving the use of technologies are well-conceived, designed and implemented in compliance with enterprise standards.
How You Will Make An Impact: list of many bullet-like sentences (each line starts with something like "Working knowledge of the Protegrity platform..." etc). Those are duties/responsibilities.
Required Qualifications: BS/BA degree... etc.
Preferred Qualifications: list of items.
Then there is a paragraph about "Please be advised that Elevance Health only accepts resumes..." etc. That's application instructions? Might be considered boilerplate? It's about agency resumes; maybe we can drop as it's not substantive? The instruction says remove application instructions. This is about resumes from agencies; could be considered application instruction. Probably drop.
Then "Who We Are" etc. That's company description; maybe we can include as "About the role"? Actually "About the role" is not present; we could use "About the role" heading for company overview? The instructions say we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings.
We have location/hours/travel info: could be under "Schedule"? Actually schedule is about work hours, location, hybrid. Could be under "Schedule". But we have "Hours: Standard Working hours" and travel description about hybrid. So we could put under Schedule.
We have Position Overview: could be under "About the role" (description of role). Or maybe "Responsibilities". But we also have "How You Will Make An Impact" which is essentially responsibilities/duties. So we could put that under Responsibilities.
We have Required Qualifications: under Requirements or Qualifications. The instruction list includes Requirements and Qualifications as separate possible headings. We could combine? Probably use "Requirements" for required qualifications, and "Preferred Qualifications" maybe under "Qualifications"? But we have both required and preferred. Could do "Requirements" for required, and "Qualifications" for preferred? Or we could have "Required Qualifications" under Requirements and "Preferred Qualifications" under Qualifications. That seems fine.
We have a list of many technical skills/experience under "How You Will Make An Impact". Those are responsibilities. Could also be considered Skills. But we already have Responsibilities.
We have no explicit Pay, Benefits info. There's a paragraph about total rewards: "We offer a range of market-competitive total rewards that include merit increases, paid holidays, Paid Time Off, and incentive bonus programs (unless covered by a collective bargaining agreement), medical, dental, vision, short and long term disability benefits, 401(k) +match, stock purchase plan, life insurance, wellness programs and financial education resources, to name a few." That's benefits. So we can create a Benefits section.
We have no explicit Pay info. So we should not create Pay section.
We have schedule info: location/hours/travel. So we can create Schedule section.
We have About the role: maybe we can include Position Overview under About the role.
We have Responsibilities: How You Will Make An Impact.
We have Requirements: Required Qualifications.
We have Qualifications: Preferred Qualifications.
We have Skills: maybe not needed; we could put technical skills under Responsibilities or Qualifications. But we already have those.
We need to ensure we don't create sections with filler. All sections we create have real content.
We must remove boilerplate: EEO, legal, vaccination policy, etc. Also remove "Who We Are", "How We Work", etc? Those are company description; maybe we can incorporate into About the role? But About the role is supposed to be about the role, not company. However we have Position Overview which is about role. So we can keep that. The "Who We Are" etc is company description; could be considered boilerplate? Not exactly, but it's not required. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Who We Are" is not explicitly listed, but it's more about company. Might be considered not substantive for the job? Could be kept as part of About the role? But we already have Position Overview. Might be safe to include a brief About the role using Position Overview only, and drop the Who We Are etc.
We also need to drop duplicated lines: there may be none.
Now produce HTML.
Structure:
About the role
Position Overview text.
Responsibilities
- Working knowledge of the Protegrity platform across core components, including architecture concepts, deployment patterns, policy administration, integration troubleshooting, and performance and operational support.
- Experience deploying and supporting Infrastructure as Code using Terraform, including module usage, debugging plans and applies, environment promotion, and Terraform state management.
... etc for each bullet.
We need to preserve all bullet points exactly as in the posting. Let's extract them from the "How You Will Make An Impact" section.
The text:
Working knowledge of the Protegrity platform across core components, including architecture concepts, deployment patterns, policy administration, integration troubleshooting, and performance and operational support.
Experience deploying and supporting Infrastructure as Code using Terraform, including module usage, debugging plans and applies, environment promotion, and Terraform state management.
Experience maintaining infrastructure, configuration, and code in GitHub (or similar), including pull request reviews, branching strategies, and release/change workflows.
Experience supporting secure application integrations across AWS and at least one additional cloud platform (Azure or GCP), with the ability to troubleshoot cross-cloud connectivity and data protection solutions.
Hands-on experience implementing serverless integration patterns using services such as AWS Lambda, Azure Functions, Google Cloud Functions, or Cloud Run, including identity, authentication, and security best practices.
Working knowledge of Kubernetes platforms (EKS, AKS, GKE, or equivalent), including application connectivity, identity, secrets management, logging, and operational troubleshooting.
Experience using Splunk to develop searches, analyze logs, and support troubleshooting, operational monitoring, and incident investigations.
Experience working within ServiceNow for incident, request, and change management, with familiarity creating or maintaining request workflows and catalog items preferred.
Experience supporting data protection solutions for object storage, databases, and file-based data transfers, including structured file formats, operational support, throughput considerations, and access patterns.
Working knowledge of Snowflake connectivity, role-based access concepts, security model, and data integration patterns.
Experience integrating applications and pipelines with HashiCorp Vault, including authentication methods, secret consumption patterns, and secret rotation practices.
Experience performing operational activities with Hardware Security Modules (HSMs), including initialization, partition and user administration, key management activities, and integration troubleshooting.
We need to keep each as - .
Now Requirements (Required Qualifications):
"Requires BS/BA degree in Information Technology or related field of study and a minimum of 5 years experience in systems support, system administration, system engineering, system security, access management, network security, network communications, computer networking, telecommunications, systems development and management, hardware, software, and/or data; or any combination of education and experience, which would provide an equivalent background.Requires experience in planning and designing highly complex systems."
Note there is a missing period between "...equivalent background.Requires". We'll keep as is.
We can put as
maybe but it's a single paragraph. Could also be
but it's not a list. Use .
Now Qualifications (Preferred Qualifications):
"Experience with multiple technical and business disciplines strongly preferredSecurity Certifications: CISSP or other technical security certifications (e.g. Systems Security Certified Practitioner, Certification and Accreditation Professional) strongly preferredPrior experience with field level protection solutionsPrior experience managing on prem and cloud infrastructureStrong technical troubleshooting skillsSelf motivated/self starterPassion for mentoring others on teamOwnership to resolution of technical issuesLeadership"
We need to split into list items? The original is a run-on sentences without punctuation. We could treat each phrase as separate bullet? But we must preserve all substantive information; we could keep as a single paragraph but it's hard to read. Better to split into logical items based on the phrases separated by missing punctuation. However we must not invent or summarize away detail. Splitting could be considered rephrasing but not adding info. It's okay to format as list items each representing a distinct qualification. The original lacked punctuation; we can infer separate items: "Experience with multiple technical and business disciplines strongly preferred", "Security Certifications: CISSP or other technical security certifications (e.g. Systems Security Certified Practitioner, Certification and Accreditation Professional) strongly preferred", "Prior experience with field level protection solutions", "Prior experience managing on prem and cloud infrastructure", "Strong technical troubleshooting skills", "Self motivated/self starter", "Passion for mentoring others on team", "Ownership to resolution of technical issues", "Leadership". That seems reasonable.
We'll output as
- each.
Now Benefits:
From "We offer a range of market-competitive total rewards that include merit increases, paid holidays, Paid Time Off, and incentive bonus programs (unless covered by a collective bargaining agreement), medical, dental, vision, short and long term disability benefits, 401(k) +match, stock purchase plan, life insurance, wellness programs and financial education resources, to name a few."
We'll put as
maybe but it's a list of benefits; could be
. Use - each item separated by commas? Better to split: merit increases, paid holidays, Paid Time Off, incentive bonus programs (unless covered by a collective bargaining agreement), medical, dental, vision, short and long term disability benefits, 401(k) +match, stock purchase plan, life insurance, wellness programs, financial education resources. We'll keep as list.
Now Schedule:
We have location and hours/travel.
Location: Indianapolis IN, Mason OH, Atlanta GA,
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting and extract sections. The posting includes: Location: Indianapolis IN, Mason OH, Atlanta GA, Grand Prairie TX, Tampa FL Hours: Standard Working hours Travel: This role requires associates to be in-office 1 - 2 days per week, fostering collaboration and connectivity, while providing flexibility to support productivity and work-life balance. This approach combines structured office engagement with the autonomy of virtual work, promoting a dynamic and adaptable workplace. Alternate locations may be considered if candidates reside within a commuting distance from an office. Please note that per our policy on hybrid/virtual work, candidates not within a reasonable commuting distance from the posting location(s) will not be considered for employment, unless an accommodation is granted as required by law. Position Overview: Maintains enterprise information security policies, technical standards, guidelines, procedures, and infrastructure necessary to support information security in compliance with established company policies, regulatory requirements, and generally accepted information security controls pertaining to data protection. Responsible for the delivery of strategic protection of data at rest. Ensures security solutions involving the use of technologies are well-conceived, designed and implemented in compliance with enterprise standards. How You Will Make An Impact: list of many bullet-like sentences (each line starts with something like "Working knowledge of the Protegrity platform..." etc). Those are duties/responsibilities. Required Qualifications: BS/BA degree... etc. Preferred Qualifications: list of items. Then there is a paragraph about "Please be advised that Elevance Health only accepts resumes..." etc. That's application instructions? Might be considered boilerplate? It's about agency resumes; maybe we can drop as it's not substantive? The instruction says remove application instructions. This is about resumes from agencies; could be considered application instruction. Probably drop. Then "Who We Are" etc. That's company description; maybe we can include as "About the role"? Actually "About the role" is not present; we could use "About the role" heading for company overview? The instructions say we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. We have location/hours/travel info: could be under "Schedule"? Actually schedule is about work hours, location, hybrid. Could be under "Schedule". But we have "Hours: Standard Working hours" and travel description about hybrid. So we could put under Schedule. We have Position Overview: could be under "About the role" (description of role). Or maybe "Responsibilities". But we also have "How You Will Make An Impact" which is essentially responsibilities/duties. So we could put that under Responsibilities. We have Required Qualifications: under Requirements or Qualifications. The instruction list includes Requirements and Qualifications as separate possible headings. We could combine? Probably use "Requirements" for required qualifications, and "Preferred Qualifications" maybe under "Qualifications"? But we have both required and preferred. Could do "Requirements" for required, and "Qualifications" for preferred? Or we could have "Required Qualifications" under Requirements and "Preferred Qualifications" under Qualifications. That seems fine. We have a list of many technical skills/experience under "How You Will Make An Impact". Those are responsibilities. Could also be considered Skills. But we already have Responsibilities. We have no explicit Pay, Benefits info. There's a paragraph about total rewards: "We offer a range of market-competitive total rewards that include merit increases, paid holidays, Paid Time Off, and incentive bonus programs (unless covered by a collective bargaining agreement), medical, dental, vision, short and long term disability benefits, 401(k) +match, stock purchase plan, life insurance, wellness programs and financial education resources, to name a few." That's benefits. So we can create a Benefits section. We have no explicit Pay info. So we should not create Pay section. We have schedule info: location/hours/travel. So we can create Schedule section. We have About the role: maybe we can include Position Overview under About the role. We have Responsibilities: How You Will Make An Impact. We have Requirements: Required Qualifications. We have Qualifications: Preferred Qualifications. We have Skills: maybe not needed; we could put technical skills under Responsibilities or Qualifications. But we already have those. We need to ensure we don't create sections with filler. All sections we create have real content. We must remove boilerplate: EEO, legal, vaccination policy, etc. Also remove "Who We Are", "How We Work", etc? Those are company description; maybe we can incorporate into About the role? But About the role is supposed to be about the role, not company. However we have Position Overview which is about role. So we can keep that. The "Who We Are" etc is company description; could be considered boilerplate? Not exactly, but it's not required. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Who We Are" is not explicitly listed, but it's more about company. Might be considered not substantive for the job? Could be kept as part of About the role? But we already have Position Overview. Might be safe to include a brief About the role using Position Overview only, and drop the Who We Are etc. We also need to drop duplicated lines: there may be none. Now produce HTML. Structure:
About the role
Position Overview text.
Responsibilities
- Working knowledge of the Protegrity platform across core components, including architecture concepts, deployment patterns, policy administration, integration troubleshooting, and performance and operational support.
- Experience deploying and supporting Infrastructure as Code using Terraform, including module usage, debugging plans and applies, environment promotion, and Terraform state management. ... etc for each bullet. We need to preserve all bullet points exactly as in the posting. Let's extract them from the "How You Will Make An Impact" section. The text: Working knowledge of the Protegrity platform across core components, including architecture concepts, deployment patterns, policy administration, integration troubleshooting, and performance and operational support. Experience deploying and supporting Infrastructure as Code using Terraform, including module usage, debugging plans and applies, environment promotion, and Terraform state management. Experience maintaining infrastructure, configuration, and code in GitHub (or similar), including pull request reviews, branching strategies, and release/change workflows. Experience supporting secure application integrations across AWS and at least one additional cloud platform (Azure or GCP), with the ability to troubleshoot cross-cloud connectivity and data protection solutions. Hands-on experience implementing serverless integration patterns using services such as AWS Lambda, Azure Functions, Google Cloud Functions, or Cloud Run, including identity, authentication, and security best practices. Working knowledge of Kubernetes platforms (EKS, AKS, GKE, or equivalent), including application connectivity, identity, secrets management, logging, and operational troubleshooting. Experience using Splunk to develop searches, analyze logs, and support troubleshooting, operational monitoring, and incident investigations. Experience working within ServiceNow for incident, request, and change management, with familiarity creating or maintaining request workflows and catalog items preferred. Experience supporting data protection solutions for object storage, databases, and file-based data transfers, including structured file formats, operational support, throughput considerations, and access patterns. Working knowledge of Snowflake connectivity, role-based access concepts, security model, and data integration patterns. Experience integrating applications and pipelines with HashiCorp Vault, including authentication methods, secret consumption patterns, and secret rotation practices. Experience performing operational activities with Hardware Security Modules (HSMs), including initialization, partition and user administration, key management activities, and integration troubleshooting. We need to keep each as
- .
Now Requirements (Required Qualifications):
"Requires BS/BA degree in Information Technology or related field of study and a minimum of 5 years experience in systems support, system administration, system engineering, system security, access management, network security, network communications, computer networking, telecommunications, systems development and management, hardware, software, and/or data; or any combination of education and experience, which would provide an equivalent background.Requires experience in planning and designing highly complex systems."
Note there is a missing period between "...equivalent background.Requires". We'll keep as is.
We can put as
maybe but it's a single paragraph. Could also be
- but it's not a list. Use
- each.
Now Benefits:
From "We offer a range of market-competitive total rewards that include merit increases, paid holidays, Paid Time Off, and incentive bonus programs (unless covered by a collective bargaining agreement), medical, dental, vision, short and long term disability benefits, 401(k) +match, stock purchase plan, life insurance, wellness programs and financial education resources, to name a few."
We'll put as
maybe but it's a list of benefits; could be
- . Use
- each item separated by commas? Better to split: merit increases, paid holidays, Paid Time Off, incentive bonus programs (unless covered by a collective bargaining agreement), medical, dental, vision, short and long term disability benefits, 401(k) +match, stock purchase plan, life insurance, wellness programs, financial education resources. We'll keep as list. Now Schedule: We have location and hours/travel. Location: Indianapolis IN, Mason OH, Atlanta GA,
. Now Qualifications (Preferred Qualifications): "Experience with multiple technical and business disciplines strongly preferredSecurity Certifications: CISSP or other technical security certifications (e.g. Systems Security Certified Practitioner, Certification and Accreditation Professional) strongly preferredPrior experience with field level protection solutionsPrior experience managing on prem and cloud infrastructureStrong technical troubleshooting skillsSelf motivated/self starterPassion for mentoring others on teamOwnership to resolution of technical issuesLeadership" We need to split into list items? The original is a run-on sentences without punctuation. We could treat each phrase as separate bullet? But we must preserve all substantive information; we could keep as a single paragraph but it's hard to read. Better to split into logical items based on the phrases separated by missing punctuation. However we must not invent or summarize away detail. Splitting could be considered rephrasing but not adding info. It's okay to format as list items each representing a distinct qualification. The original lacked punctuation; we can infer separate items: "Experience with multiple technical and business disciplines strongly preferred", "Security Certifications: CISSP or other technical security certifications (e.g. Systems Security Certified Practitioner, Certification and Accreditation Professional) strongly preferred", "Prior experience with field level protection solutions", "Prior experience managing on prem and cloud infrastructure", "Strong technical troubleshooting skills", "Self motivated/self starter", "Passion for mentoring others on team", "Ownership to resolution of technical issues", "Leadership". That seems reasonable. We'll output as
- each.
Now Benefits:
From "We offer a range of market-competitive total rewards that include merit increases, paid holidays, Paid Time Off, and incentive bonus programs (unless covered by a collective bargaining agreement), medical, dental, vision, short and long term disability benefits, 401(k) +match, stock purchase plan, life insurance, wellness programs and financial education resources, to name a few."
We'll put as