Latest Headlines

VMware View – Black Screen during login with Linux VM

The last couple of days I was playing around with a new View Pools based on Ubuntu Linux 18.04 VMs. After some initial test I created my working Image and made my pool for the users.
After a couple of days, I became a message from one of my users he could not login in the Linux Desktop. When he starts his Horizon Client he got a Black Screen and after a minute the connection was discard.
I started to investigate to the error and one of the first things I did was to looking in the Logfiles. First thing I did was to look into the installed packages which were different from my original Image. I noticed that the User installed Docker-CE in his virtual View Desktop to interact with a VMware Integrated Container (VIC) Server. For those which are not familiar with Docker, Docker need some devices (internal Network) to operate. This network is created during the installation. When I stopped the Docker Server and restart the viewagent the user could login again. After a reboot the login was not possible with the same Black Screen bevor. After these findings I looked at the logfiles from the viewagent-debug.log. There I found something in the Logs:

tail -f /var/log/vmware/viewagent-debug.log
018-08-28T18:50:53.911Z DEBUG [ComponentResponse] Reponse directed to:ID:/
2018-08-28T18:50:53.912Z DEBUG [ComponentResponse] Message is -4836c1bb:1654679ccbd:-1e95 cn=9175d3da-3be6-4353-8b36-9804624e402a,ou=servers,dc=vdi,dc=vmware,dc=int cn=linux-vms,ou=server groups,dc=vdi,dc=vmware,dc=int ubuntu-vdi-001 XXXXXXXX thisIsAframeworkSSLAlgo thisIsAframeworkThumbprint f7911431-339e-47d3-a36f-7c27ac8874c2 XXXXXXXX BLAST ready 22443 XXXXXXXX

