7 hours 1 minute
Welcome to the end map lesson on timing and performance.
At first glance, this lesson may seem like an unimportant at Aunt RN MAPP training Siri's, but I think you'll find that making use of and maps, timing and performance options can really help you in two key ways. First, that can help you tweak your scan so they provide you with intended results very quickly.
And second, it can help you to adjust timing and performance of scans and their probes in such a way that they can evade detection from intrusion detection systems.
I'm sure you can see the value of that functionality.
Let's get started.
Here are the learning objectives for this lesson.
First, I'll give you an overview of and maps performance related issues.
Next, we'll discuss some basic techniques to improve the performance of N map scans.
Then we'll talk about and maps built in timing templates and finally will run through some fine grain timing control options.
Let's talk about some General and Matt performance considerations.
First, I need to mention that performance is and always has been a big priority for M APP developers with every default scan that you run in and map. The developers have tried to take into consideration both speed and accuracy,
you can feel reasonably certain that even when timing options air not set, then map developers have tried their best to provide you with great performance. With that said, though, they've also set out to provide the user with accurate results. In general, the's to stated goals may sometimes be at odds with one another.
Additionally, scanning large networks with default scans can become slow. For example, it is certainly possible to run a default and maps can against a slash 16 network. But leaving all timing options at their default value will probably take a really long time to provide you with the information you really care about.
Several obvious ways to deal with this are to scan smaller network segments at a time,
limit the number of ports or probes toe only those that are important to you or fine tune timing and performance options like the ones provided to you in the rest of this lesson.
There are several types of scans that are pretty slow in almost every case,
even when you do a just timing options. For example, UDP scanning and version detection scans.
When you run these types of scans, take some of the things I mentioned into account
if the information they provide really doesn't align with your goals, just leave them out entirely.
Also, firewalls with response rate limiting can slow down scans. So when you determine that some of your targets are either firewalls or sitting on the other side of a firewall, you should either be willing to wait to get your scan results or should adjust timing options in such a way that the firewalls response rate limiting
is not activated.
One really powerful tool that end map uses by default is parallelism and advanced algorithms to speed up scans. This basically means that N map can send out multiple probes to multiple hosts at the same time.
Then it can dynamically calculate the best way to adjust its timing options in order to both retrieve results quickly and accurately.
The point here is that sometimes it is best to similar. Simply allow any map to make adjustments to it, scans dynamically and skip manual adjustments to timing altogether.
Ultimately, and Matt places performance optimization in the hands of the user, though,
you can feel confident that performance and accuracy are at the heart of them. ABS default scans. However, sometimes performance may be more important to you than extreme accuracy.
And the opposite is also true. Sometimes accuracy of results and the desire to be very quiet from a scanning perspective, maybe the most important.
The rest of this lesson will be devoted to helping you learn how to make those adjustments based on your goals.
Great. Mm. Scanning in that map is a result of careful scan construction that takes into account your goals and your time constraints.
Here are the most basic things you should consider regarding timing and performance and then map
first. Like I mentioned before and will probably mention again, Start with a clear goal with every one of your end map scans. Ask yourself, What information do I need to know? How important is 100% accuracy, and how fast do I need it?
leave out unnecessary tests. For example, if you don't really care about you, dp ports or if you don't need service, an application versions at the moment of your scan.
Just leave those things out since they have very clear performance ramifications.
Also, consider adjusting the ports you're interested in
by scanning using the DASH P Command line switch.
Remember that a default and maps camel scan 1000 ports, simply adding the dash capital. F option will drop that down to 100.
But if you're only interested in TCP ports 2123 25 80 then use the DASH P switch to make that change.
Third, ensure you have the latest version of en map,
though in map has been around and has been adjusted as network, the network landscape has changed. Enhancements are made very often. I'd suggest that you check your version of an map about once a month using the Dash Capital V command line switch, then compare it to the most recent stable release on maps website.
Upgrade when you can. After all, it's free.
And finally, when it makes sense, consider optimizing timing and performance parameters.
So let's talk about that