- Timestamp:
- Aug 23, 2011 2:00:43 PM (13 years ago)
- File:
-
- 1 edited
-
trunk/doc/manual/en_US/user_Security.xml (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/user_Security.xml
r38027 r38507 4 4 <chapter id="Security"> 5 5 <title>Security guide</title> 6 7 <sect1> 8 <title>Overview</title> 9 <para> 10 </para> 11 12 <sect2> 13 <title>General Security Principles</title> 14 15 <para>The following principles are fundamental to using any application 16 securely. 17 <glosslist> 18 <glossentry> 19 <glossterm>Keep Software Up To Date</glossterm> 20 <glossdef> 21 <para> 22 One of the principles of good security practise is to keep all 23 software versions and patches up to date. Activate the VirtualBox 24 update notification to get notified when a new VirtualBox release 25 is available. When updating VirtualBox, don't forget to update 26 the Guest Additions. Keep the host operating system as well as the 27 guest operating system up to date. 28 </para> 29 </glossdef> 30 </glossentry> 31 32 <glossentry> 33 <glossterm>Restrict Network Access to Critical Services</glossterm> 34 <glossdef> 35 <para> 36 Use proper means, for instance a firewall, to protect your computer 37 and your guest(s) from accesses from the outside. 38 </para> 39 <para> 40 The default networking mode for VMs is NAT which means that 41 the VM acts like a computer behind a router, see 42 <xref linkend="network_nat"/>. If bridged networking is used, 43 the VM acts like a computer inside the same network as the host, 44 see <xref linkend="network_bridged"/>. In this case, a firewall 45 might be necessary to protect other computers on the subnet from 46 a potential malicious guest. In some cases it is worth to consider 47 adding a forwarding rule for a specific port in NAT mode instead 48 of using bridged networking. 49 </para> 50 <para> 51 Sometimes a VM doesn't need to be connected to the public network 52 at all. Internal networking (see <xref linkend="network_internal"/>) 53 or host-only networking (see <xref linkend="network_hostonly"/>) 54 are often sufficient to connect VMs among each other or to connect 55 VMs only with the host but not with the public network. 56 </para> 57 </glossdef> 58 </glossentry> 59 60 <glossentry> 61 <glossterm>Follow the Principle of Least Privilege</glossterm> 62 <glossdef> 63 <para> 64 The principle of least privilege states that users should be given the 65 least amount of privilege to perform their jobs. We strongly discourage 66 from executing VirtualBox with system privileges. 67 </para> 68 </glossdef> 69 </glossentry> 70 71 <glossentry> 72 <glossterm>Monitor System Activity</glossterm> 73 <glossdef> 74 <para> 75 System security stands on three legs: good security protocols, proper 76 system configuration and system monitoring. Auditing and reviewing audit 77 records address this third requirement. Each component within a system 78 has some degree of monitoring capability. Follow audit advice in this 79 document and regularly monitor audit records. 80 </para> 81 </glossdef> 82 </glossentry> 83 84 <glossentry> 85 <glossterm>Keep Up To Date on Latest Security Information</glossterm> 86 <glossdef> 87 <para> 88 Oracle continually improves its software and documentation. Check this 89 note note yearly for revisions. 90 </para> 91 </glossdef> 92 </glossentry> 93 94 </glosslist> 95 </para> 96 </sect2> 97 </sect1> 98 99 <sect1> 100 <title>Secure Installation and Configuration</title> 101 </sect1> 102 103 <sect2> 104 <title>Installation Overview</title> 105 <para> 106 General VirtualBox installation instructions for the supported hosts can 107 be found in <xref linkend="installation"/>. On certain hosts it is possible 108 to omit certain VirtualBox components from installing but the general case 109 is to install the complete VirtualBox package. The installation must be 110 done with system privileges. 111 </para> 112 </sect2> 113 114 <sect2> 115 <title>Post Installation Configuration</title> 116 <para> 117 Normally there is no post installation configuration of VirtualBox components 118 required. However, on Solaris and Linux hosts it is required to configure 119 the proper permissions for users executing VMs which should be able to 120 access certain host resources. Linux users must be member of the 121 <emphasis>vboxusers</emphasis> group to pass USB devices to a guest. If a 122 serial interface should be accessed from a VM, the proper permissions must 123 be granted to the user as well. The same applies to raw partitions which 124 should be accessible for a VM. 125 </para> 126 </sect2> 127 128 <sect1> 129 <title>Security Features</title> 130 <para>This section outlines the specific security mechanisms offered 131 by VirtualBox.</para> 132 133 <sect2> 134 <title>The Security Model</title> 135 <para> 136 One property of virtual machine monitors (VMMs) like VirtualBox is to encapsulate 137 a guest by executing it in a dedicated environment, a virtual machine, 138 running as a user process on the host operating system. The guest cannot 139 communicate directly with the hardware or other computers but only through 140 the VMM. The VMM provides emulated physical resources and devices to the 141 guest which are used by the guest operating system to perform the required 142 tasks. The VM settings control the amount of resources provided to the guest 143 (for example the amount of guest RAM or the number of guest processors, (see 144 <xref linkend="generalsettings"/>) and the selection of features enabled 145 for a specific VM process (for example remote control, see 146 <xref linkend="vrde"/>). 147 </para> 148 </sect2> 149 150 <!-- 151 <sect2> 152 <title>Configuring and Using Authentication</title> 153 </sect2> 154 155 <sect2> 156 <title>Configuring and Using Access Control</title> 157 </sect2> 158 159 <sect2> 160 <title>Configuring and Using Security Audit</title> 161 </sect2> 162 163 <sect2> 164 <title>Congiguring and Using Other Security Features</title> 165 </sect2> 166 --> 167 168 </sect1> 169 170 <!-- 171 <sect1> 172 <title>Security Considerations for Developers</title> 173 </sect1> 174 --> 6 175 7 176 <sect1>
Note:
See TracChangeset
for help on using the changeset viewer.
