I'm gonna hate Instagram app if it will take 10 seconds just in liking a single post, will not be a good UX for me.

#DSA | 🧵

As a non-techie, can you imagine that just writing code in an optimized way can save millions of dollars in computational costs for any organization on this planet?

Yes, it can and it is all possible with one of the powerful concepts of modern computer science: DSA

1/n

For any organization, its customers are the most important and no organization can compromise on the UX (Customer Experience) as it directly impacts the survival of any organization in the market.

2/n

As a software developer, the goal is never to change 5 + 2 = 7 but optimize it by decreasing any complexity. The speed and accuracy of the output are the key parameters that matter a lot to the best UX and they need to be maintained.

3/n

For maintenance, organizations can do one of two things: Invest more-n-more in Infrastructure (Resources) or let developers apply their most important skills "DSA".

4/4

READ COMPLETE HERE: https://www.shobhitsharma.net/article/pre-dsa-things-you-should-know-to-learn-code-optimization

#DSA #DataStructuresAndAlgorithms #SoftwareEngineering #Coding

Pre-DSA things you should know first to learn code optimization

The topic "DSA" is not a Rocket-Science but can do revolutionary things when implemented properly ‎️‍🔥‎️‍🔥‎️‍🔥

To learn DSA you need to first understand the following things 👇

- Understand how programs use computer memory to store data OR how computer memory stores data?

1/n

- Start with Array, just array; not any programming specific perspective, just understand what array looks like; for example:

ceoOfMNCs = ['Elon Musk', 'Tim Cook', 'Sundar Pichai']

2/n (a)

OR it's a simple list of CEOs of MNCs having Elon Musk, Tim Cook, & Sundar Pichai as three data elements.

2/n (b)

- Understand 4 basic operations of any data structure: Read, Search, Insert, Delete & understand how they relate to Computer Memory.

3/n

- Don't jump to the Big O Notation thing directly.

4/n

Let's understand Array 101 with our ceoOfMNCs example array:

- the foundational Data Structure and a list of elements.

5/n (a)

- the counts of the elements in the array begin with 0; So, for our example array ceoOfMNCs, the elements "Elon Musk" is at index 0, "Tim Cook" is at 1 & "Sundar Pichai" is at 2.

5/n (b)

- index of an array is the number that identifies where a piece of data lives inside the array.

5/n (c)

PRO-gramming Tips

Understand

- basics of programming like conditions, variables, loops, etc. (not any specific language, just concepts)

- what arguments you're taking as input parameters?

- what type and data you're returning?

6/n (a)

- steps / algo to perform operations or solve a problem.

- each step & statement like printing the value, comparison, etc. & debug so that you can seriously understand what's going on in the code you're writing.

6/6 (b)

It isn't enough knowledge but I can share a lot with you

Follow 👉 Shobhit Sharma @ScriptKKiddie for more updates on #Technology

#ScriptKKiddie #DSA #Programming #SoftwareEngineer

You can read the unrolled version of this thread here: https://typefully.com/ScriptKKiddie/yltjMzu

DSA is not a Rocket-Science

Top ProjectDiscovery (@pdiscoveryio) Tools for Bug Hunting 🔝

The THREAD 🧵 | #BugBountyTips 

Nuclei - Fast and customizable vulnerability scanner based on simple YAML-based DSL.
https://github.com/projectdiscovery/nuclei

Subfinder - Subdomain discovery tool that discovers valid subdomains for websites. Designed as a passive framework to be useful for bug bounties and safe for penetration testing.
https://github.com/projectdiscovery/subfinder

httpx - Fast and multi-purpose HTTP toolkit allows to run multiple probers using retryablehttp library, it is designed to maintain the result reliability with increased threads.
https://github.com/projectdiscovery/httpx

naabu - Fast port scanner is written in go with a focus on reliability and simplicity. Designed to be used in combination with other tools for attack surface discovery in bug bounties and pentests.
https://github.com/projectdiscovery/naabu

dnsx - Fast and multi-purpose DNS toolkit allows running multiple DNS queries of your choice with a list of user-supplied resolvers. 
https://github.com/projectdiscovery/dnsx

Check out ProjectDiscovery's GitHub Profile
https://github.com/projectdiscovery 

#Pentesting #WebHacking #BugBounty #Cybersecurity 

Follow 👉 @ScriptKKiddie for more Technology, Security & Open-Source Threads & Resources. #ScriptKKiddie

You can read the unrolled version of this thread here: https://typefully.com/ScriptKKiddie/Zn558Ga

Top ProjectDiscovery Tools for Bug Hunting 🔝

The OWASP Top 10 2021 🔝🔟

The THREAD 🧵 | #OWASPTop10 

What's changed in the Top 10 for 2021

There are three new categories, four categories with naming and scoping changes, and some consolidation in the Top 10 for 2021.



• A01:2021-Broken Access Control https://owasp.org/Top10/A01_2021-Broken_Access_Control/ moves up from the fifth position to the category with the most serious web application security risk; the contributed data indicates that on average,... (1/2)

