> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/prevention-tools/external-scan/common-questions.md).
# Common questions
Answers to the questions most often asked about the External Scan.
Is the External Scan a penetration test?
No. Here is the difference between the two.
### External Scan
* **Objective:** continuously map and monitor the exposure surface of a computer system.
* **Method:** automated and continuous. It looks at you from the internet, like an attacker would, without passwords, and identifies open ports, exposed services, and known vulnerabilities (CVEs) on assets visible from the internet.
* **Impact on the computer system:** non-intrusive; it does not attempt to exploit vulnerabilities. It is also unobtrusive; it does not disrupt existing systems.
### Penetration test
* **Objective:** produce a detailed report with attack scenarios and advanced recommendations.
* **Method:** performed manually (or semi-automated) by cybersecurity experts, generally on an ad-hoc basis (e.g., 1 to 2 times per year). The penetration test simulates real attacks to exploit vulnerabilities and test the resilience of your systems.
* **Impact on the IT system:** deeper, more intrusive.
{% hint style="info" %}
If you would like to perform a penetration test on your IT system, Stoïk can recommend trusted partners. Contact us at .
{% endhint %}
Why didn't the scan detect a vulnerability found by an audit or used in an incident?
The External Scan only checks for known vulnerabilities on what it can reach from the internet. It does not:
* see your internal network or anything behind a login
* analyze source code
* detect that a server has already been compromised
Penetration tests go deeper and can find things the External Scan cannot. If a known vulnerability was reachable from the internet and was not detected, contact with the asset, the CVE and the date.
Does MFA fix an exposed remote desktop portal?
No. Remote desktop (RDP) and RD Web Access portals are reported because anyone on the internet can reach them. MFA lowers the risk, but the finding stays until the portal is behind a VPN or no longer reachable from the internet. See [Resolve RDP service exposure](https://docs.stoik.io/cyber-best-practices/how-to-resolve-rdp-service-exposure-from-the-internet).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.stoik.io/prevention-tools/external-scan/common-questions.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.