<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by K K Mookhey on Medium]]></title>
        <description><![CDATA[Stories by K K Mookhey on Medium]]></description>
        <link>https://medium.com/@kkmookhey?source=rss-8529ad781475------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*mRCaH3b-jbcSafeP.</url>
            <title>Stories by K K Mookhey on Medium</title>
            <link>https://medium.com/@kkmookhey?source=rss-8529ad781475------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:40:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kkmookhey/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Cybersecurity Career Guidance — Part 2 — the Intermediate Level]]></title>
            <link>https://medium.com/@kkmookhey/cybersecurity-career-guidance-part-2-the-intermediate-level-41c624e21f1c?source=rss-8529ad781475------2</link>
            <guid isPermaLink="false">https://medium.com/p/41c624e21f1c</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[K K Mookhey]]></dc:creator>
            <pubDate>Fri, 11 Sep 2020 13:36:43 GMT</pubDate>
            <atom:updated>2020-09-18T19:29:30.284Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cyber security Career Guidance — Part 2 — the Intermediate Level</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*haTOzBeDkg9yPqsOxf2PtQ.jpeg" /></figure><p>In <a href="https://medium.com/@kkmookhey/cyber-security-career-guidance-part-1-the-beginners-journey-a6781c97eab0?source=friends_link&amp;sk=243c00763779945e43531ca83c2c0b1b">Part 1</a> of this series, I wrote about how a beginner might want to approach the field of cybersecurity, and the knowledge and skills they should seek to acquire. In this article, I want to address the folks that have been working now for a couple of years and are seeking to get to the next level.</p><p>Typically, someone with 2 years of experience in cybersecurity would have spent most of those two years working in one of the following sub-domains:</p><p>1. Pen-testing</p><p>2. Advisory and/or audit</p><p>3. Security operations center</p><p>4. Digital forensics</p><p>At the 2-year stage, a key choice presents itself. Should you continue to specialize in the same field or should you look to diversify your interests. Either choice is valid and boils down to an individual’s own preference. In the next section, I lay out the pros and cons of either choice.</p><h3>Specialization vs. Generalization</h3><p>It may be the case that you are thoroughly enjoying your work within one of the four sub-domains listed above and would like to continue working in the same domain. If so, then you should ideally seek to get to the next level within the same sub-domain (see specific sections later in this article). You should also seek to acquire a well-recognized certification relevant to that sub-domain. The advantage of continuing to grow within the same domain are that you would soon be reaching a stage of expertise and this is always going to be a good thing, no matter where you go next.</p><p>Another alternate is to look to shift to a different sub-domain and spend a couple of years in that. Often, I have seen people with 2–3 years of experience hesitate to learn a different domain primarily from the fear of failure. Having done pen-testing work for a couple of years, it seems alien to now want to shift into compliance and audit related work. In my view, a generalist will eventually do better in their career than a specialist. The risk of being a super-specialist are that you may be left redundant when a tool is created that does the bulk of what you have been doing so far. By becoming a generalist, you not only de-risk your career being automated from under your feet, but also become more valuable as someone who can bring different perspectives to the larger domain of cybersecurity.</p><p>Someone who can evaluate a network diagram, review a firewall configuration, and audit a change management process, while being able to articulate the business risk from insecure firewall rules is a very valuable asset to any organization. Similarly, someone who is a forensics investigator but has had prior experience in pen-testing would be able to imagine an attacker’s modus operandi more easily than someone who does not know what the <a href="https://www.lockheedmartin.com/en-us/capabilities/cyber/cyber-kill-chain.html">cyber kill-chain</a> is or how <a href="https://en.wikipedia.org/wiki/Network_Lateral_Movement">lateral movement</a> takes place.</p><p>So, I think the key question to ask yourself is — are you resisting from expanding your portfolio because you are loving what you are doing, or because you are afraid to come out of your comfort zone. If the answer is that you absolutely love what you are doing, then read on.</p><h3>Career Progression</h3><p>In the next few sections, I list out the next steps you should seek to accomplish within each of the 4 sub-domains listed above.</p><h4>Pen-Tester to Red Teamer</h4><p>After a couple of years doing vulnerability assessments and penetration testing (VAPT) projects, you would have acquired a fair bit of skill in using the right tools, interpreting their results and using limited exploitation techniques to penetrate deeper into systems. You may even have, once in a while, gained Domain Admin access within the network you were testing. However, you would typically struggle to get that level of success within a hardened environment. Here’s a summary of where you should be at this stage and where you should aspire to get to in the next two years of your career:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K3gN2OfZL5FEN49daSe3BQ.png" /></figure><h4>Analyst to GRC Consultant</h4><p>If you have spent the first two years of your career in the compliance and advisory sub-domain then you have most likely done 20–30 engagements covering different frameworks such as ISO 27001:2013, HIPAA, PCI DSS, etc. It may be the case that you have joined a team or a company that specializes in one of these and most of your experience now is restricted to that domain, but now would be the time to expand your horizons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/881/1*Zq812khbKtaWEthg8gRTsA.png" /></figure><h3>SOC Analyst to SOC Manager</h3><p>Within a Security Operations Center, there are many different teams. There’s the security monitoring team consisting of L1 and L2 analysts, reporting into a Shift Lead. There’s the SIEM administration team that’s focused mainly on adding new log sources to the SIEM, building new use cases, etc. There’s a threat intelligence team that integrates multiple threat feeds, releases advisories, etc. An incident management team that investigates incidents, guide the IT teams to patch systems or block IP addresses, etc. and accordingly closes the reported incidents. There’s probably also a small automation team that continues to automate use cases and reports. I would strongly encourage all SOC team members to constantly seek to join these different teams or shadow their friends in the other teams and learn as much as they can. This will give them the ability to lead a larger SOC team within a Managed Security Service Provider or even head the SOC for a large organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/893/1*cpyBy74z65bq4XiRTd75aQ.png" /></figure><h3>Forensics Newbie to Expert Investigator</h3><p>Personally, I find security incident investigation to be one of the most fascinating aspects of cybersecurity. Having worked across the different sub-domains over the years, I still get fairly excited when one of our teams is digging deep into an interesting cyber attack. When starting out, you may either get involved in live forensics or offline forensics. Both are equally important, so don’t ignore one for the other. There are numerous circumstances where disk imaging and offline analysis are simply not feasible, and you have to use the right tools and techniques to conduct investigation on a live system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/861/1*nzoHpm8QM5QnC2RVghOhVA.png" /></figure><h3>General Areas of Improvement</h3><p>Besides the sub-domain specific areas listed above, the following are general areas in which you should have significantly improved yourself in the 2–5 years duration</p><p><strong>People skills.</strong> As you grow in your career, the mix between executing projects vs. managing people will continue to change. In the initial few years, you will be almost completely focused on executing projects. But from the 2nd and 3rd year onward, you will definitely get additional responsibilities to mentor new team members, lead teams, coordinate projects, etc. Most techies would resist this aspect, but you should be clear if you wish to be a single contributor for your entire career or you would like to take up the managerial responsibilities. Either ways, you must then communicate this to your management and ask to be given those types of roles. The large majority of organizations that you work in would not have the facility to allow you to continue working in a technical role without taking on any managerial responsibilities. So, make your decisions wisely as this can have long-lasting impact on your career. My 2 cents would be that for most of us it is best to start honing up our people skills and project management skills after the 2-year period, as this is what will help us move up the hierarchy.</p><p><strong>Report writing.</strong> Your reports by now should be concise, easy-to-understand, and have a logical flow. You should be able to draft very good Executive Summaries as well.</p><p><strong>Customer communication.</strong> Whether it is ongoing project-related communication or presenting the final reports, you should be able to do these with ease. One sign that your communication skills have improved is if you are able to deliver training programs on an advanced topic within your sub-domain.</p><p>In conclusion, whether you choose to stick to your sub-domain and specialize in it or you choose to switch sub-domains and become a generalist, you must be a student for life. And besides continuing to work on your technical knowledge and skills, it also becomes imperative that you improve on your non-technical skills as well. Finally, it is the team that carries the day through, and learning to work well within a team can potentially give you a higher level of success than being a solo performer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41c624e21f1c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cyber security Career Guidance — Part 1 — the Beginner’s Journey]]></title>
            <link>https://medium.com/@kkmookhey/cyber-security-career-guidance-part-1-the-beginners-journey-a6781c97eab0?source=rss-8529ad781475------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6781c97eab0</guid>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[certification]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[K K Mookhey]]></dc:creator>
            <pubDate>Thu, 03 Sep 2020 11:52:11 GMT</pubDate>
            <atom:updated>2020-09-17T20:07:37.119Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cyber security Career Guidance — Part 1 — the Beginner’s Journey</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0km5F_4OcJIwTqRg4KXIJw.jpeg" /></figure><p>One question that I frequently get asked is how should one go about building a career in cybersecurity? Having hired and overseen the careers of thousands of cybersecurity professionals at the <a href="https://www.niiconsulting.com/">company</a> I am the Founder &amp; CEO of, I thought I would jot down some ideas that may prove helpful to folks seeking to make their careers in this very exciting domain.</p><h3>Must-have Technical Knowledge and Skills</h3><p>I think a good understanding of the fundamental principles of networks, operating systems and databases is very important. Beginners should understand to a fair level the following concepts:</p><h4>Networks and Network Security</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BqsBSMdJ0GxK3LF1Av6ahw.jpeg" /></figure><p>1. <strong>TCP and UDP protocols</strong>, including how their headers look like and the functions of the different parts of these headers. For instance, if you don’t understand what is the TTL value, then you would not grasp <a href="http://users.cs.cf.ac.uk/Dave.Marshall/Internet/node77.html#:~:text=Trace%20Route%20works%20by%20setting,the%20machine%20one%20hop%20away.">how traceroute works</a> and why it doesn’t work in some networks. Similarly, without a good understanding of TCP flags, you would have a tough time figuring out how to get the most out of tools like <a href="https://nmap.org/">Nmap</a>.</p><p>2. IP, ICMP, DNS, ARP, RARP, FTP, and HTTP are some of the other <strong>important foundational protocols of the Internet</strong>. A strong know-how of how these protocols helps you get more out of various scanning tools and interpret their results more effectively.</p><p>3. A good book to get started is <a href="https://www.amazon.in/Computer-Networks-5e-5th-Tanenbaum/dp/9332518742">Computer Networks by Tanenbaum</a>. One of the other books that made me fall in love with networks and socket programming is <a href="https://en.wikipedia.org/wiki/UNIX_Network_Programming">UNIX Network Programming</a> by W. Richard Stevens, who also wrote the very popular <a href="https://www.amazon.in/TCP-Illustrated-Protocols-Addison-Wesley-Professional/dp/0201633469">TCP/IP Illustrated series</a>. I only did socket programming once as a paid assignment but learning how to do this can clear up so many concepts related to networking.</p><p>4. <strong>Network architecture</strong>. The ability to read and analyze a network diagram is very critical. The first time you look at a network diagram, it might seem overwhelming. My usual tactic is to simply ask the network administrator to walk me through the diagram. One of the easiest ways is to look for the Internet cloud in the diagram and then traverse your way to the core switch and then to the other links. Once you’ve done this a few times, it becomes fairly easy. All networks are built up from the same elements — firewalls, switches, routers, WANs, LANs, VLANs, etc.</p><p>5. <strong>Firewalls</strong>. The first firewall I played around with was <a href="https://en.wikipedia.org/wiki/Iptables">iptables</a> on Unix, which was later called <a href="https://en.wikipedia.org/wiki/Ipchains">ipchains</a>. Many commercial firewalls back in the day were built on top of ipchains. Nowadays, you not only have UTMs and Layer 7 firewalls, but also firewalling capability is present in the cloud via things like Amazon’s Virtual Private Cloud and Security Groups.</p><h4>Systems Security</h4><p>6. <strong>Windows</strong> knowledge is very important. Even if you love working on a Linux or a Mac system, many of the systems you’ll be attacking and securing would be Windows PCs and Windows servers. A good knowledge of startup programs, the structure of the Windows registry, services, users and groups, file system access control, the Event Viewer, etc., are very important.</p><p>7. <strong>Cleaning an infected system</strong> by hand is probably the best way to learn how malware infect a Windows system. Of course, you can do this only for low-tech malware, and not file-less memory-only malware. But doing this repeatedly can quickly help you understand many important concepts about Windows security</p><p>8. <strong>Unix </strong>is one of the most powerful operating systems and grasping important security concepts such as startup programs, connecting open ports to running processes (say using <em>lsof</em> or <em>netstat</em>), knowing log locations and log formats, pluggable authentication modules, bash history, etc. would go a long way in trying to attack Unix system or escalate privileges. This is also very helpful when investigating a hacked Unix system. My favorite Unix fundamentals and security book is <a href="https://www.amazon.in/Practical-Unix-Internet-Security-3e/dp/0596003234">Practical Unix and Internet Security</a>.</p><p>9. Among the popular databases — Oracle, Microsoft SQL Server, MySQL, etc. — I would suggest you play around with at least one of them. Again, numerous online and offline resources are available to learn the security principles of these technologies. <strong>Database security</strong> is one topic that tends to put off security professionals, but I feel it is one of the most important elements to be conversant with.</p><h4>Application Security</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cJb9LwqLlxmtSu7M3OAuvQ.jpeg" /></figure><p>10. The workings of web applications, basics of <a href="https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller">MVC frameworks</a>, utility of stuff like AngularJS, etc., is important if you’re going to be able to test and secure web applications. But don’t stop there, it would be a good idea to explore the building blocks of <strong>Android and iOS mobile apps</strong>. To really understand iOS apps, you might need a Mac, but that should definitely not stop you from learning as much as you can theoretically. There’s tons of material on the official Google and Apple sites dedicated to <a href="https://www.android.com/intl/en_in/security-center/">Android</a> and <a href="https://support.apple.com/en-in/guide/security/welcome/web">iOS</a> — including security how-to’s.</p><p>11. <strong>APIs and containers</strong>. With the world having moved to DevOps and micro-services architecture, it is an added advantage if you’re also conversant with the workings of APIs and containers and their security risks. Again, you need not be an expert here, but a fair bit of working knowledge would definitely go a long way.</p><p>12. The <a href="https://owasp.org/www-project-top-ten/"><strong>OWASP Top Ten Web Application Security Risks</strong></a> is also a non-negotiable element of your repertoire. Being able to explain each of the Top Ten issues would go a long way in setting you apart from the crowd. Being able to explain the mitigation measures for each of the issues would nearly seal the deal during an interview.</p><h4>Hacking Tools and Techniques</h4><p>So far, I have not emphasized on the hacking side of things. While, it is exciting to run tools like Nmap and SQLMap, it is far more important to understand how systems work. This will help you execute the right steps against the given target and analyze the output of your tools properly. It will also help you give the right recommendations to the client. So, once you have a decent grasp of the fundamentals, you should seek to now understand and have hands-on practice with:</p><p>13. <strong>Port scanning.</strong> Being conversant with Nmap and the various scanning options is a fundamental skill-set. A typical question sequence I use is as follows:</p><blockquote>a. Explain port-scanning?</blockquote><blockquote>b. How many ports will you scan against a given target?</blockquote><blockquote>c. Which tool would you use?</blockquote><blockquote>d. What type of scan options will you select, and why?</blockquote><p>If they’ve managed to answer correctly so far, I would ask:</p><blockquote>e. How does Nmap’s OS fingerprinting work? Can you explain with an example?</blockquote><p>A correct answer here would also demonstrate that you not only understand Nmap well, but you also have a fair idea of network fundamentals.</p><p>14. <strong>Application proxies</strong> like Burp Suite are the go-to tools for any application security tester. While, I would not expect a beginner to know all of the advanced capabilities of Burp Suite, but knowing how to set up a proxy, what is it used for, and how you might use it to test for say SQL Injection would be good.</p><h3>Good-to-have Technical Knowledge and Skills</h3><h4>Log Analysis</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IM1aUo6VVCcJ0B-wj6oV8w.jpeg" /></figure><p>Logs can seem overwhelming the first time you come across them. But all you must do is confront the bully head-on! In my training workshops, I always throw different log file formats on the screen and ask the students to analyze what’s going on. At first, there’s a typical sigh across the whole class, but soon people begin to interpret the different fields and what they could mean. There are numerous tools out there — some that support multiple log formats, others which do a great job at a specific log format. With experience, you will figure out which tool works best for which type of log format, but nothing beats being able to look at raw logs and not be intimidated.</p><h4>Malware Analysis</h4><p>As exotic as this topic sounds, the basics of analyzing any executable are not that difficult. I would not expect a fresher to be able to analyze disassembled code, but knowing how to run <a href="https://docs.microsoft.com/en-us/sysinternals/"><strong>Sysinternals</strong></a><strong> </strong>tools to monitor the behavior of an exe or even basic tools like <a href="https://www.winitor.com/">PEStudio</a> would be impressive coming from a beginner.</p><h4>Cloud Security</h4><p>I was debating whether I should keep cloud security in the optional section or not. I would suggest that firing up an AWS account might even be a good way to learn the fundamentals. Back in the day, we had to struggle to get a copy of and install say the Oracle database. Today, all you need is a credit card and you can fire up all sorts of operating systems and databases and other technologies up and running in a matter of minutes. And playing around with these technologies is really the best way to learn. No amount of reading will give you the confidence that trying out the commands and security steps will give you. Also, while you’re playing around in the cloud, you will also be able to understand various cloud security concepts, such as VPCs, Security Groups, S3 bucket security, etc.</p><h4>Programming</h4><p>This is a controversial subject within the security community. I would say, while it is not mandatory that you know a programming language, <strong>but it helps a lot</strong>. During the interview process, unless it is mentioned on your resume, I would not ask about your programming know-how. But from personal experience, I can vouch for the power of programming when solving real-world technical issues. Again, which language you know is not important. Even C is fine. Shell scripting is possibly even better. Python is awesome. In college, we were taught Basic and C. We taught ourselves C++ and Java on the side. After college, I used Visual Basic to create some of the early set of tools that would help us conduct security audits. I taught myself HTML and CSS when building the company’s first website. I also taught myself Perl because it seemed cool. And finally, a forensics project I did a few years back forced me to learn Unix shell scripting because the client would simply not let us install any tools to analyze the gigabytes of logs.</p><h3>Communication Skills</h3><p>You carried out an awesome pen-test, you got root on the company’s main eCommerce server, you got Domain Admin on their Active Directory, but when you presented your findings the final reaction in the room was ‘meh’. Yes, this has happened to me and it proves that while the quality of your work is very important, it is equally important to be able to present your findings in the right way. One common mistake that many security professionals make is to fill up their report with <strong>jargon </strong>such that only another security professional would be able to understand what’s going on, if that.</p><p>It is very important that you are able to articulate not only the details of the vulnerabilities you have found, but also their <strong>risks to the organization</strong>, how you found those vulnerabilities, and what are the <strong>appropriate recommendations</strong> to fix the issues. A recommendation for the Apache web server when the vulnerability was found in an IIS server is a common put-off. SQL injection mitigation measures that only talk about white-listing or black-listing, but not about using strongly typed parameters is another one. Reports that don’t have a management friendly executive summary are also problematic. <strong>Over-hyped or under-hyped</strong> articulation of risks undermines the excellent work you may have done.</p><p>Along with strong written and verbal communication skills, the ability to create decently formatted <strong>Word documents and PowerPoint presentations</strong> is also important. There are tons of resources online, and I would strongly advise you to spend time on these aspects as well.</p><p>Communication skills will also help you overcome challenges during project execution, interact positively with your peers and seniors in the company, and fast track your career progression.</p><h3>Analytical Skills</h3><p>If you’re not solving challenging problems as part of your job, you are soon about to become redundant. If running scans and copy-pasting results is your main job, I have sad news for you — a tool will take over your job shortly. To solve problems, you need to have strong analytics skills. I am not an expert in this field, and I don’t know how best one should go about building one’s analytical skills. But here are some helpful tips:</p><p>1. <strong>Listening</strong>. When a client is articulating the problem, the ability to simply listen, acknowledge what they are saying, take notes, jot down your questions, and await your turn to speak is a key skill. (secret tip: it also makes you appear more knowledgeable on the subject than you might be!)</p><p>2. Solving non-work-related problems on a regular basis helps hone your problem-solving muscles. Are you good at Sudoku or crossword puzzles? Then read no further sensei, you are already ahead of the curve.</p><p>3. <strong>Positing hypotheses</strong> and then testing them is the core of problem solving. This is the scientific method that we must apply to our work as well. Given a situation, what could be the possibilities. If you’re faced with a login page, what are the possible vulnerabilities that could exist. Those are hypotheses — or as we call them — test cases. Then you test each and see what the results are and note down your results. This systematic approach to testing an application is often ignored in lieu of the more exciting approach of throwing Nmap, Burp Suite scanner, SQL Map and the kitchen sink at the application.</p><p>4. The basic principle that behind every problem is a solution (and possibly multiple solutions), questioning all the baked-in assumptions and exploring unconventional hypotheses is very important. Again, you can teach yourself to become good at problem-solving. And with practice you also become better at it.</p><p>Having read all of this, it might scare you to think how long it would take to cover all of these topics to be able to ace your interview. My estimate is that even if you spent two weeks on each of the sub-topics under the must-have section, it still only requires about 28 weeks or about 6 months. Many of you would be able to get there much faster.</p><h3>Parting Thoughts</h3><h4>Bug Bounties</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kZkWFlITemsp3Rfp" /><figcaption>Photo by <a href="https://unsplash.com/@cliffordgatewood?utm_source=medium&amp;utm_medium=referral">Clifford Photography</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Before we conclude, I would also like to share my views on bug bounties. Should you participate in these programs? Sure, go ahead. All practice is good. Are they a serious career option? Absolutely not. Do not get enamored by the few success stories you read on social media; for the majority of people, bug bounties can at best be a hobby or a side income. If during the interview your claim to fame is that you found XSS vulnerabilities in some Content Management System that no one has heard about, it won’t impress me much.</p><h4>Certifications</h4><p>One key topic to cover is do you need to acquire certifications. Honestly, no. If I am interviewing you as a beginner, and you are able to demonstrate confidently your knowledge in the above topics and can clear the practical tests we conduct, the certifications won’t matter at all. You can always acquire them once you are earning a decent salary. So, don’t worry too much about certifications at this stage of your career.</p><h4>College Degree</h4><p>The final point I would like to address is your college degree. Do you need to have a degree in computer science or computer engineering to become good at cybersecurity? Absolutely not. I dropped out of college to start my firm, and thousands of cybersecurity experts come from a non-CS background, many even from a non-tech background. So do not let the lack of the right college degree ever make you think that you can’t make it in this industry. Focus on learning and practicing as much as you can — constantly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6781c97eab0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Powerful Business Insights From Humanitarian Aid Work]]></title>
            <link>https://medium.com/@kkmookhey/powerful-business-insights-from-humanitarian-aid-work-c7ef2d850b65?source=rss-8529ad781475------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7ef2d850b65</guid>
            <category><![CDATA[social-services]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[people]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[humanitarian]]></category>
            <dc:creator><![CDATA[K K Mookhey]]></dc:creator>
            <pubDate>Mon, 10 Aug 2020 19:21:13 GMT</pubDate>
            <atom:updated>2020-08-11T07:08:58.764Z</atom:updated>
            <content:encoded><![CDATA[<h3>Powerful Business Insights From Humanitarian Aid</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RArF6ZgXEA8cHFHVfENWmA.png" /></figure><p>In March 2020, I first ventured into the humanitarian sector by volunteering with a collective called <a href="https://twitter.com/HelpingHandsTwt">Helping Hands</a> in the aftermath of the <a href="https://en.wikipedia.org/wiki/2020_Delhi_riots">NE Delhi Riots</a>. Later, I also volunteered in Mumbai to respond to the <a href="https://www.dw.com/en/coronavirus-indias-lockdown-turning-into-humanitarian-crisis/a-53377588">humanitarian crisis</a> triggered as a result of the sudden lock-down announced in India. This work covered primarily two operations — <a href="https://www.khaanachahiye.com/">dry ration kits to </a>the poor as well as helping <a href="https://twitter.com/gharbhejo">migrant workers travel back</a> during the lock-down.</p><p>Having spent nearly 20 years as an entrepreneur, this experience has been nothing short of an eye-opener. In this article, I wanted to compare the people aspect of volunteer-driven social work versus a typical business environment and see what lessons we can draw for our businesses and our relationships with the people that work with us.</p><h3><strong>Organizational structure</strong></h3><blockquote>In any company that starts to reach some sort of scale, an organizational structure is very important. There are hierarchies, job descriptions, objectives, key responsibility areas, and so forth. In the humanitarian sector, I saw a complete lack of such a structure. And the most amazing part was that even in the absence of a job description, people came to the fore and did what had to be done at that point in time.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/717/1*LyzLufPY9FY-3ziBgOUZGQ.png" /><figcaption>Vishal doing his thing for the next train at Borivali station</figcaption></figure><p><strong>Case in point:</strong> The third train that we organized for migrant workers to go from Mumbai to Uttar Pradesh was going to be packed to capacity. We had used IVR, SMS and calling campaigns to build passenger lists and get people to the stations. But, I was quite anxious to see how would we manage the crowd and sift the genuine travelers (on our lists) from others who had come to the station anyway to try their luck. By the time I reached Bandra Terminus (the starting point of the journey), I saw crowds neatly queued up already. When I reached the start of the queue, one of our volunteers — <a href="https://www.facebook.com/actorvishallamba/?pageid=1138224729646136&amp;ftentidentifier=2013664342102166&amp;padding=0">Vishal Lamba</a> — had already put in place a system where hand-written chits were being given to people who had our SMS and these groups had then been moved into a separate enclosure. Within the next half an hour, he had completed this process and updated us with the exact count of passengers who had received our confirmation SMS. Since this same train was also going to pick up hundreds of passengers at another station (Vasai), we were able to manage the crowds at both ends and ensure that passengers were properly on-boarded. It turned out Vishal had years of experience in event management. No one asked him to do this, nor did he have any written job description. He simply saw the situation and applied his experience and skills to the task at hand. This process then became our standard operating procedure for all the trains that we organized.</p><h3><strong>Working hours</strong></h3><blockquote>In corporate life, we are used to 9-to-5 or some sort of a fixed working hours schedule. Working additional hours is considered a rarity and working over weekends even more so. In the humanitarian sector, I cannot recall a single instance where any volunteer said they were not available because it was the weekend.</blockquote><p><strong>Case in point:</strong> One memorable day was when there was unseasonal rain in Delhi. One of the largest riot relief camps was set up in the massive courtyard of a mosque — Idgah. The tents got flooded and the mattresses on the floor got wet. People were naturally upset and worried about falling sick if the rains continued through the night. Upon receiving an SOS for 500 folding beds, one of our team members started calling suppliers who could supply these on the same day and in bulk. Once we found the supplier, we needed a volunteer to reach them and travel with the trucks to Idgah. It was already late evening, but two volunteers stepped up to the task. They drove nearly 40 kilometres from their homes in South Delhi to Rohini, and then escorted the trucks another 25 kilometres to the Idgah camp in North East Delhi. <a href="https://twitter.com/HelpingHandsTwt/status/1235979835182329860?s=20">They ensured the beds were unloaded and properly delivered</a> into the camp even though it was way past midnight by that time. This won <a href="https://twitter.com/abhinandita_m/status/1236173983910895616?s=20">kudos from the Delhi government also</a>.</p><h3><strong>Job descriptions</strong></h3><blockquote>People stepping out of their comfort zones or doing things that are not in their job description is again a welcome rarity in the corporate world. However, in disaster relief work, nearly everyone who got involved was facing new and unprecedented challenges.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HQJqHKUn07f74bSezBxj7Q.png" /><figcaption>Homes and shops burnt down in NE Delhi</figcaption></figure><p><strong>Case in point:</strong> One of the areas where riot victims needed help was in getting cooking gas cylinders. With their homes completely destroyed — often by rioters using these very cylinders to blast homes and shops — they figured that if they had gas cylinders they could at least return back to their homes and set up their kitchens. One of the volunteers, <a href="https://twitter.com/Pallavi_Dhody">Pallavi Dhody</a> figured out the process, put up a desk in one of the localities, got people to fill up the necessary forms, collected their Aaadhar card details, contacted the gas agencies — all in one day. By the next day, <a href="https://twitter.com/HelpingHandsTwt/status/1237783535722926080?s=20">gas cylinders started getting delivered</a> and the dry ration kits that we were supplying could actually be put to good use. And to some extent I hope they got a sense of normalcy back by at least cooking their own meals. Now, she did not say, it is not my job, or I am not sure how to go about doing this. She saw a problem, called a few people, figured out the solution and got the job done.</p><h3><strong>Standard Operating Procedures</strong></h3><blockquote>As an organization grows and people come and go, it becomes important to start documenting critical processes. This helps with standardization but can also lead to bureaucratization of work. I did try to document our SOPs, but they changed on an almost everyday basis. It was definitely very challenging to run operations where the ground reality changed so frequently. And this required team members to show a lot of flexibility in adapting to the changing circumstances.</blockquote><p><strong>Case in point: </strong>In the initial few days of running relief operations in riot-affected NE Delhi, local transportation was unavailable as autos and taxis refused to ferry social workers and relief material into the worst-affected areas. We hired two vans from these localities to help ply people and material to the people who needed it most. Eventually, we hire a larger tempo as we had to transport food packets. These three vehicles became a mainstay of our logistics operations. As the COVID-19 situation worsened, the warehouse we were using to store bulk grains and package these into family-sized ration kits shut down. We then transitioned to helping people procure essential groceries from local stores and began paying the store owners using digital wallets.</p><h3>Succession Plans</h3><p>In a company, we spend a lot of time agonizing over succession plans, identifying key management personnel, even taking specific insurance covers for them. For many of our key people, we cannot imagine how that department would function in their absence. In smaller companies, the exit of a key person can handicap an entire operation, impact revenues and reduce profits.</p><p>Case in point: In humanitarian aid, it was quite the opposite. Every operation had some key people, but even when they stepped away, others readily stepped in and took on the mantle. During the NE Delhi relief work there were days when I was handling 100s of phone calls, was a part of innumerable WhatsApp groups. And then when I decided to take backseat, within one day, the entire operation had been taken over by other volunteers who very likely did an even better job than me. The same thing has happened with Ghar Bhejo operations as <a href="https://www.linkedin.com/in/ashma-gupta-8ab34b60/?originalSubdomain=in">Ashma</a>, <a href="https://twitter.com/GovindAgarwal_">Govind</a>, Vishal and others have taken it over.</p><h3><strong>No parallels</strong></h3><p>There is one aspect though that I don’t think has parallels in the corporate environment. Volunteers often did what was needed to be done even if it meant a risk to their personal safety. I remember the night before <a href="https://en.wikipedia.org/wiki/Holi">Holi</a>, there were rumors on WhatsApp groups that people belonging to the majority religion would be taking out loud and boisterous processions through minority-dominated localities. The Delhi Police warned all NGOs to have no volunteers on the ground on the day of the festival. There were about 1000 people that we had been providing cooked food to. So, we decided to procure non-perishable food items (bread loaves, biscuits, fruits, etc.) and delivery them the night before. By the time these emergency purchases had been made, it was close to midnight and a curfew had been imposed throughout the area. Our volunteers set out in the dark of the night on scooters and in autos to get these food items to the people. There was a real risk to them, and we remained in constant touch with them till the deliveries were done and they reached their homes. These sorts of situations would be extremely rare in the corporate world but were commonplace in relief work.</p><h3>Insights for our work and our businesses</h3><p>While humanitarian aid — typified by the urgency to take actions needed to save people’s lives — is quite different in nature from a business environment, yet there might be insights we can gain from this experience:</p><ol><li>When people come together for a shared purpose and believe that they are doing things that go beyond their immediate needs (ref <a href="https://en.wikipedia.org/wiki/Maslow&#39;s_hierarchy_of_needs">Maslow’s hierarchy</a>), then great things can happen.</li><li>Ego is truly the enemy. The most successful interventions were those where individuals kept their egos aside and worked for the common cause. Where there was a lot of jostling for credit, it did sour the experience.</li><li>Adam Grant explains in <a href="https://www.amazon.in/Give-Take-Helping-Others-Success/dp/1780224729/ref=sxts_sxwds-bia-wc-nc-drs1_0?cv_ct_cx=give+and+take&amp;dchild=1&amp;keywords=give+and+take&amp;pd_rd_i=1780224729&amp;pd_rd_r=171709ed-e2ab-48d0-9121-d17ac7961c3d&amp;pd_rd_w=GoQAG&amp;pd_rd_wg=QXNA3&amp;pf_rd_p=f0c2150d-89bf-44f5-9aab-a971a58a11aa&amp;pf_rd_r=P3Y3P0DTKAY8F41Y6KRN&amp;psc=1&amp;qid=1596917903&amp;sr=1-1-71bd35eb-fa42-45ae-bc3c-4020570d5e67">Give and Take</a> that burn-out when giving is prevented when you can see the impact of what you were doing. Here, we were able to see the impact immediately. The smiles on people’s faces when they got the ticket to board the train back home. The relief when people got food, essential groceries, medicines, clothes, and school kits for their kids.</li><li>The joy of working with like-minded people makes a big difference. This type of work attracts people who have very similar principles and ethics. For me personally, this was the biggest positive of the whole experience so far. I met so many amazing people through this journey and enjoyed working with them on each of the campaigns.</li><li>The novelty of the work is also very interesting. As every day was a new challenge, and each initiative involved overcoming different obstacles, it really pushed all of us outside our comfort zones. But we knew that each of us had the other’s back. And this gave us the confidence to say, yeah let’s do this.</li></ol><p>Having said that, I look back at this entire experience and am reminded of the <a href="https://csl.ku.edu/sites/csl.ku.edu/files/docs/ECP_SavingBabies.pdf">Parable of Babies in the River</a>. There is so much more that needs to be done at a policy and framework level to address these problems systemically.</p><p>PS: My sincere apologies to the hundreds of people who I haven’t mentioned. They inducted me into this field, guided and mentored me, and all of those who stood shoulder by shoulder with each other and helped achieve nothing short of miracles.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7ef2d850b65" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Work from home diaries]]></title>
            <link>https://medium.com/@kkmookhey/the-work-from-home-diaries-ab396f0f0872?source=rss-8529ad781475------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab396f0f0872</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[work-from-home]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[business-continuity]]></category>
            <dc:creator><![CDATA[K K Mookhey]]></dc:creator>
            <pubDate>Tue, 24 Mar 2020 08:55:38 GMT</pubDate>
            <atom:updated>2020-03-24T08:55:38.034Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6JEZgZaMSnly_u5m" /><figcaption>Photo by <a href="https://unsplash.com/@thoughtcatalog?utm_source=medium&amp;utm_medium=referral">Thought Catalog</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This is a chronicle of how we planned and enabled work from home for 600 of our staff working around the world. There’s also comparative timeline of the number of Covid-19 infections in India and the steps we undertook as the infection spread wider. But first, a bit about us. <a href="https://www.niiconsulting.com/">Network Intelligence</a> is a cybersecurity firm founded in 2001. We grew from a single-person company to nearly 600 people working in offices in India and the Middle East, with consultants also onsite for projects in Asia Pacific and other regions of the world. Here’s the story of how we responded to the COVID-19 situation as it started to impact our countries of operation.</p><h3>3rd March</h3><p><em>Number of infections: 9</em></p><p>We had our first COVID-19 response team meeting to discuss the COVID-19 situation. This consisted of the senior leadership team and one senior representative from the business continuity and project management team.</p><p>The main outcome of this was to build a project-by-project and employee-by-employee tracker and tag against these which of them could work from home and which ones would not be able to because of client or technical dependencies. We were still looking at only a partial WFH situation at that time.</p><p>HR started sending out regular emails to employees on washing hands, staying home in the event of a cold, etc.</p><h3>4th March</h3><p><em>Number of infections: 32</em></p><p>First communication to all the employees assuring them that we were on top of the situation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/1*LIfTvSefWLfjZTtPZoh7XA.png" /></figure><p>Eventually, there would be nearly a dozen emails from me to the entire company on the process.</p><h3>Date: 5th March</h3><p><em>Number of infections: 33</em></p><p>The project-wise and employee-wise tracker from the previous meeting was ready and another list of various action items was prepared and responsibilities allocated. Another call was held to go over these projects, and we decided that we would treat offsite and onsite projects separately and develop different plans for these two types of projects. Further, for the onsite projects we would explore different options for the milestone-based projects versus the staff augmentation projects.</p><h3>Date: 6th March</h3><p><em>Number of infections: 34</em></p><p>Another senior leadership meeting was held with all the department heads</p><p>We planned for 5 scenarios:</p><ol><li>Work from home enabled for some teams</li><li>Work from home enabled for all our teams, except those that were onsite</li><li>Some clients shut down; some projects cancelled</li><li>Entire cities in lock-down — we would have to be 100% WFH if this situation arose</li><li>Business significantly down, possibility of ceasing operations.</li></ol><p>We decided to plan thoroughly till stage 3; and leave stage 4 and 5 for later when the time came. As it turned out, stage 4 came fairly quickly.</p><p>Our major focus at this point was on the SOC (Security Operations Centre) operations as these are 24/7 and are governed by strict client SLAs.</p><p>One key decision we made was to begin partial WFH from the coming Monday — 9th March. The 10th of March was anyway going to be a holiday. So, the partial WFH on 9th March would give us some breathing time to recover on the holiday. On priority, the support teams (finance, IT, admin, HR, and PMO) were moved either completely or partially to WFH. Finance, some team members had to continue coming as we use an accounting software Tally which runs on the LAN and it not cloud-hosted.</p><p>Also, from the 6th March on wards, we instituted twice-a-day meetings and daily emails from me to the entire company on the status.</p><p>Mass email sent out to 100+ students undergoing classroom trainings at various centers informing them that we were taking steps and most likely would be moving all classes online.</p><h3>Date: 8th-9th March</h3><p><em>Number of infections: 50</em></p><p>We had 20+ employees attending a cybersecurity conference in Goa (Nullcon). We emailed all of them and asked them to be in a 7-day compulsory quarantine upon their return.</p><p>We made a list of all our overseas employees (whether on business trips or on personal trips) and determined their return dates. They were also emailed and asked to go into a 14-day quarantine.</p><p>An HR point person was appointed to call each of these people up every day and check up on their health and report back to us.</p><h3>Date: 10th March</h3><p><em>Number of infections: 65</em></p><p>WFH mandated for all Bengaluru employees. Later that night, we asked all Pune employees to also WFH</p><h3>Date: 11th March</h3><p><em>Number of infections: 65</em></p><p>All delivery teams who are not onsite, were asked to WFH. We pushed out a form for employees to share their concerns directly with me so that I could also get a bottom-up view of the situation.</p><p>We approved a small monthly allowance to all employees to upgrade their home Internet connections</p><p>Urged all employees to contact me directly if they had any concerns at all.</p><p>Email sent to the Board and our investors outlining worst case scenarios and our plans for each of these and soliciting their inputs.</p><p>Email sent to all students about moving classes online.</p><h3>Date: 12th March</h3><p><em>Number of infections: 77</em></p><p>Efforts on moving people to WFH continued. By this time our NOIDA office was also completely WFH. The major tasks that remained were:</p><p>- SOC in our two Mumbai offices as we had to ensure secured connectivity to the teams when moving to WFH</p><p>- Finance. We had found a vendor who would move our Tally to the cloud. This was approved and the process started</p><p>- Development team. While a lot of their systems were cloud-hosted, the big data setup of Elastic was in our server rooms. So secure remote connectivity had to be enabled. Also, we realized we were a few licenses short on VPN connections. This was resolved immediately.</p><p>Email sent to all customers informing them about the need to enable WFH for all our employees and that we were there to help in any way we could with no commercial angle to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/623/1*0F9-Y4GtS-tQdnrmyf08jA.png" /></figure><p>A general email sent to all employees</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/687/1*kKJU_0Ge_YFb03GQC-afKQ.png" /></figure><p>Another email was sent out later that day with some more inputs to the teams:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/726/1*xl5BZgkcODrWfB4i1cCaKw.png" /></figure><h3>Date: 13th March</h3><p><em>Number of infections: 85</em></p><p>We had achieved 100% WFH for our entire India staff working out of all 9 India offices — Mumbai, Thane, Pune, Bangalore, Hyderabad, Chandigarh, Delhi, NOIDA, Vizag.</p><p>One-to-one emails were now being sent to customers by our senior leadership team and me and a targeted outreach started to push our clients to enable WFH for our employees. We also began receiving panic emails from some onsite employees, and we kept a clear line of communication assuring them that their health was our top priority and we were pushing all our customers to enable WFH.</p><h3>14th — 19th March</h3><p><em>Number of infections: 100–198</em></p><p>On the 16th of March, we put up a survey link for each employee to directly inform us about their challenges when WFH. We also published detailed <a href="https://drive.google.com/file/d/1gq4TLQwhok_qntZ0-Op6kge86t0t3LWD/view?usp=sharing">WFH guidelines and a remote working security checklist for our teams</a>. You may feel free to use them within your organization with any modifications you see fit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*z3qVZsCQpbTLfYBypIBjSw.png" /></figure><p>Barring a few exceptions, all our clients had moved staff offline. All staff working on overseas projects had been flown back. We began calculating the financial impact of projects put on hold due to travel restrictions in order to present to the Board.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/686/1*2bC00E9Qq6OdXCOEQTukag.png" /></figure><h3>Lessons learnt and next steps:</h3><ul><li>Once the decision has been taken, then actions should be undertaken immediately; there really is no time to waste. The day I decided not to send my kids to school (10th March) was the day it was clear to me that all our teams had to be 100% WFH at the earliest.</li><li>Aligning the entire senior management team was the key to us being able to achieve 100% WFH with zero impact to customers.</li><li>Our IT teams worked day and night to get VPN connections going, admin teams arranged laptops for employees, cloud access was enabled for some of the apps. Maybe in the first few days, most people thought we were over-reacting, but when the state government started issuing orders to push private companies to WFH, the message was loud and clear, and everyone got on board.</li><li>Clear and constant communication is the key. People need to be assured that we are doing everything in our control to ensure their safety and well-being, irrespective of the financial costs.</li><li>We are using various technologies to constantly connect with our teams. For instance, we did our monthly townhall on Microsoft Teams, daily huddles/meetings are on Skype and Zoom, etc.</li><li>We are also undertaking a comprehensive security review of our own setup given the number of changes done to set up VPNs and remote access.</li></ul><h3>Conclusion</h3><p>This is an unprecedented global crisis. We and the people we know may fall ill; and a small number of them may not survive the illness. Businesses will be massively impacted, and jobs will be lost. Let’s all stay together and keep an eye out for those that are lesser privileged — the daily laborers, the Ola/Uber drivers, the housekeepers, and ensure they are able to sustain themselves and their families in the next few weeks and months. As business leaders, first and foremost are our employees and then come our customers. Revenues and profits are likely to be much lower this year than in the previous year. But if we survive, we can always rebuild our businesses and possibly do it better the second time round.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab396f0f0872" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>