So, you’ve got Security Onion (SO) running from the Security-Appliance-in-a-Box via Ansible. Now what? How do you begin to ingest logs from your other devices into the included Elastic instance? I’m glad you asked! There’s a couple steps you’ll need to follow. Allow Access First you’re going to need to open the firewall to allow …
Read more “Ingesting External Logs via Security Onion’s Elasticsearch”
On my first attempt to install Security Onion in my Security-Appliance-in-a-Box, I ran into a weird networking issue. The install script failed with the error “The IP being routed by Linux is not the IP address assigned to the management interface (ens1)“. Looking around online, I discovered that I’m not the first person to experience …
For my home network I’ve historically used an IPfire firewall, running on a Raspberry Pi. In general, it’s been a great little setup, however I’ve decided that I wanted to move to a beefier rig that contains both a pfSense Firewall, and a NIDS tap that feeds into a Security Onion Server, all on the …
We’ve talked at length about how we got started on Salesforce, now let’s explore (in a development/test instance) what it looks like practically as it’s implemented. When a user logs in the are greeted with the entirety of our portfolio. From this they can chose from a variety of areas such as On-Premises vs. Cloud …
Read more “Portfolio and Lifecycle Management – Tooling Overview”
As I mentioned in the introduction one of the primary drivers towards low-code development is increased velocity and a lower bar of entry. Both of these are good things, however, as we saw earlier the lower bar of entry might not be enough. Additionally, the increased velocity (due to more contributors from a non-technical background) …
Read more “The Road to Low-Code | Lifecycle Management and Feature Cataloging”
So, now you’ve built this low-code platform and overly optimistic expectation is that all your users who previously had requests are going to be tripping over each other to implement their features. Well, not so much… We’ve had a mixed response coming from our users around embracing the low-code mentality. In some cases it’s very …
Read more “The Road to Low-Code | Will (and Should) They Come?”
Version 1 Our first CI/CD strategy was very basic; and for a simple reason, we didn’t have control of what SalesforceDX (SFDX) generated. The fear that I had was that we in the engineering community would start embracing the coded aspects of the Salesforce configuration and start to use cherry picking and end up in …
Before we started our journey to low code we knew that there were going to be areas that we had to mitigate in advance if we were going to be successful. The core of many of these was around the ability to capture the “low-code output” as actual code and storing it in our own …
Read more “The Road to Low-Code | Mitigating Foreseen & Unforeseen Low-Code Impacts”
If you are to search for “low-code benefits” you will quickly find that there are many opinions and experiences around the benefits of low-code development. The aforementioned Google search returns about 8.5 billion results. A couple examples are: Decreased costs Higher productivity Improved agility Enhanced Innovation (hmm… that’s an interesting concept) Lower barrier to entry …
Every team, every operation, and even every object has its weakest link. You can’t remove the weakest link as another aspect will take its place. Hence business, like every other area of life is consistently addressing the weakest link to raise the strength of the whole. Our team, like make is constrained on resources, specifically …