The IT Professional
The IT Professional
The IT Professional
1
25/10/2024
2
25/10/2024
▪ Successful technicians control their own reactions and emotions from one customer call to the next
▪ A good rule for all technicians to follow is that a new customer call means a fresh start
➢ Never carry your frustration from one call to the next
3
25/10/2024
10
11
4
25/10/2024
13
Professional Behavior
Using Professional Behavior with the Customer
❖ The following list describes things that you should not do when talking with a customer:
▪ Do not minimize a customer’s problems
▪ Do not use jargon, abbreviations, acronyms, and slang
▪ Do not use a negative attitude or tone of voice
▪ Do not argue with customers or become defensive
▪ Do not say culturally insensitive remarks
▪ Do not disclose any experiences with customers on social media
16
5
25/10/2024
Professional Behavior
Using Professional Behavior with the Customer
❖ The following list describes things that you should not do when talking with a customer:
▪ Do not be judgmental or insulting or call the customer names
▪ Avoid distractions and do not interrupt when talking with customers
▪ Do not take personal calls when talking with customers
▪ Do not talk to co-workers about unrelated subjects when talking with the customer
▪ Avoid unnecessary holds and abrupt holds
▪ Do not transfer a call without explaining the purpose of the transfer and getting customer consent
▪ Do not use negative remarks about other technicians to the customer
17
Professional Behavior
Tips for Hold and Transfer
▪ When dealing with customers, it is necessary to be professional in all aspects of your role
▪ You must handle customers with respect and prompt attention
▪ When on a telephone, make sure that you know
o how to place a customer on hold, as well as
o how to transfer a customer without losing the call.
19
6
25/10/2024
Professional Behavior
Tips for Hold and Transfer
❖ Putting a customer on hold:
20
Professional Behavior
Tips for Hold and Transfer
❖ Transferring a customer:
▪ Explain that you will transfer their call, to whom, and why
21
7
25/10/2024
▪ Give feedback
o Let the customer know that you understand the problem and
develop a friendly and positive conversational manner
23
2. Types of customers
24
8
25/10/2024
▪ Recognizing these traits will help them to manage the call accordingly
o A talkative customer
o A rude customer
o An angry customer
o A knowledgeable customer
o An inexperienced customer
25
26
9
25/10/2024
Types of Customers ▪ Complains during the call, makes negative comments, may be
abusive and uncooperative, and may be easily aggravated
▪ Apologize for the wait time and the inconvenience, even if there
has been no wait time
▪ Do not ask the customer to follow many obvious steps if there is a way you can determine the problem
without the customer
27
28
10
25/10/2024
▪ Tell the customer the overall approach to what you are trying to
verify
29
❖ An inexperienced customer
30
11
25/10/2024
31
▪ Netiquette are personal and business etiquette rules that govern email and text communications:
o Be pleasant and polite
o Begin each email with an appropriate greeting
o Never send chain letters via email
o Do not send or reply to flames
o Use mixed case
➢ Upper case is considered as shouting
o Check grammar and spelling before sending
o Be ethical
o Never mail or post anything you would not say to a person’s face
32
12
25/10/2024
▪ When working with many customers, do not give faster and better service to some favourite customers
▪ Do not take calls for other technicians unless you have permission to do so
33
13
25/10/2024
3. Organizational Documentation
36
Documentation
Documentation Overview
❖ Purposes for documentation include:
▪ Providing descriptions for how products, software, and hardware
function through the use of diagrams, descriptions, manual pages
and knowledgebase articles.
▪ Standardizing procedures and practices so that they can be
repeated accurately in the future.
▪ Establishing rules and restrictions on the use of the organization’s
assets including acceptable use policies for internet, network, and
computer usage.
▪ Reducing confusion and mistakes saving time and resources.
▪ Complying with governmental or industry regulations.
▪ Training new employees or customers.
37
14
25/10/2024
Documentation
IT Department Documentation
▪ Keeping documentation current is a challenge for even the best managed IT departments.
▪ In general, IT documentation falls into four categories: Policies, Operations, Projects, and User Documentation
38
Documentation
IT Department Documentation
39
15
25/10/2024
Documentation
Report and Procedures
▪ Acceptable Use Policy (AUP)
o This is an agreement between two or more parties that defines the appropriate user access to
resources or services
▪ Incident Report
o also known as an After-Action Report (AAR)
o AAR be used to document an episode of a critical and major incident, such as a security breach
o The purpose of the report is to identify potential issues, provide insight for improvements, and allow
prompt corrective action to prevent a similar event in the future
40
Documentation
Reports and Procedures
▪ Standard Operating Procedures (SOP)
o These are step-by-step instructions to guide employees on how to use computers and networked
services
• efficiently
• securely
• and expected responsibilities
o The main goals are to establish uniformity across the company, create high-quality work consistently,
and reduce miscommunications
o SOP can also be in the form of user checklists
41
16
25/10/2024
Documentation
Reports and Procedures
▪ Standard operating procedures (SOP)
o Two examples of user checklists are:
42
Documentation
Knowledge Base and Articles
▪ A knowledge base is a centralized repository of articles and documents
▪ The knowledge base allows users to create, share, and manage knowledge across the organization
▪ The articles in the knowledge base can provide these common types of data:
o Answers to frequently asked questions (FAQs)
o Troubleshooting scenarios
o Internal database to support self-service support
o Training documents
o Links to external legitimate and verifiable knowledge base articles
44
17
25/10/2024
Documentation
Regulatory Compliance Requirements
▪ Federal, state, local, and industry regulations can have documentation requirements over and above
what is normally documented in the company’s records
▪ Regulatory and compliance policies often specify what data must be collected and how long it must be
retained
▪ A few of the regulations may have implications on internal company processes and procedures
▪ Some regulations require keeping extensive records regarding how the data is accessed and used
➢ Failure to comply with laws and regulations can have severe consequences, including
fines, termination of employment, and even incarceration of offenders.
45
Documentation
Asset Databases
❖ Asset management
▪ This is the tracking and management of assets to ensure that they are
o used properly
o maintained
o upgraded
o disposed of responsibly at the end of their lifecycles
▪ The organization needs an inventory of all the deployed hardware assets along with the consumables,
spare components in case of hardware failures, and software assets, such as warranty information,
licenses, and intellectual property (IP)
46
18
25/10/2024
Documentation
Asset Databases
❖ Asset management comprises of:
▪ Database system
o Many software solutions are available for businesses to manage and track their assets
o Asset management software can improve the visibility and management of the assets to reduce
hardware and software costs
47
Documentation
Asset Procurement
❖ Procurement life cycle
▪ Each asset goes through five main stages during its life:
▪ Planning
o Analysis of the organization’s current and future needs combined with potential asset impact on business,
network, daily operations and implemented devices is needed before requesting a new or upgraded asset
▪ Procurement/Acquire
o A budget is determined, and a supplier or vendor is identified to deliver the asset
▪ Deployment
o The procured asset can be installed or integrated with the other tools in the business to be used
48
19
25/10/2024
Documentation
Asset Procurement
❖ Procurement life cycle
▪ Each asset goes through five main stages during its life:\
▪ Maintenance
o Provisions should be made to keep your assets in operating condition to optimize their use
▪ Disposal
o When an asset has reached the end of life, the asset should be sanitized of any data
o The sanitized asset can be sold, recycled, donated, or destroyed.
49
Documentation
Asset Procurement
❖ Procurement life cycle
50
20
25/10/2024
Documentation
Asset Procurement
❖ Assigned users
▪ Depending on the type of assets, the assets can be assigned to individuals or shared within the entire
organization
▪ Typical assets managed by individual accounts:
o Workstations
o Laptops
o Mobile devices, like smartphones and tablets
o Software license Shared assets managed by individuals or security groups within a department:
• Servers
• Routers
• Switches
• Access points
51
53
21
25/10/2024
55
▪ Some aspects of the network design that should be included in the disaster recovery are:
o Are there backup connectivity options and is there redundancy in the network design?
o Availability of offsite servers or cloud providers that can support applications such as email and database
services
57
22
25/10/2024
▪ Create an inventory of all locations, devices, vendors, used services, and contact names
▪ Verify cost estimates that are created in the risk assessment step
❖ Phase 3 - Verification
▪ Create a verification process to prove that the disaster recovery strategy works
▪ Practice disaster recovery exercises to ensure that the plan is up to date and workable
58
❖ Phase 5 - Review
▪ After the disaster recovery plan has been implemented for a year, review the plan
▪ Information in the plan must be kept up to date, or critical services may not be restored in the case of
a disaster
59
23
25/10/2024
60
61
24
25/10/2024
62
▪ The PCI Security Standards Council was formed in 2005 by the 5 major credit card companies in an
effort to protect account numbers, expiration dates, magnetic strip and chip data for transactions
around the globe
➢ For more information on PCI, visit www.pcisecuritystandards.org
63
25
25/10/2024
64
66
26
25/10/2024
❖ Licensing:
▪ Enterprise license: The company pays for the employees to use the software
▪ Open source license: This license allows developers to modify and share the codes
▪ Commercial license: The commercial license allows the licensee to make money from the software
▪ Digital rights management: The software is designed to prevent illegal access to digital content and
devices
67
68
27
25/10/2024
69
▪ Volatile data
o RAM, cache, and registries contain volatile data
o Data in transit between a storage medium and a CPU is also volatile data
o If you are reporting illegal activity or are part of an incident response team, it is important to know how
to capture this data, because it disappears as soon as the computer is turned off
70
28
25/10/2024
71
72
29
25/10/2024
73
▪ These procedures also prevent evidence tampering so that the integrity of the evidence can be
ensured
▪ Incorporate computer forensics procedures into your approach to computer and network security to
ensure the integrity of the data
▪ These procedures help you capture necessary data in the event of a network breach
▪ Ensuring the viability and integrity of the captured data helps you prosecute the intruder
74
30
25/10/2024
89
90
31
25/10/2024
91
92
32
25/10/2024
93
94
33
25/10/2024
6. Basic scripting
99
100
34
25/10/2024
Script Syntax
101
102
35
25/10/2024
Linux
103
104
36
25/10/2024
105
106
37