beef_integration
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
beef_integration [2015/11/25 18:29] – lucy | beef_integration [2016/09/06 09:59] – lucy | ||
---|---|---|---|
Line 5: | Line 5: | ||
BeEF is short for The Browser Exploitation Framework. By using techniques similar to common drive-by Malware, testers can assess the security of a target’s internal environment, | BeEF is short for The Browser Exploitation Framework. By using techniques similar to common drive-by Malware, testers can assess the security of a target’s internal environment, | ||
Unlike other security frameworks, BeEF looks past the hardened network perimeter and client system, and examines exploitability within the context of the one open door: the web browser. | Unlike other security frameworks, BeEF looks past the hardened network perimeter and client system, and examines exploitability within the context of the one open door: the web browser. | ||
+ | |||
+ | |||
+ | ===== BeEF setup in LUCY ===== | ||
+ | |||
+ | As BeEF is running in the background of a phishing landing page it only will work in scenario' | ||
+ | |||
+ | To enable BeEF go into the Base Settings of the campaign, select the scenario in which you want to activate BeEF and then go to scenario settings. At the bottom you will find a checkbox "BeEF Information Gathering" | ||
+ | |||
+ | {{ beefmodulesii.png? | ||
+ | |||
+ | After LUCY 3.1 you will have the possibility to activate each single BeEF information Gathering module on its own. | ||
+ | |||
+ | {{ beefmodules.png? | ||
+ |
beef_integration.txt · Last modified: 2019/07/25 12:49 by 127.0.0.1