Partner Newsletter December 2022

Dear

While the year is almost over, we are still working at full speed. Last month, we released one of the most requested features, which is the scanner exclusions functionality. And that's not all. In this edition of our partner newsletter, you will read how we upgraded our Probes, giving Partners more insight into their performance.

Also in this newsletter, read about Guardian360's totally overhauled partner programme. In 2023, we will strive to position our Partners as an information security authority to their clients.

In addition, we present a video reference with customer Innovam. Of course, we also tell you about G360DAO and, last but not least, I'll share my concerns regarding hyped vulnerabilities.

For now, enjoy reading and on behalf of the Guardian360 team I wish you a blessed Christmas and a wonderful New Year!

Kind regards,

Jan Martijn Broekhof

Managing Director

Lighthouse update

As mentioned above we've deployed the Scanner Exclusion functionality late November. This new functionality allows Partners to exclude specific scanners from scanning specific ports. It's even possible to only exclude scanning of specific ports for specific scanners. As a result, Partners are not forced to exclude scan objects from scanning completely. Of course, this functionality can be used via your browser as well as the API.

Below you'll find a screenshot of our ApMon functionality, which has been released early December. Partners are now able to better determine the status of probes via their console. When troubles arise, the interface will indicate what is causing these and suggest how to solve it. We expect this new functionality to make partners even more independent while deploying and troubleshooting probes!

One of our ongoing innovation and site reliability engineering projects is to further improve scalability and performance of our platform. This month we expect to be able to run 80% of the Lighthouse platform on new infrastructure locally. While there's still a lot of work to be done, we expect to deploy the revised architecture by the end of Q2, 2023 at the latest.

In the past few weeks we also fixed some bugs and implemented improvements:
Hacker Alert Exclusions will be deleted at the same time a Hacker Alert Appliance is deleted
The contract index has been updated
Scanning for SNMPvx services has been improved

Finally, our UX-Engineer Martin is still working on the new Lighthouse interface. We expect to share an update on this in the next Partner newsletter, so stay tuned!

Guardian360 Partner Program 2023

When we came up with our first Partner programme in 2016, the information security market looked completely different from what it does today. Over the past few years, we have therefore kept updating our partner programme. For next year, however, we want to introduce a completely new partner programme with the main theme:

"We support Partners to present themselves as information security authorities to their clients"

2023 will see an increased focus on positioning Partners who have a clear vision regarding information security. We will introduce new training courses for Partners, organise workshops and lunch & learn sessions for clients, and introduce new Partner statuses.

Keep an eye on our partner newsletter!

Reference case Innovam, SLTN and Guardian360

Innovam, a training provider in the mobility sector, has chosen SLTN as its partners of choice since 2008 when it comes to infrastructure, workstations and also increasingly security. The importance of ICT for Innovam is connecting all primary processes and securing data of the business, end users and trainees alike. In a video, Maarten van den Berg, ICT project leader at Innovam, explains more about this collaboration and how SLTN deploys Guardian360 to secure Innovam even better.

G360DAO Update

We are currently collaborating with EY(Ernst & Young) regarding strategical, legal and tax focal points that are required to launch G360DAO as a legitimate legal entity. In the past weeks we discussed the business model, tokenomics, governance and community building. We are currently processing information gathered from intense weeks and substantial debates with EY representatives. We are thrilled that EY member firms globally are contributing to provide insights from people acting in the crypto vanguard in at least 15 different countries.

Besides the work done with EY, we

organised our first community event, the recording can be found via Discord
Jan Martijn presented G360DAO during the 'How to DAO it 2' event in Utrecht

Olivier will publish his blog regarding the G360DAO Bucket Voting system this week, you'll find it on our mirror page.

The boy who cried wolf

The story in Aesop’s fables, "The boy who cried wolf" is one of the most popular fables among children and storytellers. Once upon a time, there was a shepherd boy who used to take his flock of sheep to the hill to graze on the fresh green grass. Sitting there, he had nothing to do the whole day. One day, an idea struck him. To overcome his boredom, he cried out, "Wolf! Wolf!" All the men came running with their sticks and to their dismay found no wolf! The boy laughed.

For those of you who don’t know the story, I am sure you can guess what happened when the real wolf appeared…

I don't want to pretend that information security professionals do nothing all day, but in my opinion, they are sometimes too quick to communicate alarmingly, when in many cases this is not necessary.

This worries me because it may make system administrators, network engineers and application administrators less sensitive to real alarms and therefore do not act quickly when it is really necessary.

Vulnerabilities are also published without a fix, giving malicious actors a head start. Something that rightly causes concern among system administrators, network engineers and application administrators.

I sadly observe that many information security professionals increase panic by immediately communicating that these vulnerabilities must be fixed as soon as possible, while sometimes this is far from correct and that some vulnerabilities can only be found amongst a small number of customers. Consider Log4J and OpenSSL3 as examples.

Because of this, the Guardian360 team is reluctant to communicate and prefers to do a bit more research before commenting on the severity of a vulnerability. Hopefully, more and more information security professionals will follow us!