... 3.81% of applications tested had one or more Common Weakness Enumerations (CWEs) with more than 318k occurrences of CWEs in this risk category. The 34 CWEs mapped to Broken Access Control had more occurrences in applications than any other category. (2/2)

• A02:2021-Cryptographic Failures https://owasp.org/Top10/A02_2021-Cryptographic_Failures/ shifts up one position to #2, previously known as A3:2017-Sensitive Data Exposure, which was a broad symptom rather than a root cause.... (1/2)

... The renewed name focuses on failures related to cryptography as it has been implicitly before. This category often leads to sensitive data exposure or system compromise. (2/2)

• A03:2021-Injection https://owasp.org/Top10/A03_2021-Injection/ slides down to the third position. 94% of the applications were tested for some form of injection with a max incidence rate of 19%,... (1/2) 

... an average incidence rate of 3.37%, and the 33 CWEs mapped into this category have the second most occurrences in applications with 274k occurrences. Cross-site Scripting is now part of this category in this edition. (2/2)

• A04:2021-Insecure Design https://owasp.org/Top10/A04_2021-Insecure_Design/ is a new category for 2021, with a focus on risks related to design flaws. If we genuinely want to "move left" as an industry, we need more threat modeling, secure design patterns, and principles,... (1/2)

... and reference architectures. An insecure design cannot be fixed by a perfect implementation as by definition, needed security controls were never created to defend against specific attacks. (2/2)

• A05:2021-Security Misconfiguration https://owasp.org/Top10/A05_2021-Security_Misconfiguration/ moves up from #6 in the previous edition; 90% of applications were tested for some form of misconfiguration, with an average incidence rate of 4.5%,... (1/2)

... and over 208k occurrences of CWEs mapped to this risk category. With more shifts into highly configurable software, it's not surprising to see this category move up. The former category for A4:2017-XML External Entities (XXE) is now part of this risk category. (2/2)

• A06:2021-Vulnerable and Outdated Components https://owasp.org/Top10/A06_2021-Vulnerable_and_Outdated_Components/ was previously titled Using Components with Known Vulnerabilities and is #2 in the Top 10 community survey, but also had enough data to make the Top 10 via data analysis. This category moves up... (1/2)

... from #9 in 2017 and is a known issue that we struggle to test and assess risk. It is the only category not to have any Common Vulnerability and Exposures (CVEs) mapped to the included CWEs, so a default exploit and impact weights of 5.0 are factored into their scores. (2/2)

• A07:2021-Identification and Authentication Failures https://owasp.org/Top10/A07_2021-Identification_and_Authentication_Failures/ has previously Broken Authentication and is sliding down from the second position, and now includes CWEs that are more related to identification failures.... (1/2) 

... This category is still an integral part of the Top 10, but the increased availability of standardized frameworks seems to be helping. (2/2)

• A08:2021-Software and Data Integrity Failures https://owasp.org/Top10/A08_2021-Software_and_Data_Integrity_Failures/ is a new category for 2021, focusing on making assumptions related to software updates, critical data, and CI/CD pipelines without verifying integrity.... (1/2)

... One of the highest weighted impacts from Common Vulnerability and Exposures/Common Vulnerability Scoring System (CVE/CVSS) data mapped to the 10 CWEs in this category. A8:2017-Insecure Deserialization is now a part of this larger category. (2/2)

• A09:2021-Security Logging and Monitoring Failures https://owasp.org/Top10/A09_2021-Security_Logging_and_Monitoring_Failures/ was previously A10:2017-Insufficient Logging & Monitoring and is added from the Top 10 community survey (#3), moving up from #10 previously.... (1/2)

... This category is expanded to include more types of failures, is challenging to test for, and isn't well represented in the CVE/CVSS data. However, failures in this category can directly impact visibility, incident alerting, and forensics. (2/2)

• A10:2021-Server-Side Request Forgery https://owasp.org/Top10/A10_2021-Server-Side_Request_Forgery_%28SSRF%29/ is added from the Top 10 community survey (#1). The data shows a relatively low incidence rate with above-average testing coverage, along with above-average ratings for Exploit and Impact potential.... (1/2)

... This category represents the scenario where the security community members are telling us this is important, even though it's not illustrated in the data at this time. (2/2)

This is the latest installment of the OWASP Top 10! #OWASP #Top10 #Web 

Follow @ScriptKKiddie for more Technology, Security & Open-Source  Threads & Resources. #ScriptKKiddie 

The OWASP Top 10  2021

That 9️⃣9️⃣9️⃣ Failure — The Eternal Experience

THREAD 🧵

Experience what? For many of all the population, experience is

“I love to cook, and I’m having years of cooking experience!”

I love to play games, I’m playing for a long time.

I have to work as a waiter as I need to support my family economically, I’m working for many years.

Love to play games or have to work as a waiter, In both of the sentences, we’re gaining the experiences.

I’m failing for a long time in achieving expertise in something! Failing for a long time in achieving?

If expertise is not achieved, did I achieve any experience yet?

READ ORIGINAL: https://scriptkkiddie.medium.com/that-999-failure-the-eternal-experience-38afaf069e21

#scriptkkiddie #shobhitsharma