I’ve created 2 Ansible Roles (chilcano.apache-nifi and chilcano.apache-nifi-toolkit) to automate the creation of a multi-node and secure NiFi cluster. The chilcano.apache-nifi Ansible Role doesn’t implement Cluster State coordination through Apache ZooKeeper, and the TLS Toolkit Standalone mode has been implemented by the chilcano.apache-nifi-toolkit Ansible Role.
The purpose of this blog post is explaining how to automate the creation of 5 instances of Apache NiFi, secure and not secure.
This blog post is implementing the same scenario used in the previous post Mass provisioning of Kismet and Apache MiNiFi in Raspberry Pi using Ansible. The unique difference is this new blog post I’m using Ansible Roles instead of Ansible Playbooks where all automated operations as install, configure, run, etc. were implemented in Ansible Tasks.
Lately I’m focusing on Automation in Big-Data Projects, and with my experience in Cyber Security I can bring new approaches (Threat Analisys, Privacy, Intrusion Detection, etc.) and ideas to those Big-Data Projects. With this post I will start a serie of articles explaining how to do “Data Ingestion/Capture” in the
Edgeby using Ansible to do
provisioning, multiple remote devices in the
Edge(Raspberry Pi), Kismet to capture WIFI Anonymous traffic, Apache MiNiFi to captured traffic in the
edgeand Apache NiFi to aggregate, enriched and forward traffic to Solr / ElasticSearch …everything near to real-time.
So a few months ago I published a serie of post explaining how to capture WIFI traffic and process it near to real time by using WSO2 BAM, CEP Siddhi, Apache Cassandra, Apache Thrift, Kismet running on a Raspberry Pi and Docker.
Now, after several Big Data and Security projects, I can add to previous solution, fresh air and improve the technological approach.
Provisioning massively cross-compiled binaries to Raspberry Pi (arm) using Vagrant, VirtualBox, Ansible and Python
If you are involved in an IoT or Mobile Application provisioning Project you probably need build a mechanism to spread your application binaries to all Devices on stock and to all the rolled out Devices. With this Proof-of-concept I will shown you how to build the app binary provisioning system for your custom platform, in this case I’m going to use Raspberry Pi (ARM processor) quickly avoiding perform unnecessary tasks and providing also an ARM cross-compiling platform.
“How do you eat an elephant? One bite at a time” - This phrase makes sense, everybody understands It but sometimes is forgotten.
Happily some technology companies have managed to internalize this phrase in its processes and products.
Below some examples:
In my 4 previous blog post I explained each part of this Proof-of-concept, they are:
- Analysing Wireless traffic in real time with WSO2 BAM, Apache Cassandra, Complex Event Processor (CEP Siddhi), Apache Thrift and Python:
- A Python Microservice in a Docker Container (MAC Address Manufacturer Lookup)
Now, in this blog post I’m going to explain how to run two Docker Containers, the WSO2 BAM and the MAC Address Manufacturer Lookup containers, by using Docker Compose.
A MAC address, also called physical address, is a unique identifier assigned to every network interfaces for communications on the physical network segment. In other words, you can identify the manufacturer of your device through your pyshical address.
There are different tools on the Internet that allow you to identify the manufacturer from the MAC Address. I previous post I wrote about how to capture the wireless traffic and all MAC Address, now in this post I will explain how to implement a Docker container exposing a Rest API to get the Manufacturer from the captured MAC Address.
WIFI Pineapple Nano is a nice tiny device to do Wireless Security Auditing. It has OpenWRT embedded as SO with 2 Wireless NIC pre-configured and a lot of Security tools pre-installed ready to perform a Security Wireless Auditing.
The idea of this post is to do a quick wardriving around of the Mobile World Congress at Barcelona to check if the attendants are aware about their Mobile Devices with the leak of information.
Everything generates data: Capturing WIFI anonymous traffic using Raspberry Pi and WSO2 BAM (Part III)
After configuring the Raspberry Pi in monitor WIFI/802.11 mode (first blog post) and after configuring Raspberry Pi to send the 802.11 captured traffic to WSO2 BAM and Apache Thrift listener (second blog post), now I will explain how to create a simple Dashboard showing the WIFI traffic captured in real-time.