Skip to content

Latest commit

 

History

History
109 lines (62 loc) · 7.33 KB

Setting_up_vbox.md

File metadata and controls

109 lines (62 loc) · 7.33 KB
Raw

This will instruct on how to install virtual box along with oracle extension. I will also include kali/metasploitable machines installation guide here. NOTE: DONT BE SILLY USE SCREENSHOTS!!!!!!!!!!!

WARNING: Some Vulnerable machines if misconfigured can be left open to the public wich may result in network compromise.

INSTALLING

Visit https://www.virtualbox.org/wiki/Downloads to download the most current version. I would also advise installing the oracle extension pack as-well. The extension pack provides the following added functionality:

  • VirtualBox Remote Desktop Protocol (VRDP) support. See Section 7.1, “Remote Display (VRDP Support)”.

  • Host webcam passthrough. See Section 9.5, “Webcam Passthrough”.

  • Intel PXE boot ROM.

  • Disk image encryption with AES algorithm. See Section 9.29, “Encryption of Disk Images”.

  • Cloud integration features. See Section 1.16, “Integrating with Oracle Cloud Infrastructure”.

This video provides a walkthrough from downloading to installing a windows 7 machine. ( I recommend installing A windows 10 instead for pen-test practice, win7 is also no longer being provided by microsoft.)

Video: | https://www.youtube.com/watch?v=NwCYnOab2Zo&ab_channel=ComputerSupport |

Once installed you can follow the same process for the kali machine OR you can download the virtual machine version's of kali

vm link: | https://www.kali.org/get-kali/#kali-virtual-machines |

NETWORK SETUP

TO reach the network setting. Right click on the machine you'd like to edit. Select settings, from here a pop up should happen and you will see the network selction between Audio & Serial Ports. You will have 4 adaptors. Ensure that only one is being used at a time unless you know what you are doing.

NETWORK TROUBLE SHOOT: Sometimes when I use legacy machines and I want to connect with another vm machine I would need to change its adapter type within Advanced. Normally you wouldnt want to touch anything in advanced but incase here are why you would want to change this.

  • AMD PCnet-PCI II (Am79C970A). This network adapter is based on AMD chip and can be used in many situations. As for Windows guests, this network adapter can be used for older Windows versions (such as Windows 2000) because newer Windows versions such as Windows 7, 8 and 10 do not contain a built-in driver for this adapter. Originally, the Am79C970A PCI device contained a single chip 10-Mbit controller and the DMA engine was integrated. This network adapter also supports AMD’s Magic Packet technology for remote wake-up.

  • AMD PCnet-FAST III (Am79C973). This virtualized network adapter is supported by almost all guest operating systems that can run on VirtualBox. GRUB (the boot loader) can use this adapter for network boot. Similarly to the previous network adapter, this one is based AMD chip.

  • Intel PRO/1000 MT Desktop (82540EM). This adapter works perfectly with Windows Vista and newer Windows versions. The most of Linux distributions support this adapter as well.

  • Intel PRO/1000 T Server (82543GC). Windows XP recognizes this adapter without installing additional drivers.

  • Intel PRO/1000 MT Server (82545EM). This adapter model is useful to import OVF templates from other platforms and can facilitate import process.

  • Paravirtualized Network Adapter (virtio-net) is a special case. Instead of virtualizing networking hardware that is supported by most operating systems, a guest operating system must provide a special software interface for virtualized environments. This approach allows you to avoid the complexity of networking hardware emulating and, as a result, can improve network performance.

How to attach virtual Types: There is a setting within the network adapter called "Attached to:" , This is crucial to how it affects your personal network you are creating and can also affect your home network. Below is a list of said different types and why you would use one of them.

  • Not attached. In this mode, Oracle VM VirtualBox reports to the guest that a network card is present, but that there is no connection. This is as if no Ethernet cable was plugged into the card. Using this mode, it is possible to pull the virtual Ethernet cable and disrupt the connection, which can be useful to inform a guest operating system that no network connection is available and enforce a reconfiguration.

  • Network Address Translation (NAT). If all you want is to browse the Web, download files, and view email inside the guest, then this default mode should be sufficient for you, and you can skip the rest of this section. Please note that there are certain limitations when using Windows file sharing. See Section 6.3.3, “NAT Limitations”.

  • NAT Network. A NAT network is a type of internal network that allows outbound connections. See Section 6.4, “Network Address Translation Service”.

  • Bridged networking. This is for more advanced networking needs, such as network simulations and running servers in a guest. When enabled, Oracle VM VirtualBox connects to one of your installed network cards and exchanges network packets directly, circumventing your host operating system's network stack.

  • Internal networking. This can be used to create a different kind of software-based network which is visible to selected virtual machines, but not to applications running on the host or to the outside world.

  • Host-only networking. This can be used to create a network containing the host and a set of virtual machines, without the need for the host's physical network interface. Instead, a virtual network interface, similar to a loopback interface, is created on the host, providing connectivity among virtual machines and the host.

  • Cloud networking. This can be used to connect a local VM to a subnet on a remote cloud service.

  • Generic networking. Rarely used modes which share the same generic network interface, by allowing the user to select a driver which can be included with Oracle VM VirtualBox or be distributed in an extension pack.

HOW I SETUP MY NETWORK FOR OFFLINE PENTESTING: This is for when I can't have any internet access to or from my victim machine as I might be using an untested vulnerabililty/malware on said victim machine that could result in data loss/hardware damage.

  • USE Internal-Networking. you will be interacting with malware and as such you dont need to be connected to the outside internet, let alone your host hardware. It will ensure that no inbound/outbound connectivity cannot happen.(Update what you need before starting offline pentest. Ex: kali on patch tuesdays.)
  • Change the MAC address to something you can remember if you have a mesh of vms at the same time.
  • If adding a spunk/opensense with a siem please use that network routing in vbox settings.

Sources found here: | https://www.virtualbox.org/manual/ch06.html | | https://www.nakivo.com/blog/virtualbox-network-setting-guide/ |