|
|
xiii | |
About the author |
|
xv | |
|
1 Background of It and Cybersecurity Fields |
|
|
1 | (10) |
|
|
1 | (1) |
|
|
2 | (1) |
|
|
3 | (1) |
|
Where IT meets cybersecurity |
|
|
4 | (1) |
|
|
5 | (1) |
|
|
6 | (1) |
|
|
7 | (1) |
|
Major shifts in IT/cybersecurity |
|
|
8 | (1) |
|
|
9 | (2) |
|
2 Roles and responsibilities in IT |
|
|
11 | (18) |
|
|
11 | (1) |
|
|
12 | (2) |
|
|
14 | (2) |
|
|
16 | (2) |
|
|
18 | (2) |
|
Database administrator/data science |
|
|
20 | (2) |
|
Cloud administrator/engineer |
|
|
22 | (1) |
|
|
23 | (1) |
|
|
24 | (1) |
|
Operational technology engineer |
|
|
25 | (1) |
|
IT generalist vs IT specialist |
|
|
26 | (1) |
|
|
27 | (1) |
|
|
28 | (1) |
|
3 Roles and responsibilities in cybersecurity |
|
|
29 | (18) |
|
|
29 | (1) |
|
|
30 | (1) |
|
Security Assessors/Auditors |
|
|
31 | (2) |
|
|
33 | (1) |
|
|
34 | (1) |
|
|
35 | (1) |
|
|
36 | (1) |
|
|
37 | (1) |
|
|
38 | (2) |
|
Governance, risk, and compliance |
|
|
40 | (1) |
|
|
41 | (2) |
|
Threat intelligence analysts |
|
|
43 | (1) |
|
|
44 | (1) |
|
|
44 | (3) |
|
4 Where IT meets cybersecurity |
|
|
47 | (14) |
|
Technology meets cybersecurity |
|
|
47 | (1) |
|
People, process, and technology |
|
|
48 | (2) |
|
|
50 | (1) |
|
|
51 | (2) |
|
|
53 | (1) |
|
Legal and privacy concerns |
|
|
54 | (1) |
|
|
55 | (2) |
|
|
57 | (1) |
|
New IT I development projects |
|
|
58 | (1) |
|
Empathy in IT and cybersecurity |
|
|
59 | (1) |
|
|
60 | (1) |
|
|
60 | (1) |
|
5 The disconnect (IT vs cybersecurity) |
|
|
61 | (14) |
|
|
61 | (1) |
|
|
62 | (1) |
|
|
63 | (1) |
|
|
64 | (2) |
|
|
66 | (1) |
|
|
67 | (2) |
|
|
69 | (2) |
|
|
71 | (1) |
|
|
72 | (1) |
|
|
73 | (2) |
|
|
75 | (12) |
|
|
75 | (1) |
|
|
75 | (2) |
|
|
77 | (1) |
|
|
78 | (1) |
|
|
79 | (1) |
|
|
80 | (1) |
|
|
81 | (2) |
|
|
83 | (1) |
|
|
83 | (2) |
|
|
85 | (1) |
|
|
85 | (2) |
|
|
87 | (12) |
|
|
87 | (1) |
|
|
88 | (1) |
|
|
89 | (2) |
|
|
91 | (2) |
|
|
93 | (2) |
|
|
95 | (1) |
|
|
96 | (1) |
|
|
97 | (2) |
|
8 Financial issues and responsibilities |
|
|
99 | (18) |
|
|
99 | (1) |
|
|
100 | (2) |
|
|
102 | (1) |
|
|
103 | (1) |
|
|
104 | (1) |
|
|
105 | (1) |
|
|
106 | (2) |
|
|
108 | (2) |
|
|
110 | (1) |
|
|
111 | (1) |
|
|
112 | (1) |
|
|
113 | (2) |
|
|
115 | (2) |
|
9 Education gaps between IT and cybersecurity |
|
|
117 | (12) |
|
|
117 | (1) |
|
|
118 | (1) |
|
Cybersecurity certifications |
|
|
119 | (1) |
|
|
120 | (1) |
|
Cybersecurity higher education |
|
|
121 | (1) |
|
|
122 | (1) |
|
Cybersecurity training options |
|
|
123 | (1) |
|
Vendor-agnostic certifications |
|
|
124 | (1) |
|
Vendor-specific certifications |
|
|
124 | (2) |
|
|
126 | (1) |
|
|
127 | (2) |
|
10 Bridging the technology and cybersecurity gap |
|
|
129 | (12) |
|
|
129 | (1) |
|
|
130 | (1) |
|
|
131 | (1) |
|
|
132 | (1) |
|
|
133 | (1) |
|
|
134 | (1) |
|
Technical and practical meet |
|
|
135 | (1) |
|
Cybersecurity foundational knowledge |
|
|
136 | (1) |
|
|
137 | (1) |
|
|
138 | (3) |
|
11 Embracing functionality and security |
|
|
141 | (12) |
|
|
141 | (1) |
|
Functionality is not a four-letter word |
|
|
142 | (1) |
|
|
143 | (1) |
|
Problem-solving and decision-making |
|
|
144 | (1) |
|
Encouraging both operations and cybersecurity |
|
|
145 | (1) |
|
|
146 | (1) |
|
|
147 | (1) |
|
Understanding cognitive limitations |
|
|
148 | (1) |
|
Understanding personality types |
|
|
149 | (2) |
|
Our differences make our teams stronger |
|
|
151 | (1) |
|
|
152 | (1) |
|
|
153 | (10) |
|
Thinking outside current job descriptions |
|
|
153 | (1) |
|
|
154 | (1) |
|
New types of cybersecurity roles |
|
|
155 | (1) |
|
|
155 | (2) |
|
Cybersecurity operations liaison |
|
|
157 | (1) |
|
Incident response/operations specialist |
|
|
157 | (1) |
|
IT/cybersecurity cooperation working group |
|
|
158 | (1) |
|
Human factors security engineer |
|
|
159 | (1) |
|
Human factors IT specialist |
|
|
160 | (1) |
|
Cybersecurity EI (emotional intelligence) engineer |
|
|
161 | (1) |
|
|
162 | (1) |
|
13 Building trust and new relationships |
|
|
163 | (14) |
|
|
163 | (1) |
|
Getting rid of preconceived notions |
|
|
164 | (1) |
|
Approaching projects in a new way |
|
|
165 | (1) |
|
Early and often open communication |
|
|
166 | (1) |
|
|
167 | (1) |
|
Considering the other side |
|
|
168 | (1) |
|
Improve security and functionality |
|
|
169 | (1) |
|
Changing meeting structure |
|
|
170 | (1) |
|
|
171 | (2) |
|
|
173 | (1) |
|
|
174 | (3) |
|
|
177 | (20) |
|
|
177 | (1) |
|
Bridging the technical gap |
|
|
178 | (1) |
|
|
179 | (2) |
|
Behavioral analysis techniques |
|
|
181 | (1) |
|
Technology and security second |
|
|
182 | (1) |
|
Vertical and lateral changes |
|
|
183 | (1) |
|
|
184 | (2) |
|
|
186 | (2) |
|
|
188 | (7) |
|
|
195 | (1) |
|
|
196 | (1) |
Index |
|
197 | |