Muhammad Waqar’s Post

**Why Fewer People Are Choosing to Become Network Engineers** I recently watched a thought-provoking video on the decline in interest in network engineering careers. Here's why, in my opinion, this field is losing its appeal: 1. **Comparative Appeal**: Network engineering seems less attractive compared to trending fields like cybersecurity, DevOps, and programming. 2. **Complexity and Knowledge**: The role requires deep knowledge of various protocols and platforms, making it more challenging and less enjoyable. 3. **Perceived Importance**: Networks work so seamlessly that their importance is often overlooked, but when issues arise, the consequences can be severe. 4. **Job Stress**: The high stress and demanding nature of the job can be significant deterrents. Staying ahead in tech means embracing change and evolving with the industry. What are your thoughts about this 💭 ? #TechCareers #NetworkEngineering #TechTrends #CareerDevelopment #Networks #Techtalks #Networking

Networking is a world of its own, until you enter the real world.

If you want to run a Modern SOC, the first book you should read isn't even about security. And it's free. It's this: https://lnkd.in/ewvbY4KV Teach yourself how to build systems, models, frameworks, processes that work to solve the security problem. You can't just hire 15 analysts, spend £1m on a fancy tech stack, and hope for the best anymore.

#Hiring a #computer #scientist or #engineer to support #nationalsecurity missions. Identify and mitigate #software vulnerabilities used in #defense, #energy, and critical infrastructure assets.

From Network Engineer to Security Pro: Mastering the Transition Learn why network engineers have a natural advantage when it comes to becoming security professionals. Discover how their strong foundation in networking lays the groundwork for success in the security field. Understand the importance of understanding network architecture and troubleshooting techniques in a security role. #NetworkEngineer #SecurityProfessional #MasteringTransition #NetworkKnowledge #TroubleshootingTechniques #NetworkingIssues #ITCareerPath #SecurityFoundation #DataFlow #NetworkArchitecture

Network engineering

What types of tabletop exercises are we building at Ally Security Inc? There are 3 main flavors: 1️⃣ Operational: For any role named in the IR plan, mainly centered around testing your incident response plan, procedures, or playbooks. Test your escalation paths, coordinate internal and external communications, and ensure your plan works for your org. If you're building your IR plan or overhauling it due to new people or processes, this is a good place to start! 2️⃣ Technical: For security engineers, SOC analysts, DevOps, and IT teams to walk through an incident and discuss how to handle various threat types. Activities focus on analyzing logs, discussing root causes, exploring containment options, and documenting evidence. 3️⃣ Executive: For senior management, boards, and non-technical audiences. Remove the jargon, focus on the business problems, risks, and how response choices affect the business. Set up your program to run them in the order above. Start by getting the plan right, then test it with more complex threats, and finally make sure the top layer of the org is involved. Then repeat.

🔥Must Read: 👇Microsoft Global IT Outage Lesson learned for Enterprise Architect, Global Governance Body , developer, tester and Business architect. Note: My view , my point 👇 **CrowdStrike Falcon sensor faulty deployment leads to MS Windows Blue Screen** CrowdStrike, a cybersecurity firm with thousands of customers globally, admitted on Friday that a defective software update caused a major IT outage, affecting airports, banks, hospitals, media outlets, and businesses worldwide. As an Enterprise Architect, I'm reflecting on the following considerations: - Was High Availability/Disaster Recovery (HA/DR) in place, at least in standby? - Was the User Acceptance Testing (UAT) report approved? - Who approved the change, and how was it managed? - Was there a change approval board (CAB) involved? - What were the Recovery Time Objective (RTO) and Recovery Point Objective (RPO)? - Was there a rollback mechanism in place? - Was the patch version tested in UAT before going to production? - Avoid deploying in production on a Friday (just kidding)! - While zero risk doesn't exist, was the acceptable risk defined? - Should consumers have the option for manual updates rather than forced ones, considering cybersecurity constraints? - Does the organization follow a multi-cloud strategy? - The company should share the Root Cause Analysis (RCA) publicly! - Every person who are using windows, need to learn how to reboot systems in fail safe mode - Was code pushed by Intern or skilled programmers? One line of code update made Global outage. This is the beauty of Software engineer or Cybersecurity engineer. 👇Your thoughts in the comment 👇. Let’s understand it. #Crowdstrike #microsoft #outage #shutdown #CyberSecurity #ITOutage #SoftwareUpdate #DisasterRecovery #ChangeManagement #RiskManagement #UAT #HighAvailability #MultiCloud #RootCauseAnalysis #TechLessons #SystemArchitecture #ITStrategy

Must Read 👇 . Please read it below and share it ! DM me or comment below if you have any questions.

We suffer from a 100+:1 outnumbering of developers to security, and we don't have enough butts in appsec/prodsec seats to do the job, by a long shot. There is also _definitely_ a budget gap, so we can't hire new butts into those seats. That means CISOs and other security leaders have to: * Reduce the likelihood of a successful attack by investing heavily in runtime protections * Limit the apps and findings we look at to only the most critical * Push more workload/responsibility to engineering Our human capital on the security side is just too precious to cover any significant portion of the portfolio or the issues we find. Great leaders find ways to inspire their teams when the odds are stacked against them, so we don't spend all day demoralizing our teams by lamenting this limitation, but the blindspots we have are galaxy-sized. Even if our leaders had their 2020 budgets, we'd still not be covering a significant portion of our enterprises. There's not enough budget, and there's also just not enough of those people to go around. We need AI product security engineers to fill the gap -- we always have, and we always will. You need your engineers to be able to self-serve on tool results by getting contextual feedback like this. If you're ready to scale your prodsec/appsec services to your whole portfolio, call Pixee.