InfoSec GRC Business Engineer (Contract)
- . For prose, use
. We need to avoid repeating job title as heading (not present). Do not put Job ID/requisition numbers as headings (none). We need to output only HTML fragment. Let's craft:
About the role
This role is a contract assignment at Palo Alto Networks. Contractors will not be employed by Palo Alto Networks but through our trusted staffing partners. Location: Santa Clara (Hybrid). Duration: 6 Months.
Responsibilities
- Maintain security risk exceptions queue for the InfoSec GRC team
- Interact with business users and InfoSec stakeholders to review security risk exceptions for appropriate business justification, description of risk, impact, mitigating controls, and remediation plans
- Answer general user questions regarding navigating the risk exception process
- Conduct user outreach to drive risk exceptions to closure
- Conduct reporting related to risk exceptions
Requirements
- B.S. in Computer Science / CyberSecurity or equivalent experience
- Relevant certifications (CISSP, CISM, CISA, CRISC) with 4‑5 years of experience
- Relevant certifications of 4-5 yrs (CISSP, CISM, CISA, CRISC)
- Knowledge of Information Security domains, controls, and compensating controls
- Knowledge of cloud security and application security concepts
- Experience with risk management processes
- Strong analytical and problem-solving skills
- Excellent communication and collaboration abilities
- Ability to work independently and manage multiple priorities
- Medical
- Dental
- Vision
- 401K
- for any list of duties/requirements/benefits. Benefits is a list, so we should use list.
Thus:
Benefits
- Medical
- Dental
- Vision
- 401K
Pay
The compensation offered for this position will depend on qualifications, experience, and work location. For candidates who receive an offer, this is the pay range that Magnit reasonably expects to pay for this position: $85/hour - $90/hour. Please note that the compensation information in this posting reflects the hourly wage only and does not include benefits.
We might also include the note about sponsorship: "Magnit is not able to provide assistance to candidates requiring sponsorship or a visa for this position." That's substantive; where to put? Could be under Pay or a separate section like Notes. But we only have predefined headings; we could incorporate into Pay paragraph as extra sentence. Thus Pay paragraph includes that note. We also have "Information About Palo Alto Networks" description. That could go under About the role? Or maybe a separate section like "About the company". But not in list of allowed headings. Could be part of About the role? The heading "About the role" is for role description; company info maybe could be included there as extra paragraph. But we should not invent headings not in list. We could add a paragraph under About the role after the location/duration. Thus About the role paragraph: include contract assignment, location, duration, and then company description. Let's craft:About the role
This role is a contract assignment at Palo Alto Networks. Contractors will not be employed by Palo Alto Networks but through our trusted staffing partners. Location: Santa Clara (Hybrid). Duration: 6 Months.
At Palo Alto Networks®, everything starts and ends with our mission: Being the cybersecurity partner of choice, protecting our digital way of life. We have the vision of a world where each day is safer and more secure than the one before. These aren’t easy goals to accomplish — but we’re not here for easy. We’re here for better. We are a company built on the foundation of challenging and disrupting the way things are done, and we’re looking for innovators who are as committed to shaping the future of cybersecurity as we are.
That preserves all. Now check we didn't miss any substantive info: The "Your Impact" section we turned into Qualifications? Actually "Your Impact" includes knowledge statements; we moved them to Qualifications. That's okay. "Your Experience" we moved to Requirements. "Key Competencies" we moved to Skills. "Education" we could also include under Requirements or Qualifications? Actually Education is Bachelor's degree etc. We already have B.S. in Computer Science / CyberSecurity or equivalent experience in Requirements. Education also includes "Relevant certifications such as CISSP, CISM, CISA, or CRISC". That's similar to certifications. We might duplicate. But we need to preserve all info; we can include both but avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include both lines even if similar. However we can combine them if they are same meaning? They are slightly different: one says "Relevant certifications of 4-5 yrs (CISSP, CISM, CISA, CRISC)" (implies 4-5 years experience with certs). The other says "Relevant certifications such as CISSP, CISM, CISA, or CRISC" (no years). To preserve both, we could list both as separate list items. Thus Requirements list could have: - B.S. in Computer Science / CyberSecurity or equivalent experience - Relevant certifications of 4-5 yrs (CISSP, CISM, CISA, CRISC) - Relevant certifications such as CISSP, CISM, CISA, or CRISC But that seems redundant. However we must preserve. Could combine into one item with both details? That would be summarizing? Might be okay to combine as it's not losing detail. The instruction: do NOT invent or summarize away detail. Combining is not summarizing away; it's just combining two statements into one sentence preserving both details. That should be fine. Thus Requirements: - B.S. in Computer Science / CyberSecurity or equivalent experience
- Relevant certifications of 4-5 yrs (CISSP, CISM, CISA, CRISC); also relevant certifications such as CISSP, CISM, CISA, or CRISC But that's awkward. Maybe better to keep two separate items; it's not losing detail. It's okay to have similar items. We
Qualifications
Skills
Benefits
Magnit offers Medical, Dental, Vision and 401K.
but instruction: Use