In the Log I could see that the Blast protocol was mapped to the wrong (the Docker network). So that was the reason which the Screen keep Black when the user tried to login. After some searching how to find the Blast protocol to the right network I found the solution in the VMware Community ( In short the solution is: That you configure the correct network (Subnet)in the /etc/vmware/viewagent-custom.conf file and there the parameter "Subnet=XXX.XXX.XXX.XXX/24" . After that you must restart the viewagent service ( service vieagent restart ). That’s all and also after a reboot of a system the login is possible.
Hope this helps if somebody has the same problem.


Honeypot as a Service (HaaS) Part 3

This is the third Post of the Haas Series…..

After we have everything up and running would should take a deeper look at the vRealize Log Insight.  There we get our notifications in the interactive analytics. In normal cases nobody will monitor the whole time the interactive analytics therefore we create a Dashboard. The create dashboard is only for your custom view. The log Insight documentation state it like this “You can add, modify, and delete dashboards in your Custom Dashboards space.”

So, in the first step we create a dashboard for your personal view. The creating is quite easy. So, if you have an alert in the interactive analytics you can create the Dashboard from there.



Just click in the New Dashboard Icon on the right site. In the Wizard you create a new dashboard. Provide a Name and if you want share the Dashboard with other Users in the environment.

I use the chart graph for my Dashboard. After you are finished you will find your Dashboard in on the Dashboard View under Shared Dashboards.

Quite Easy or? But would It be better to get an Alert Notification from Log Insight?

This is also very easy. When you go back in the Interactive Analytics just take the Alerts Button.

In the Windows we choose “Create Alert from Query”.

There you provide the required Details for the Alert. Be sure that you configured your SMTP Server before when you use E-Mail as alert notification.

That was cool so far, or?

In the last months I made a couple of NSX Implementations. NSX provides us some really cool feature like the possibility to move VMs into Quarantine to isolate them from the communication with other VMs. So why wo should not use these feature, to migrate the VM were the Access violation was made, into a quarantine location to research what is happening on this VM? When the access was done from a physical machine, we can also create a firewall rule which deny the access to the virtual environment? From my point of view this is security in an automated way.

In this blog Post I will not show how to install and configure the NSX Part of this series. There are a lot of useful information available.

To archive these goal, we can use a REST API Call to the vRO Server to call a workflow which we develop to migrate the VMs or create the firewall rule. One of the first things which we need, is the possibility to interact with NSX from the VMware Orchestrator. Therefore, will install the VMware Orchestrator NSX Plugin. The plugin can be found on the VMware Page:

We also need two additional Plugins The first plugin is needed to decrypt the BASE64 encrypt string from the Shim in vRO. The Plugin can be found here:

The next Plugin is not really necessary but from my point of view the JSON Implementation in vRO is not the best in the world…. therefore, I use the jsonPath for Orchestrator Plugin frim Soeldner-Consulting. The documentation and the Link to the VMware Solution Exchange can be found here:

jsonPath for Orchestrator

After we download the all plugins we can install them via the vRO Control center.

After we are finished with that, we have to create our Workflow that must start when an alert is triggered. The triggering can be done via email or REST API Call. I prefer the REST-API Call du the circumstance that this more flexible, but wait…….here we have a problem. The VMware vRealize Log Insight doesn’t offer any option to create a REST API Call. In the Web GUI only Webhook Notification is available. Therefore, we need a translation between the Webhook and the REST API Call which we need for the vRealize Orchestrator. As always there is an solution available…..Steve Flanders create a Shim which can act as Proxy for the Webhook notification in direction of the VMware vRealize Orchestrator. Steve has a GIT Repository with a good documentation about the different available versions and the installation. I will not go further on the installation as already everything is explained here:

Another useful post can you find here:

After we installed and configured the Shim, we are ready to make our next steps.

I created a vRO Workflow which used as Input parameter the name of the Attacker VM. The workflow checks the Attacker VM against the configured Datacenter. When it is a virtual machine, then an NSX Security Profile is attached to the virtual machine and all communication is denied. When it is not a virtual machine, then an IPSet is created and this IPSet is added to a Security Group

For the workflow it is necessary, that the NSX Manager is configured within vRO. Also, that a security Policy exist which we can use in the workflow. Also, the Datacenter which host our virtual machines in our environment must be provided.

Now let’s have a look at the Workflow:

The Workflow consists from different areas. In the First Part of the Workflow (the yellow box) we have to decode the Base64 string and parse the VM Name from the Log Insight Message.

When we are finished with that, we check if the Attacker Machine is a virtual machine (the red box).  When the machine is a VM, we apply the security Group to the VM (the light brown box) which denies all communication via the Security Policy.

When the Attacker VM is not a virtual machine then the machine will be checked against DNS (the green box) to gather the IP. The DNS checking is done via vRO DNS query so the Orchestrator Appliance must be configured correctly with DNS Server. The DNS Check is done via Name and FQDN. When the name could be resolved and we have the IP Address, then an IPSet is created and the Attacker machine is applied to the security Policy. This only protects the virtual environment!

In all cases a email is created (the blue box) and send to an Administrator.

The Workflow itself has some Attributes which must be filled:

  1. Datacenter –> The Datacenter were to check against the Attacke Machine if it is a VMs
  2. SecurityGroupID –> The Securitygroup ID. The ID is not the name but should look like this: securitygroup-98765. If you don’t know the SecurityGroupID, you can Browse within vRO in the NSX Manager Connection. There you can find the correct name
  3. NSXManager –> Your corresponding NSX Manager (which must be configured before in vRO)
  4. smtpHost –> Your Mail Server
  5. fromName –>  Email Sender Name
  6. fromAddress –>  Email Sender Address
  7. toAddress –> Were the Mail should arrive
  8. DNSDomain –> Your DNS Name to check against FQDN
  9. Optional: SMTPUsername –> The Mail Server Username, if required
  10. Optional: SMTPPassword –> Password for the Mail Server user

For the Workflow itself there is room for optimizing. A loop to check against different Datacenter, or a loop to check against different Domain names……For me and this Demo the Workflow makes his job….

The Workflow can be found here:


Honeypot as a Service (HaaS) Part 1 Link:
Honeypot as a Service (HaaS) Part 2 Link:


Honeypot as a Service (HaaS) Part 2

In the second Post of this series, we create the Log File Reporting which we will send to vRealize Log Insight.


After our samba server is configured (in Part 1) we have to deal with our logfiles and report them to our vRealize Log Insight.

In our Samba Server we already configured the logging which is done in the path /var/log/samba. There files are created for every client which tries to access our server. As long as no client tried to access the file the director should log like this:

When you already accessed your server, you will have a log entry like log. or similar.

I will create an event every time a client is accessing the share. Therefore, I will use the inotify-tools. unfortunately, these program is not included the standard CentOS Repository so we have to add an additional repo. I use the fedoraproject repo where we download the Repo configuration and install it.


rpm -ivh epel-release-7-10.noarch.rpm

After that we can install the inotify-tools with yum.

yum -y install inotify-tools-devel.x86_64

After that we create the string to monitor the samba server for client access.

inotifywait -mrq -e create -e modify -e delete /var/log/samba

In this monitoring we ignore changes to the log.smbd file, due the circumstance that this a a standard file form the samba service. The output of this monitoring locks like this:

/var/log/samba/ MODIFY log log.client1-vcoportal

As we want the information on a remote server, we have to extend our logging string with logger to send the information to a remote server.

inotifywait -mrq -e create -e modify -e delete /var/log/samba  | while read file; do ( logger -n securitybreak $file ) done

I send my string to a vRealize Log Insight server and tag the log entry with the word “securitybreak”. In Log Insight we can filter for that word……

So, if you use the interactive analyses you can search for your string.

For me the is still room for improvement. The only relevant information for me is the client name. So, let’s modify the monitoring string.

inotifywait -mrq -e create -e modify -e delete /var/log/samba/host | while read file; do hostname=$(echo $file | cut -d '.' -f2,3,4,5 ); (logger -n -t securitybreak $hostname) done


We strip done the string we send to our Log Insight Server to just the Client name. I guess there is a better way to create the string but for me this one work fine.

Now we get only the Client name reported in our Log Insight

How cool is that?

The last thing we have to do is to create a startup script for our monitoring string.

In our case, we will want to run inotifywait as a service and create an init script. First we will create our configuration file:

# specify log file


# specify target directory for monitoring


# specify target events for monitoring ( comma separated )

# refer ro man inotifywait for kinds of events


# Log Insight or SNMP Server

# Security tag



Next, we will create the init script where we use the config file we created before as input for the variables.


# inotifywait: Start/Stop inotifywait


# chkconfig: 2345 10 90

# description: inotifywait waits for changes to files using inotify.


# processname: inotifywait

. /etc/rc.d/init.d/functions

. /etc/sysconfig/network

. /etc/inotifywait.conf



start() {

echo -n $Starting inotifywait:

# Clear Log File

if [ -e $LOGFILE ];then /usr/bin/truncate -s0 $LOGFILE;fi

# Start the Monitoring

/usr/bin/inotifywait -e $EVENT -dmrq $MONITOR --exclude ‘\(log.smbd\)*’ -o $LOGFILE | cut -d '.' -f2,3,4,5 $LOGFILE | while read file; do (/usr/bin/logger -n $SNMPSERVER -t $SECURITYTAG $file) done


echo [ $RETVAL -eq 0 ] && touch $LOCK return $RETVAL


stop() {

echo -n $Stopping inotifywait:

killproc inotifywait


echo [ $RETVAL -eq 0 ] && rm -f $LOCK return $RETVAL


case $1 in start)





status inotifywait;;





echo $Usage: $0 {start|stop|status|restart}

exit 1


exit $?


The permissions need to be 755:

chmod 755 /etc/rc.d/init.d/inotifywait


We can start the service now:

/etc/rc.d/init.d/inotifywait start


The result will be like this:

[[email protected] ~]# /etc/rc.d/init.d/inotifywait start

Starting inotifywait (via systemctl):                      [  OK  ]


We need to ensure that the service starts when the server boots, so we need to add it to chkconfig

chkconfig --add inotifywait

chkconfig inotifywait on


The log entry is written in the /var/log/inotify.log file and from there they were cut down to post the to the log insight server. We have to use this loop due the circumstance, that in our start script inotiywait is used in daemon mode. There a logfile is mandatory.

That’s it for Part 2


Honeypot as a Service (HaaS) Part 1 Link:
Honeypot as a Service (HaaS) Part 3 Link:


Honeypot as a Service (HaaS) Part 1


This series will show some Ideas which include “homemade” Security Functions. For professional environments, I recommend to talk to the security Vendor of your choice to build up a secure environment. This series will show examples which include different VMware products and their Interaction and teach things which can be done with them.

Now, let’s start.

Today I will start a series which I call Honeypot as a Service (HaaS). What is the Idea behind the HaaS?

In most environments hackers are already a long time present bevor the get localized. When the hacker has access on one of the server, he will start to search for other systems where he can get access and grab sensitive information (credit card data, intellectual property). So, which are system / functions a hacker is locking for?

So, most Hacker are looking for routing information and will start a “slow and silence network scan” for systems which he can attack and get into his hands. When we now start to place virtual machines in our network, which doesn’t have any functions for our network nobody should access them in normal case. From the standpoint of an attacker, he doesn’t know if a system is relevant or not. That’s will be the point for us, to provide the hacker a system with an old infectible SMB Server which he can attack. So, if somebody / somewhat tries to access such an “no functional VM”, we generate a log entry which is forwarded to an Log system. There we can parse the logs and generated “automated” rules to isolate VMs or VM communications.

In this example, I will use a lot of different VMWare products to archive these HaaS environment and the actions we will use.

This series will include:

  • VMware vRealize Log Insight as log host
  • VMware vRealize Orchestrator as “workhorse for a lot of task”
  • VMware NSX for VM isolation and Firewall Rules
  • A small Linux System as Honeypot with an SAMBA Service

So, let start to build up a Linux System which we can use in our vRA Blueprint as Honeypot. I prefer a CentOS Distribution. I choose a 7.x Release of CentOS. The ISO can be downloaded here

I will use the minimal Installation ISO and Install Samba and SSH afterwards.

We will change the Hostname and IP Settings for a later time in vRA so during installation we keep the hostname and network on default settings. We have one important things which we take care about during installation. By default, the NICs are not automatically connected during installation, so that should be changed.

After our Installation has finished we will install the following packages:

  • Perl
  • Samba
  • DNS tools (just for Troubleshooting)
  • Network Manager (Text Version if you need to reconfigure your Config)

This can be done via this command:

yum -y install perl samba system-config-network-tui.noarch dns-utils

When you don’t have a DHCP Server in place, then you need to configure your network settings on Command line: $ sudo ifconfig eth0 netmask

Also, you need to set your default route:

$ sudo route add default gw eth0

As last step you need some DNS Server entries:

$ sudo vi /etc/resolv.conf

Modify or enter nameserver as follows:


After we have installed the need packages we can start with the installation from the VMware tools. This is documented well in the VMware documentation so I will not write it down here.

The next Step is to configure our Samba Server for a SMB Share which is available for the attacker.

Now, let us create a fully accessed anonymous share for the users. Everybody can read/write in this share.

We create a directory called /samba/backup and set full permission. The reason (for me) to set the name to backup is, to mark the share as important and a useful target which information or potential interesting thinks in it. I also will create some additional folders to have a interesting target. I use a linux bash script to create the folder and set the required permissions.

echo "This script creates a bunch of folder which were used in a samba share example on"


echo "$dirname"

if [ ! -d "/$dirname" ]


echo "Folder doesn't exist. Creating now"

mkdir --p "/$dirname"

echo "Create some other Folders ....."

mkdir --p "/$dirname/HR"

mkdir --p "/$dirname/IT"

mkdir --p "/$dirname/Dev"

mkdir --p "/$dirname/Public"

mkdir --p "/$dirname/Files"

mkdir --p "/$dirname/Userhome"

echo "Set some permissions for the parent Folder"

chmod -R 0775 /samba/backup

echo "Set nobody as Owner for the Folder so that everybody can read see and read it"

chown  nobody:nobody /samba/backup

echo "Change SE Linux Permissions on the Folder"

chcon -t samba_share_t /samba/backup


echo "Parent Directory exists"


Just create a file and make it executable with the script content in it. You can change the directory names to whatever you want / need.

After we created the directory we must edit the Samba configuration file.

vi /etc/samba/smb.conf
# See smb.conf.example for a more detailed config file or
# read the smb.conf manpage.
# Run 'testparm' to verify the config is correct after
# you modified it.
        workgroup = vcoportal
        security = user
        passdb backend = tdbsam
        unix charset = UTF-8
        dos charset = CP932
        hosts allow = 127. 192. 172. 10.
        max protocol = SMB2
        map to guest = Bad User
        # log files split per-machine (the host logs are stored on a non-default path):
        log file = /var/log/samba/log.%m
Log level = 2
        # maximum size of 50KB per log file, then rotate:
        max log size = 50
        comment = Home Directories
        valid users = %S, %D%w%S
        browseable = No
        read only = No
        inherit acls = Yes
comment = Backup Share
path = /samba/backup
browsable =yes
writable = yes
guest ok = yes
read only = no
force user = nobody

Now we can test the Samba server configuration

We can test the Samba server configuration syntax errors using the command ‘testparm’.


When everything looks good you can browse to your samba share.





That’s it for Part 1


Honeypot as a Service (HaaS) Part 2 Link:
Honeypot as a Service (HaaS) Part 3 Link:


VMware Realize Orchestrator OVF Transfer Plug-In Version 3 released

I am pleased to announce a new Version of the popular OVF Transfer Plugin. The new mayor release Version is 3. My colleague Sascha Bitzer made a lot of Improvements for the plugin.

In this version we include some bugfixes and also new feature. Here are some Highlights:

The OVA/F Transfer plug-in allows you to import and export virtual machines as OVF/OVA template to/from the VMware vCenter via the VMware vCenter/vRealize Orchestrator.

This plug-in provides actions and workflows to use the OVF/A functionalities directly in

your own workflows. It also supports the automated creation of OVF/A Import Workflows, based on provided ovf/ova files.

Nowadays this plugin also supports new features like vRA-Integration, Authentication and simple File upload



This plug-in includes amongst others following features:

  • [Export] Export of virtual machines as OVF templates
  • [Import] Import of virtual machines as OVF or OVA templates
  • [Import] Automated creation of Import workflows based on OVF/A
  • [Import] Support for vSS and vDS PortGroups
  • [Import] Support for multiple vNics
  • [Import] Support for OVF properties and Deployment Options, e.g. used for virtual appliance imports
  • [Import/Export] Supported sources/destinations: Locale file, HTTP, HTTPS,FTP, CIFS
  • [Import] Import OVF/A using vCAC/vRA – Service Blueprint
  • [Import/Export] Support for Basic and Digest authentication
  • [Import] Upload of any file to datastore (e.g. ISO)



This plug-in contains two ready to use workflows for importing and exporting virtual machines. It also contains one workflow for extracting and displaying all available OVF

properties usable for the import workflow. For a wizard like experience there is also a workflow for an automated generation of import workflows based on the provided

OVF/A files. This automatically generated workflow will contain all input parameters and options for the given OVF/a file. In addition to those workflows you will now find

two new workflows. The first one is used to upload any kind of file to a target datastore.

This workflow can therefore be used to manage the upload of ISO files/images. The second workflow enables you to integrate the process of importing an OVF/A into your

vRA environment. Now it’s possible to import OVF/A directly with vRA. You can find those workflows in the Workflows folder: SVA/OvaTransfer



The Plugin can be found at the VMware Solution Exchange. Here is the URL:


Have fun and orchestrate the World 😉