13 hours 9 minutes
hello and welcome to another penetration testing execution. Standard discussion today were in part two of the rules of engagement. So to pick up where we left off will be discussing time of the day for testing, attack reporting, permission to test and legal considerations.
So with that in mind, let's jump right in
time of the day testing. This is where certain customers may require that testing be done outside of business hours and in some cases be limited to certain time frames after hours.
So Tom of Day requirements are something that need to be established with the client or customer
prior to ever starting the engagement. If there
peak hours for sales are 11 to 3 in during the day and they cannot experience downtown, and some components of your testing could cause downtown
that needs to be noted and you need to not test during those hours. If they can experience no downtown from 8 to 5, then you should do no testing from 8 to 5 very, very, very explicit parameters here that the client would provide. I've had clients that have said I only want you testing
from one in the morning, 1 a.m.
3 a.m. That's it. You get in that window of time to do testing. So I had to have a tester there
testing from one in the morning till three in the afternoon at the office.
And that just is what it is. We have to accommodate their schedules. And you know, the client
ultimately rules. And when they want that testing done, if we test outside of those parameters,
then we're not sticking within the rules of engagement or the permission to test memo that opens this up for issues. So keep that in mind
when you're coming through and in determining the time of day for the testing. If you set a vulnerability skin up to run it one in the morning, and it's only supposed to run from one this ring in the morning and it runs until five.
That testing has been conducted outside of that time of day requirement, so keep that in mind
now, attack reporting. This is specific to you as the tester and they as the client reporting your attacks.
And so this is appropriate, in some cases
for the Target's organization security team to not know when you are attacking so the responses can be recorded.
This needs to be discussed with the client at length,
and the primary point of contact should be aware.
And I would say that one person on security team, especially the manager of that team, should be made aware, should be made aware of the context of the test while the test is being done.
And, you know, one would hope that they would, you know, uh, continue to keep that information confidential so that the test integrity isn't invalidated. Now, if there's someone above them
who's given you permission to do this and they are allowed to accept the risk and they're allowed Thio speak on behalf of that team and make that decision fine, so be it. That will help again with test integrity.
But, um, you should not, um,
do so in secret.
As far as like keeping the point of contact in the dark unless they explicitly tell you to attack, reporting should be evaluated again on a case by case basis. With the clients. Keep back, it may not be appropriate
to keep them in the dark. In all cases, if you're doing something that's completely open air. There's no need to evaluate the response of the security team. They don't have a security team that makes no sense of that point to keep it a secret. So we tell them when we're testing, they could be aware of that. They could see that coming in on their systems and go yet. We knew that they were attacking today, and we knew it was gonna be at this time.
Now they may have 1/3 party
who manages, longs for the environment or has 1/3 party software that tells them when systems were attacked. And so if the client owns the hardware and the underlying systems and they're really just paying for 1/3 party to monitor this,
then they may not tell that third party, and they may want to see how long it takes for a ticket to be generated or response to be generated. So again,
case by case scenario on win,
you would need to inform the client that you're attacking and give them a kind of insight as to what is being done.
So we're not going to spend a huge amount of time on the permission to test memo. We've touched on many templates on and things that you could use for writing that out again. This memo provides you the permission to test outside of your contract the dates for testing the person's authorizing the test, general parameters of the test with any restrictions.
so again, this is your get out of jail free card.
So if it's not well laid out, if you're not one of the parties that's allowed to test if the person giving you permission to do the test is not the signature on this memo, and they're not the ones that are authorized to conduct or give you permission to conduct the tests, you need to be very, very cautious. This memo needs to be air tight,
especially if you're doing physical penetration testing
air tight, which you can do when you condone it, how you can do it. And if the person that is responsible for that facility ultimately has the ability to call the police on you and have you arrested, they need to be aware that the test is being conducted. They need to approve it, and they need to give you permission to do it. If anything is missing from that memo and you step outside of that,
you're running the risk of having legal issues. So keep that in mind that permission to test mammal is huge.
Now, we're gonna touch on legal considerations at a high level here. So it is best to remember that activities common to penetration testing may violate local laws, national laws. Whatever the case may be, check the legality of common tasks based on where the work will be performed and the location of the systems in question.
I don't care if the office is in,
uh, New York. If the systems are overseas in Europe, you need to take into consideration the laws for that area. It doesn't matter. Never take
anything for planet. Never take anything at face value trust, but verify all the time. An example of this would be
that if you're capturing void calls is a part of the test
depending on the area, it could be considered wiretapping, which is, you know, a lot of times illegal without specific permissions, and Moritz.
So you need to make sure that anything that you're going to do does not violate any local or national statutes. Always, always, always do your research. Always, always, always involved. Involved council when there are questions. Now, let's do a quick check on learning
which of the following is not one of the three concepts in regular status meetings. So we talked about three things.
Which one of these was not one of those three things?
All right, so
the right answers plans. Okay, What plans does the organization have was one of those progress was one of those problems was one of those places was not a component of those those regular status meeting concepts. So
next question, true or false? Regional laws and local laws are the same with regards to penetration testing.
So that's the question. Our regional laws
and local laws the same with regards to penetration testing. Well, the response there is that they are not. You should never consider regional laws and local laws as the same with respect to penetration testing.
All right, everyone. So in summary, we discussed time of the day for testing, attack, reporting, permission to test and legal considerations. With that in mind, I want to thank you for your time today. And I look forward to seeing you again soon.
Kali Linux Fundamentals
In this Kali Linux course you will learn about the industry standard tool for penetration ...
1 CEU/CPE Hours Available
Certificate of Completion Offered
How to Use SET (BSWR)
The Set or Social Engineers Toolkit is a commonly known open source framework available on ...
Certificate of Completion Offered