You need to see, feel the hooks on all fronts:
')
- Application vulnerabilities - here we need not only knowledge, but also flair. RCE, XSS, SQLinj, XXE, SSFR, CSRF, errors in loading files, alax / backround scripts (they are much more common than in main scripts). In my personal experience, here the scanner can spend an order of time longer than a manual check. Moreover, in recent times, “vulnerabilities from examples” are becoming less and less common, and localization is almost always needed.
- Vulnerabilities of services on the server - this is not very strong. A good example of this is the job with an unclosed mail server and the EXPN command.
- Attention to detail - sometimes one little thing can get rid of a couple of sleepless nights. Or dull, monotonous work.
- OSINT - measure seven times - cut once. Preparing for an attack / audit is no less important than the attack / audit itself. As was rightly said at the last PHD (in my free presentation) - you can immediately begin to attack and spend a week fighting windmills, or you can spend two days preparing, and find a subdomain vulnerable by the simplest vector, because him "no one knows (!)."
- The ability to investigate incidents - to see the consequences / consequences is not great task, to understand what led to them - this is where the true creativity. And good programmers with a bad temper are sometimes inventive to the horror.
- Knowledge in the field of cryptography - it is necessary to understand at least the basics of how to encrypt, how to decipher it, what algorithms can be considered persistent, which do not. What is worth wasting time on the reverse, and leaving what is left to the great-grandchildren, and even great-great-grandchildren.
- Knowledge of tools that make life easier: Backtrack or Kali are very helpful in this, everything is there to start, or rather, even to continue, you can get lost there at the start of your information security activities :). These two distributions can be used as a great Soviet encyclopedia. He opened, launched each tool, wondered which stones from his shoulders could be transferred to the computer. I did not understand what it is all about - I searched, read on the Internet. Understood the basics, looked for examples of use, examples of operation. I tried not only to exploit and get a list of databases, but also figured out the source codes and / or the coincidence that led to this.
- A collection of dictionaries / rainbow tables for brutus, attacks not the base of hashes - nowhere without them. Thank God, passwords in clear form are becoming less common. But without dictionaries, even the base of simple md5 can become a big obstacle. 100K hashes in Google is not vobsh. Here I advise you to deal with relatively new types of attacks - hybrid dictionary attacks, hybrid attacks on the most frequent character sets. Such attacks sometimes give stunning results.
- Social engineering is generally a separate volume of information security encyclopedia. I sent a letter - I compromised the machine with metaasploit - no ... do not do it :) But anyway, people and the result of their activity is the weakest link. Do not use them - insanely stupid.
- Knowledge of English is unconditional. Despite the fact that the Russian community is quite developed. And there is a large number of not only practitioners, but also theorists. We are only a part of the world, and a huge reservoir of knowledge is born by experts from other countries, and their results, workshops, PoC in English. You do not know English - you are definitely in the tail of knowledge.
Source: https://habr.com/ru/post/191108/
All Articles