Naijadevopsguy's Posts
Nairaland Forum › Naijadevopsguy's Profile › Naijadevopsguy's Posts
1 (of 1 pages)
Wealthyonos:What careers do you think will thrive in the AI world? |
FreeStuffsNG:Thank you |
sofeo:Php/Laravel, Nodejs, reactjs. I am in Lagos |
I am down and weak. Everyday I wake up I am exhausted because of when I look at the mistakes of my past and what I would have achieved if I had listened would have been much more better but it is done and there is nothing I can do about my past. I hate seeing mornings. I am tired even before going to work. I work as a software engineer but I am paid peanuts. I will drop my journey later. After so many years and nothing to show for it. Everyone I started with are doing pretty well. I am just in regrets and exhausted already. |
yesterday Laying down on my bed and pressing my phone after a while the kind of aroma coming from my neighbour's flat can quench the hunger of an angry man. I just check my account balance and compared it with the aroma and it was no where to be found. I just thought if I had a better opportunity. "Shey no be competition me and am for dey do now" but I no get power nah Please refer me to your company vacancies, jobs, gigs etc I do fullstack with devops Laravel, Reactjs, nodejs, docker, k8s, terraform, github ci, ansible, aws. I can also learn quickly any other skill to move the organization forward. |
Worked on an article Ultimate Guide: Securing Your Linux Server Like a Pro👏👏👏 Prerequisite A computer Internet connection A linux(ubuntu) server Objectives Secure a ubuntu linux server Checkout the article https://devsecops-blog.hashnode.dev/ultimate-guide-securing-your-linux-server-like-a-pro |
I pray and hope to get a connect that will land me a job that will pay me this amount by end of this year.
|
The Open Web Application Security Project (OWASP) Top 10 is a widely recognized guide that highlights the most significant security risks that developers and organizations must address to protect their applications. Here is a straightforward explanation to each risk: 1. Broken Access Control: Access control is all about ensuring that users can only access the data and functions they're allowed to. When this system fails it is known as Broken Access Control. 2. Cryptographic Failures: Cryptographic Failures refer to problems with how sensitive information is protected, especially when it's stored or transmitted. 3. Injection: Injection attacks occur when attackers send malicious data to a web application, tricking it into executing harmful commands. These attacks can result in significant data breaches, allowing attackers to steal, alter, or destroy important information stored within the system. 4. Insecure Design: Insecure Design refers to flaws in the design of a web application that make it inherently vulnerable to attacks. 5. Security Misconfiguration: Security Misconfiguration happens when web applications are set up with incorrect or weak security settings. 6. Vulnerable and Outdated Components: Using outdated or vulnerable components, such as software libraries, frameworks, or plugins, is a common risk in web applications. 7. Identification and Authentication Failures: Identification and Authentication Failures occur when there are issues with verifying a user's identity and managing their access to the application. 8. Software and Data Integrity Failures: This category focuses on ensuring the integrity of software and data, particularly during updates or within continuous integration/continuous deployment (CI/CD) pipelines. 9. Security Logging and Monitoring Failures: Security Logging and Monitoring Failures occur when web applications do not adequately log or monitor security-related events. Without proper logging, it can be challenging to detect and respond to security incidents, leaving the application vulnerable to ongoing attacks. 10. Server-Side Request Forgery (SSRF): Server-Side Request Forgery (SSRF) is a type of attack where a web application is tricked into making requests to unintended locations, often within the application's internal network. Credit: Security Trybe
|
1 (of 1 pages)
