Skip to content

Commit 4d588a6

Browse files
authoredJan 28, 2022
Fix spelling (OWASP#2049)
1 parent 44215ec commit 4d588a6

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed
 

‎Document/0x04b-Mobile-App-Security-Testing.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ In this guide, we cover mobile app security testing in two contexts. The first i
1313
Let's start by defining the concepts:
1414

1515
- **Black-box testing** is conducted without the tester's having any information about the app being tested. This process is sometimes called "zero-knowledge testing". The main purpose of this test is allowing the tester to behave like a real attacker in the sense of exploring possible uses for publicly available and discoverable information.
16-
- **White-box testing** (sometimes called "full knowledge testing") is the total opposite of black-box testing in the sense that the tester has full knowledge of the app. The knowledge may encompass source code, documentation, and diagrams. This approach allows much faster testing than black-box testing due to it's transparency and with the additional knowledge gained a tester can build much more sophisticated and granular test cases.
16+
- **White-box testing** (sometimes called "full knowledge testing") is the total opposite of black-box testing in the sense that the tester has full knowledge of the app. The knowledge may encompass source code, documentation, and diagrams. This approach allows much faster testing than black-box testing due to its transparency and with the additional knowledge gained a tester can build much more sophisticated and granular test cases.
1717
- **Gray-box testing** is all testing that falls in between the two aforementioned testing types: some information is provided to the tester (usually credentials only), and other information is intended to be discovered. This type of testing is an interesting compromise in the number of test cases, the cost, the speed, and the scope of testing. Gray-box testing is the most common kind of testing in the security industry.
1818

1919
We strongly advise that you request the source code so that you can use the testing time as efficiently as possible. The tester's code access obviously doesn't simulate an external attack, but it simplifies the identification of vulnerabilities by allowing the tester to verify every identified anomaly or suspicious behavior at the code level. A white-box test is the way to go if the app hasn't been tested before.

‎Document/0x04f-Testing-Network-Communication.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -284,7 +284,7 @@ If not already done, install the CA certificates in your mobile device which wil
284284

285285
#### Intercepting Traffic
286286

287-
Start using the app and trigger it's functions. You should see HTTP messages showing up in your interception proxy.
287+
Start using the app and trigger its functions. You should see HTTP messages showing up in your interception proxy.
288288

289289
> When using bettercap you need to activate "Support invisible proxying" in Proxy Tab / Options / Edit Interface
290290

0 commit comments

Comments
 (0)
Please sign in to comment.