Auditing in shared distributed virtualized environments


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Auditing in shared distributed virtualized environments
# 1  
Old 01-22-2008
Auditing in shared distributed virtualized environments

HPL-2008-4 Auditing in shared distributed virtualized environments - Baldwin, Adrian; Shiu, Simon; Beres, Yolanta
Keyword(s): audit, virtualization, security, assurance
Abstract: The introduction of virtualization into the data centre can help provide a more manageable platform for the enterprise by reducing the number of physical machines and increasing utilization as well as enabling automation via virtual machines, networks and storage elements. Enterprises are required t ...
Full Report

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. Linux

Unique Linux ID in virtualized environment

Hi I need to know what is the unique identifier for Linux OS even in a virtualized environment? eg like Machine GUID for windows. I need to know something similar for linux, AIX, Solaris in virtualized environment. Thanks (6 Replies)
Discussion started by: skyineyes
6 Replies

2. Programming

Shared library with acces to shared memory.

Hello. I am new to this forum and I would like to ask for advice about low level POSIX programming. I have to implement a POSIX compliant C shared library. A file will have some variables and the shared library will have some functions which need those variables. There is one special... (5 Replies)
Discussion started by: iamjag
5 Replies

3. Solaris

Can SunOS be virtualized?

As the title reads; is it possible to virtualize a Sun server running the sparc processor? I know VMWare can do SunOS with the x86 processor, but we have several Sun Servers with the Sparc processor and I would like to move it to a virtual environment. (11 Replies)
Discussion started by: bbbngowc
11 Replies

4. Virtualization and Cloud Computing

Facebook Meets the Virtualized Enterprise

HPL-2008-72 Facebook Meets the Virtualized Enterprise - Curry, Roger; Kiddie, Cameron; Markatchev, Nayden; Simmonds, Rob; Tan, Tingxi; Arlitt, Martin; Walker, Bruce Keyword(s): social networking, Web 2.0, cloud computing Abstract: "Web 2.0" and "cloud computing" are revolutionizing the... (0 Replies)
Discussion started by: Linux Bot
0 Replies
Login or Register to Ask a Question
SYSTEMD-DETECT-VIRT(1)						systemd-detect-virt					    SYSTEMD-DETECT-VIRT(1)

NAME
systemd-detect-virt - Detect execution in a virtualized environment SYNOPSIS
systemd-detect-virt [OPTIONS...] DESCRIPTION
systemd-detect-virt detects execution in a virtualized environment. It identifies the virtualization technology and can distinguish full machine virtualization from container virtualization. systemd-detect-virt exits with a return value of 0 (success) if a virtualization technology is detected, and non-zero (error) otherwise. By default, any type of virtualization is detected, and the options --container and --vm can be used to limit what types of virtualization are detected. When executed without --quiet will print a short identifier for the detected virtualization technology. The following technologies are currently identified: Table 1. Known virtualization technologies (both VM, i.e. full hardware virtualization, and container, i.e. shared kernel virtualization) +----------+----------------+--------------------------------------+ |Type | ID | Product | +----------+----------------+--------------------------------------+ |VM | qemu | QEMU software virtualization, | | | | without KVM | | +----------------+--------------------------------------+ | | kvm | Linux KVM kernel virtual machine, | | | | with whatever software, except | | | | Oracle Virtualbox | | +----------------+--------------------------------------+ | | zvm | s390 z/VM | | +----------------+--------------------------------------+ | | vmware | VMware Workstation or Server, and | | | | related products | | +----------------+--------------------------------------+ | | microsoft | Hyper-V, also known as Viridian or | | | | Windows Server Virtualization | | +----------------+--------------------------------------+ | | oracle | Oracle VM VirtualBox (historically | | | | marketed by innotek and Sun | | | | Microsystems), | | | | for legacy and KVM | | | | hypervisor | | +----------------+--------------------------------------+ | | xen | Xen hypervisor (only domU, not dom0) | | +----------------+--------------------------------------+ | | bochs | Bochs Emulator | | +----------------+--------------------------------------+ | | uml | User-mode Linux | | +----------------+--------------------------------------+ | | parallels | Parallels Desktop, Parallels Server | | +----------------+--------------------------------------+ | | bhyve | bhyve, FreeBSD hypervisor | +----------+----------------+--------------------------------------+ |Container | openvz | OpenVZ/Virtuozzo | | +----------------+--------------------------------------+ | | lxc | Linux container implementation by | | | | LXC | | +----------------+--------------------------------------+ | | lxc-libvirt | Linux container implementation by | | | | libvirt | | +----------------+--------------------------------------+ | | systemd-nspawn | systemd's minimal container | | | | implementation, see systemd- | | | | nspawn(1) | | +----------------+--------------------------------------+ | | docker | Docker container manager | | +----------------+--------------------------------------+ | | rkt | rkt app container runtime | +----------+----------------+--------------------------------------+ If multiple virtualization solutions are used, only the "innermost" is detected and identified. That means if both machine and container virtualization are used in conjunction, only the latter will be identified (unless --vm is passed). OPTIONS
The following options are understood: -c, --container Only detects container virtualization (i.e. shared kernel virtualization). -v, --vm Only detects hardware virtualization). -r, --chroot Detect whether invoked in a chroot(2) environment. In this mode, no output is written, but the return value indicates whether the process was invoked in a chroot() environment or not. --private-users Detect whether invoked in a user namespace. In this mode, no output is written, but the return value indicates whether the process was invoked inside of a user namespace or not. See user_namespaces(7) for more information. -q, --quiet Suppress output of the virtualization technology identifier. -h, --help Print a short help text and exit. --version Print a short version string and exit. EXIT STATUS
If a virtualization technology is detected, 0 is returned, a non-zero code otherwise. SEE ALSO
systemd(1), systemd-nspawn(1), chroot(2), namespaces(7) systemd 237 SYSTEMD-DETECT-VIRT(1)