Support in Siem

**EXPERIENCE AND EDUCATION**:
**Essential Qualifications/Experience**:

- A good understanding of IT Security
- 2+ years of relevant experience and strong technical skills in administering, deploying, installing, configuring and maintaining large distributed Splunk Enterprise environment
- Good programming skills in at least one of these languages: Ansible.python or bash
- A good understanding of networking and various protocols such as TCP/IP, HTTP(S), DNS
- Strong reporting skills to various levels of seniority

**DUTIES/ROLE**:

- Log collection
- Manage log collection of new data log sources in SIEM which includes, but is not limited to, log ingestion process from various data sources located on premise or in the cloud, data mapping to Splunk Common Information Model, integration with existing Splunk data models, testing log ingestion, validating log ingestion quality with stakeholders
- Document all relevant information in Confluence in accordance with CSDE standards
- Coordinate such activity with CSDE team and T3 customers
- Outcome:

- Assigned tasks shall be completed within the time allocated for this task by the requestor in the NCSC ticketing system(s). In case of an external request, the time to consider will be the time allocated by the CSDE cell head, the SDM or one of their delegated authorities
- Quality of log collection shall be reviewed by Security Analysts and confirmed as in line with expectations in the ticket
- Service availability and monitoring
- Act as one of the engineers and Subject Matter Expert (SME) for SIEM and Log Collection services within the Cyber Security Data team
- Monitoring the availability and performance of the SIEM environment including log collection
- Detecting and reporting to SDM any service degradation
- Taking appropriate actions to restore the environment to a fully operational state when a problem is detected
- Following best practices for maintaining the Splunk environment in a stable and reliable state with the objective of preventing any service degradation
- Ensure that data security systems operate within any KPI’s, as defined in Service Level Agreements with NCSC customers
- Outcome:

- Service degradation must be detected in less than 2 hours during standard working hours. This measure will be based on the ticket creation time compared to the issue occurrence time
- Availability of the splunk environment must stay above 99.8% uptime in a fully operational state
- Change management
- Follow NCSC Change management process to get approval before implementing changes. This includes, but is not limited to, creating the change request, ensure all necessary information is provided in due diligence, following up the change request to ensure quick approval, attending to CAB meeting when necessary, providing impact assessment when required
- Coordinate all these changes with CSDE and external teams
- Develop and maintain documentation guidelines, standard operating procedures, system and service design documents and other relevant documentation that support management of the data security systems
- Outcome
- Assigned tasks shall be completed within the time allocated for this task by the requestor in the NCSC ticketing system(s). In case of an external request, the time to consider will be the time allocated by the CSDE cell head, the SDM or one of their delegated authorities
- Reporting and advisory role
- Attending meeting when there is a need for representing the cell, for providing technical advice or for reporting relevant information to the team or other stakeholders
- Reporting any relevant information to the cell head, the SDM or other team members
- Outcome:

- Quality of the reporting to be assessed by the Cell Head or the SDM
- Providing support to customers
- Provide support to customers (mainly security analysts but not limited to them) facing issues or needing technical assistance
- Outcome:

- Tickets should be closed within the time allocated by the Cell Head, the SDM or their delegated authorities
- Problem resolution shall be confirmed by the requestor in the ticket