Cybersecurity Business Analyst — Data Risk – Multiple Offices (Hybrid)
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must only include sections when posting has real specific content. All sections we plan have content.
We must not include filler like "commensurate with experience". Not present.
We need to preserve all substantive info: role description, hybrid location list, salary range, bonuses, responsibilities bullet list, requirements bullet list, qualifications bullet list, benefits list, About Littler description.
We must not invent or summarize away detail. So keep details.
We need to format responsibilities as list items under
Responsibilities
. Similarly Requirements, Qualifications, Benefits.
About the role: maybe a with the role description paragraph(s). Also include hybrid location and schedule? Could be separate Schedule section.
Pay section:
Pay
with containing salary range and bonus eligibility.
Schedule section:
Schedule
with describing hybrid and onsite once per month.
We must not repeat job title as heading. So no heading for Cybersecurity Business Analyst - Data Risk.
We must not put Job ID/requisition numbers as headings.
We must output only HTML fragment, no /, no markdown.
Let's craft.
First, About the role: combine first two paragraphs: "The Cybersecurity Business Analyst - Data Risk, is responsible for identifying, analyzing, and helping remediate risks to the firm's sensitive and regulated data throughout its lifecycle. The role bridges security, privacy, compliance, and business teams—translating data protection requirements into actionable controls, clear reporting, and prioritized risk decisions that reduce exposure while enabling the business." Also mention hybrid position and locations? Might be better to put location in Schedule? Actually location is part of role description; but we have Schedule section for onsite expectation. Location list could be in About the role or maybe a separate Location section? Not required headings; we can include location in About the role paragraph.
Thus About the role paragraph includes hybrid position and list of locations.
Now Responsibilities: list items as given.
Requirements: list items as given under "Requirements, reporting, and analysis". Actually the heading "Requirements, reporting, and analysis" includes responsibilities? Wait the posting: after Responsibilities, there is "Requirements, reporting, and analysis" then bullet list. That seems like a section of responsibilities? Actually it's more like "Requirements, reporting, and analysis" as a functional area. But we have separate Requirements section for qualifications? The posting also has "Qualifications" later. So we need to map: The bullet list under "Requirements, reporting, and analysis" is actually part of responsibilities (like gathering requirements, building dashboards, etc). So we should treat that as part of Responsibilities. The "Qualifications" section later includes Preferred qualifications and Certifications.
Thus we need to split: Responsibilities includes all bullet points under "Data risk analysis and assessment", "Data governance and controls", "Requirements, reporting, and analysis", "Stakeholder enablement and collaboration". So we combine all those bullet points into one list under Responsibilities.
Then Requirements section: maybe we don't have a separate "Requirements" heading besides qualifications? The posting uses "Requirements, reporting, and analysis" as a functional area, not a qualifications section. The actual qualifications are under "Qualifications". So we may not have a separate Requirements section; we could omit Requirements heading if no explicit qualifications list besides Qualifications. But the instruction says use headings for Requirements if posting has real specific content. The posting does not have a separate "Requirements" section besides Qualifications. So we should not create a Requirements heading. Instead we have Qualifications heading.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule.
Check if we need a separate "Requirements" heading: The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they list possible headings but we only include those with content. Since there is no explicit Requirements bullet list separate from Qualifications, we skip Requirements.
Now Qualifications: include Preferred qualifications bullet list and Certifications bullet list. Could combine into one list or separate? We'll make one list under Qualifications.
Benefits: list items as given.
Pay: salary range and bonus eligibility.
Schedule: hybrid position and onsite expectation once per month.
Now ensure we preserve all substantive info: include list of locations, mention that it's hybrid, onsite once per month.
Also include note about Washington and Minneapolis regulations salary range.
Also mention eligibility for performance-based bonuses.
Also mention factors affecting starting pay.
Also mention "We offer generous compensation and benefits packages." and link.
Also include About Littler paragraph(s). That is part of About the role? Could be separate About the company but not required heading. We could include in About the role after role description. Or we could add a separate section "About Littler" but not in allowed headings; but we could incorporate into About the role as a paragraph.
Better to keep About the role as role description only, and maybe add a separate paragraph about Littler under same heading? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So About the role heading likely expects description of the role, not company. But we can still include company info under same heading as prose; it's still substantive. Might be okay.
Alternatively we could add a separate heading "About Littler" but not in list; risk of being considered filler. Safer to include under About the role.
Thus About the role About the role
then
containing role description + hybrid location + onsite expectation + maybe company description.
But we also have separate Pay and Schedule sections; we should not duplicate location/schedule in About the role if we put them in Schedule. However we need to keep location list somewhere; we could put location list in About the role (makes sense). Schedule section can mention onsite expectation once per month. Hybrid nature could be mentioned in About the role or Schedule. Let's put location list in About the role, and Schedule section just mentions onsite expectation once per month (and maybe hybrid). But we need to convey hybrid nature; we can mention in About the role that it's a hybrid position.
Thus About the role paragraph: "The Cybersecurity Business Analyst - Data Risk, is responsible for identifying, analyzing, and helping remediate risks to the firm's sensitive and regulated data throughout its lifecycle. The role bridges security, privacy, compliance, and business teams—translating data protection requirements into actionable controls, clear reporting, and prioritized risk decisions that reduce exposure while enabling the business. This is a hybrid position and can be resident in Phoenix, AZ; Atlanta, GA; Minneapolis, MN; Seattle, WA; Charlotte, NC; Miami or Orlando, FL; or Dallas, TX."
Then Schedule section:
Schedule
Onsite expectation of once per month.
Pay section: Pay
Pursuant to Washington and Minneapolis regulations, the salary range is $137,800 to $151,600 annually and includes eligibility for performance-based bonuses. Factors which may affect starting pay within this range may include geography/market, skills, education, experience and other qualifications of the successful candidate.
We could also include "We offer generous compensation and benefits packages." maybe in Benefits or Pay. But we already have Benefits section.
Now Responsibilities: need to list all bullet points.
Let's extract bullet points:
From Data risk analysis and assessment:
- Maintain an inventory of sensitive and regulated data, data flows, systems, and third-party sharing.
- Conduct data risk assessments covering confidentiality, integrity, availability, and regulatory exposure.
- Analyze data classification, access, retention, and handling to identify gaps and control weaknesses.
- Quantify and prioritize data risks, and track remediation activities through to closure.
Data governance and controls:
- Support data classification, DLP, and data protection policies and standards.
- Translate privacy and regulatory requirements (e.g., GDPR, CCPA, HIPAA where applicable) into data control requirements.
- Partner with control owners to define, document, and validate data safeguards.
- Monitor control effectiveness and produce metrics on the firm’s data risk posture.
Requirements, reporting, and analysis:
- Gather and document business and security requirements for data protection initiatives.
- Build dashboards and reports on data risk, exposure, and remediation progress for leadership.
- Perform root-cause and trend analysis on data incidents, DLP alerts, and access anomalies.
- Support audits and client assessments with data risk evidence and documentation.
Stakeholder enablement and collaboration:
- Serve as a liaison between Security, Privacy, Risk, IT, and business stakeholders.
- Translate technical data risks into clear business language and actionable recommendations.
- Provide guidance that helps teams handle data safely and meet compliance obligations.
- Support response to data-related incidents, findings, and control failures.
We'll make a with - for each.
Now Qualifications:
Preferred qualifications:
- Experience in a legal, professional services, or other highly regulated environment.
- Familiarity with data governance and risk platforms (e.g., OneTrust, Microsoft Purview, ServiceNow).
- Comfort with data analysis and visualization tools (e.g., Excel / Power BI) and basic querying (e.g., SQL).
Certifications:
- Core security / risk: CISM, CRISC, or CISSP.
- Data / privacy: CIPP, CIPM, or CDPSE.
- Governance / analysis: ISO/IEC 27001 lead implementer/auditor or a recognized business analysis certification (e.g., CBAP).
We'll combine into one list under Qualifications.
Now Benefits:
List:
- comprehensive health, dental and vision plan for you, your spouse/domestic partner and children.
- superior 401(k) plan.
- ample time off programs.
- mental health programs.
- family building and caregiving.
- generous paid parental leave.
- life insurance.
- disability insurance.
- a wellness program.
- flexible spending accounts.
- employee referral bonus program.
Also mention "We offer a generous benefits package to full-time and part-time employees working at least a 50% schedule." and link for more info: https://www.littler.com/benefits/state-details. Also link for firm: www.littler.com. We can keep that as prose after list or as part of Benefits section.
We should not include application instructions like email, careers page, no recruiters, etc.
Now About Littler description: we can include as a paragraph under About the role after role description? Might be lengthy but okay.
Let's craft HTML.
We'll start with
About the role
then containing role description + hybrid location + maybe company description.
We'll add a second paragraph for About Littler if needed; but we can keep as same
with two sentences.
Better to separate:
role description + hybrid location. Then another <
for prose. We must only include sections when posting has real specific content. All sections we plan have content. We must not include filler like "commensurate with experience". Not present. We need to preserve all substantive info: role description, hybrid location list, salary range, bonuses, responsibilities bullet list, requirements bullet list, qualifications bullet list, benefits list, About Littler description. We must not invent or summarize away detail. So keep details. We need to format responsibilities as list items under
Responsibilities
. Similarly Requirements, Qualifications, Benefits. About the role: maybe awith the role description paragraph(s). Also include hybrid location and schedule? Could be separate Schedule section. Pay section:
Pay
withcontaining salary range and bonus eligibility. Schedule section:
Schedule
withdescribing hybrid and onsite once per month. We must not repeat job title as heading. So no heading for Cybersecurity Business Analyst - Data Risk. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment, no /, no markdown. Let's craft. First, About the role: combine first two paragraphs: "The Cybersecurity Business Analyst - Data Risk, is responsible for identifying, analyzing, and helping remediate risks to the firm's sensitive and regulated data throughout its lifecycle. The role bridges security, privacy, compliance, and business teams—translating data protection requirements into actionable controls, clear reporting, and prioritized risk decisions that reduce exposure while enabling the business." Also mention hybrid position and locations? Might be better to put location in Schedule? Actually location is part of role description; but we have Schedule section for onsite expectation. Location list could be in About the role or maybe a separate Location section? Not required headings; we can include location in About the role paragraph. Thus About the role paragraph includes hybrid position and list of locations. Now Responsibilities: list items as given. Requirements: list items as given under "Requirements, reporting, and analysis". Actually the heading "Requirements, reporting, and analysis" includes responsibilities? Wait the posting: after Responsibilities, there is "Requirements, reporting, and analysis" then bullet list. That seems like a section of responsibilities? Actually it's more like "Requirements, reporting, and analysis" as a functional area. But we have separate Requirements section for qualifications? The posting also has "Qualifications" later. So we need to map: The bullet list under "Requirements, reporting, and analysis" is actually part of responsibilities (like gathering requirements, building dashboards, etc). So we should treat that as part of Responsibilities. The "Qualifications" section later includes Preferred qualifications and Certifications. Thus we need to split: Responsibilities includes all bullet points under "Data risk analysis and assessment", "Data governance and controls", "Requirements, reporting, and analysis", "Stakeholder enablement and collaboration". So we combine all those bullet points into one list under Responsibilities. Then Requirements section: maybe we don't have a separate "Requirements" heading besides qualifications? The posting uses "Requirements, reporting, and analysis" as a functional area, not a qualifications section. The actual qualifications are under "Qualifications". So we may not have a separate Requirements section; we could omit Requirements heading if no explicit qualifications list besides Qualifications. But the instruction says use headings for Requirements if posting has real specific content. The posting does not have a separate "Requirements" section besides Qualifications. So we should not create a Requirements heading. Instead we have Qualifications heading. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. Check if we need a separate "Requirements" heading: The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they list possible headings but we only include those with content. Since there is no explicit Requirements bullet list separate from Qualifications, we skip Requirements.
Now Qualifications: include Preferred qualifications bullet list and Certifications bullet list. Could combine into one list or separate? We'll make one list under Qualifications.
Benefits: list items as given.
Pay: salary range and bonus eligibility.
Schedule: hybrid position and onsite expectation once per month.
Now ensure we preserve all substantive info: include list of locations, mention that it's hybrid, onsite once per month.
Also include note about Washington and Minneapolis regulations salary range.
Also mention eligibility for performance-based bonuses.
Also mention factors affecting starting pay.
Also mention "We offer generous compensation and benefits packages." and link.
Also include About Littler paragraph(s). That is part of About the role? Could be separate About the company but not required heading. We could include in About the role after role description. Or we could add a separate section "About Littler" but not in allowed headings; but we could incorporate into About the role as a paragraph.
Better to keep About the role as role description only, and maybe add a separate paragraph about Littler under same heading? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So About the role heading likely expects description of the role, not company. But we can still include company info under same heading as prose; it's still substantive. Might be okay.
Alternatively we could add a separate heading "About Littler" but not in list; risk of being considered filler. Safer to include under About the role.
Thus About the role About the role
then
About the role
thencontaining role description + hybrid location + onsite expectation + maybe company description. But we also have separate Pay and Schedule sections; we should not duplicate location/schedule in About the role if we put them in Schedule. However we need to keep location list somewhere; we could put location list in About the role (makes sense). Schedule section can mention onsite expectation once per month. Hybrid nature could be mentioned in About the role or Schedule. Let's put location list in About the role, and Schedule section just mentions onsite expectation once per month (and maybe hybrid). But we need to convey hybrid nature; we can mention in About the role that it's a hybrid position. Thus About the role paragraph: "The Cybersecurity Business Analyst - Data Risk, is responsible for identifying, analyzing, and helping remediate risks to the firm's sensitive and regulated data throughout its lifecycle. The role bridges security, privacy, compliance, and business teams—translating data protection requirements into actionable controls, clear reporting, and prioritized risk decisions that reduce exposure while enabling the business. This is a hybrid position and can be resident in Phoenix, AZ; Atlanta, GA; Minneapolis, MN; Seattle, WA; Charlotte, NC; Miami or Orlando, FL; or Dallas, TX." Then Schedule section:
Schedule
Onsite expectation of once per month.
Pay section:Pay
Pursuant to Washington and Minneapolis regulations, the salary range is $137,800 to $151,600 annually and includes eligibility for performance-based bonuses. Factors which may affect starting pay within this range may include geography/market, skills, education, experience and other qualifications of the successful candidate.
We could also include "We offer generous compensation and benefits packages." maybe in Benefits or Pay. But we already have Benefits section. Now Responsibilities: need to list all bullet points. Let's extract bullet points: From Data risk analysis and assessment: - Maintain an inventory of sensitive and regulated data, data flows, systems, and third-party sharing. - Conduct data risk assessments covering confidentiality, integrity, availability, and regulatory exposure. - Analyze data classification, access, retention, and handling to identify gaps and control weaknesses. - Quantify and prioritize data risks, and track remediation activities through to closure. Data governance and controls: - Support data classification, DLP, and data protection policies and standards. - Translate privacy and regulatory requirements (e.g., GDPR, CCPA, HIPAA where applicable) into data control requirements. - Partner with control owners to define, document, and validate data safeguards. - Monitor control effectiveness and produce metrics on the firm’s data risk posture. Requirements, reporting, and analysis: - Gather and document business and security requirements for data protection initiatives. - Build dashboards and reports on data risk, exposure, and remediation progress for leadership. - Perform root-cause and trend analysis on data incidents, DLP alerts, and access anomalies. - Support audits and client assessments with data risk evidence and documentation. Stakeholder enablement and collaboration: - Serve as a liaison between Security, Privacy, Risk, IT, and business stakeholders. - Translate technical data risks into clear business language and actionable recommendations. - Provide guidance that helps teams handle data safely and meet compliance obligations. - Support response to data-related incidents, findings, and control failures. We'll make a- with
- for each.
Now Qualifications:
Preferred qualifications:
- Experience in a legal, professional services, or other highly regulated environment.
- Familiarity with data governance and risk platforms (e.g., OneTrust, Microsoft Purview, ServiceNow).
- Comfort with data analysis and visualization tools (e.g., Excel / Power BI) and basic querying (e.g., SQL).
Certifications:
- Core security / risk: CISM, CRISC, or CISSP.
- Data / privacy: CIPP, CIPM, or CDPSE.
- Governance / analysis: ISO/IEC 27001 lead implementer/auditor or a recognized business analysis certification (e.g., CBAP).
We'll combine into one list under Qualifications.
Now Benefits:
List:
- comprehensive health, dental and vision plan for you, your spouse/domestic partner and children.
- superior 401(k) plan.
- ample time off programs.
- mental health programs.
- family building and caregiving.
- generous paid parental leave.
- life insurance.
- disability insurance.
- a wellness program.
- flexible spending accounts.
- employee referral bonus program.
Also mention "We offer a generous benefits package to full-time and part-time employees working at least a 50% schedule." and link for more info: https://www.littler.com/benefits/state-details. Also link for firm: www.littler.com. We can keep that as prose after list or as part of Benefits section.
We should not include application instructions like email, careers page, no recruiters, etc.
Now About Littler description: we can include as a paragraph under About the role after role description? Might be lengthy but okay.
Let's craft HTML.
We'll start with
About the role
thencontaining role description + hybrid location + maybe company description. We'll add a second paragraph for About Littler if needed; but we can keep as same
with two sentences. Better to separate:
role description + hybrid location. Then another <