Vacancy
Cyber Security Process and Risk Awareness
Hybrid Slough and remote • Contract • £0.00-£0.00 Per Day
Summary
Overview
Cyber Security Process and Risk Awareness
Title: Cyber Security Process and Risk Awareness
Location: Slough/Hybrid
Duration: 6 months
Start 01/07/2024
Rate: Day rate negotiable on experience.
Skills
Cyber Security Process
Raising Cyber Security Awareness
Duties
Building Cyber Security Awareness
Ensuring Cyber Security Policy and strategy are turned into good processes.
Gather intelligence and disseminate it to the correct people
Run workshops on cybersecurity subjects.
Attend and contribute to the annual Cyber Sec Conference
Spot Cyber Security trends and research
Bring Cyber Security intelligence into the organisation.
ID Process identification and generating the relevant automation using Splunk. Training in Splunk provided.
It is not a technical role, but Splunk is lo-code, so it can do some stuff and then pass it to developers.
Incident documentation for management of incidents by frameworks, not writing playbooks framework-based approach key roles and functions, as no incidents are the same, you could write 36 playbooks, and then the 37th variety comes along.
Exchange ideas with other business units and teams in corporate structure.
Not policy writing.
Looking at corporate policy.
Familiarity with Audits not as an auditor but as an auditee.
Title: Cyber Security Process and Risk Awareness
Location: Slough/Hybrid
Duration: 6 months
Start 01/07/2024
Rate: Day rate negotiable on experience.
Skills
Cyber Security Process
Raising Cyber Security Awareness
Duties
Building Cyber Security Awareness
Ensuring Cyber Security Policy and strategy are turned into good processes.
Gather intelligence and disseminate it to the correct people
Run workshops on cybersecurity subjects.
Attend and contribute to the annual Cyber Sec Conference
Spot Cyber Security trends and research
Bring Cyber Security intelligence into the organisation.
ID Process identification and generating the relevant automation using Splunk. Training in Splunk provided.
It is not a technical role, but Splunk is lo-code, so it can do some stuff and then pass it to developers.
Incident documentation for management of incidents by frameworks, not writing playbooks framework-based approach key roles and functions, as no incidents are the same, you could write 36 playbooks, and then the 37th variety comes along.
Exchange ideas with other business units and teams in corporate structure.
Not policy writing.
Looking at corporate policy.
Familiarity with Audits not as an auditor but as an auditee.