D3 Responsibility and self-management
Introduction
In this document, I will be demonstrating the different ways I have shown individual responsibility
and self-management. Both these will need to have been done effectively to ensure the planning
and protection of the IT system is carried out to offer the highest level of defence against both
external and internal threats.
Planning and recording
Throughout the process of developing the IT system security, I have planned out each stage so that it
covers every aspect of security - this includes physical and software security, and evolving policies
and procedures. By doing this planning, I made sure that I didn’t miss any parts of the network that
need protecting. The use of a Gantt chart allowed me to set time -based targets, which ensured that
every protection method would be undertaken in a formally fashion. Recording the work undertaken
was carried out at every stage, with documents and screenshots displaying what had been done to
enhance the security on the system. Feedback from others was collected in many ways, the first was
having weekly meetings to discuss the progress that had been made on certain projects and monthly
meetings to review and edit policies. These meetings were attended by members of management,
whilst emails were how other members of staff were able to get in contact with me. The feedback
gathered took many forms, with emails, meeting minutes and face -to-face conversations allowing
me to plan and record what work I needed to do next.
Figure 1.0: Gantt chart Figure 1.1: Progress table
Reviewing
To ensure that the protection applied to the network was effective, I had to undertake several
reviews and tests. These made sure that everything had been set up to the highest level and was
robust enough to stand up against external and internal threats. Involved within this was responding
to any issues that occurred, for example, finding that a firewall port was open - when it's not meant
to be - and closing it before any damage is caused. I also took feedback from fellow IT professionals;
this allowed me to be sent any issues that arose, fixing them and resolving the issue. My reviewing
process involved going through a number of tasks to identify any weaknesses in the system - this
was effective as it covered all aspects and scenarios on the network. Foll owing this, I wrote a
conclusion which looked over what was implemented and how it performed in the test. I found that
Unit 7: IT Systems Security and Encryption
, all my methods thoroughly protected the system without hindering the systems everyday use (e.g.
visiting certain websites, accessing certain folders).
Figure 2.0: Testing table Figure 2.1: Email
Professionalism
During my time working on the IT system, I had to maintain a level of professionalism which saw me
perform tasks as quickly as I could, whilst remaining calm in these under-pressure situations. When
undertaking this work, I had to use specific terminology with others to ensure they knew exactly
what I was talking about and the complexity of each task. In addition, I used formal language to
remain presentable, polite and professional - this was most evident in my emails, which show me
using formal language to ask and answer questions from colleagues. When answering emails from
others I had to be supportive to ensure their issues could be resolved, whilst showing leadership by
making clear I was the person to talk to if staff came across any problems with the IT system.
Anything that went wrong on the system was my responsibility, meaning I was accountable for
anything that happened. For this reason, I had to make sure that everything was configured correctly
to prevent liability to problems.
Figure 3.0: Email Figure 3.1: Email
Outcomes
In order to make recommendations or decisions I had to go through a number of different tests.
These involved checking whether protection techniques have worked by looking at all avenues and
testing using varied techniques. By going through I ensured that me final decision was high-quality or
that the recommendation had systematic evidence behind it. To ensure all outcomes were high-
quality, I had to change anything that could be seen as a weakness - this maintains the highest level
of protection and makes sure that all recommendations are fully justified. Decisions had to always
be based upon what was best to do, for example, closing Firewall ports and blocking certain
connections made sure that no external hackers could gain access to the network. When in
meetings, we would discuss what things could be changed/or added - talking about their benefit -
Unit 7: IT Systems Security and Encryption
Introduction
In this document, I will be demonstrating the different ways I have shown individual responsibility
and self-management. Both these will need to have been done effectively to ensure the planning
and protection of the IT system is carried out to offer the highest level of defence against both
external and internal threats.
Planning and recording
Throughout the process of developing the IT system security, I have planned out each stage so that it
covers every aspect of security - this includes physical and software security, and evolving policies
and procedures. By doing this planning, I made sure that I didn’t miss any parts of the network that
need protecting. The use of a Gantt chart allowed me to set time -based targets, which ensured that
every protection method would be undertaken in a formally fashion. Recording the work undertaken
was carried out at every stage, with documents and screenshots displaying what had been done to
enhance the security on the system. Feedback from others was collected in many ways, the first was
having weekly meetings to discuss the progress that had been made on certain projects and monthly
meetings to review and edit policies. These meetings were attended by members of management,
whilst emails were how other members of staff were able to get in contact with me. The feedback
gathered took many forms, with emails, meeting minutes and face -to-face conversations allowing
me to plan and record what work I needed to do next.
Figure 1.0: Gantt chart Figure 1.1: Progress table
Reviewing
To ensure that the protection applied to the network was effective, I had to undertake several
reviews and tests. These made sure that everything had been set up to the highest level and was
robust enough to stand up against external and internal threats. Involved within this was responding
to any issues that occurred, for example, finding that a firewall port was open - when it's not meant
to be - and closing it before any damage is caused. I also took feedback from fellow IT professionals;
this allowed me to be sent any issues that arose, fixing them and resolving the issue. My reviewing
process involved going through a number of tasks to identify any weaknesses in the system - this
was effective as it covered all aspects and scenarios on the network. Foll owing this, I wrote a
conclusion which looked over what was implemented and how it performed in the test. I found that
Unit 7: IT Systems Security and Encryption
, all my methods thoroughly protected the system without hindering the systems everyday use (e.g.
visiting certain websites, accessing certain folders).
Figure 2.0: Testing table Figure 2.1: Email
Professionalism
During my time working on the IT system, I had to maintain a level of professionalism which saw me
perform tasks as quickly as I could, whilst remaining calm in these under-pressure situations. When
undertaking this work, I had to use specific terminology with others to ensure they knew exactly
what I was talking about and the complexity of each task. In addition, I used formal language to
remain presentable, polite and professional - this was most evident in my emails, which show me
using formal language to ask and answer questions from colleagues. When answering emails from
others I had to be supportive to ensure their issues could be resolved, whilst showing leadership by
making clear I was the person to talk to if staff came across any problems with the IT system.
Anything that went wrong on the system was my responsibility, meaning I was accountable for
anything that happened. For this reason, I had to make sure that everything was configured correctly
to prevent liability to problems.
Figure 3.0: Email Figure 3.1: Email
Outcomes
In order to make recommendations or decisions I had to go through a number of different tests.
These involved checking whether protection techniques have worked by looking at all avenues and
testing using varied techniques. By going through I ensured that me final decision was high-quality or
that the recommendation had systematic evidence behind it. To ensure all outcomes were high-
quality, I had to change anything that could be seen as a weakness - this maintains the highest level
of protection and makes sure that all recommendations are fully justified. Decisions had to always
be based upon what was best to do, for example, closing Firewall ports and blocking certain
connections made sure that no external hackers could gain access to the network. When in
meetings, we would discuss what things could be changed/or added - talking about their benefit -
Unit 7: IT Systems Security and Encryption
