Third-Party Monitoring and Reporting

. . . a new name for a long-standing service.

The latest edition of Executive Vice President, Michael Hartke’s article series!

super heroes punching bad guy with POW, saying

Two of Dan’s articles, What’s in a Name and Interagency Wisdom, have pointed out something that we fight with here at infotex.

We are regularly developing new services and features to respond to the needs of our Clients – most of them in highly regulated industries. While we pride ourselves in the ability to customize our approach to best fit our Clients’ needs, we often fall flat when it comes to the naming of these beneficial services and marketing them. Allow me to induce some personal cringe by providing some examples.

We started a feature of our Security Information and Event Management (SIEM) in 2008 called Put A Watch (PAW) and Private Put A Watch (Private PAW) where we will monitor a person, endpoint, service, really anything available in IDS/ELM traffic and provide reports and real time events to our Clients on our 24×7 SOC. The Private PAW was just another option with that service that would allow a separate commutation layer for supervisory personnel like Risk Officers, Board, etc. if you are concerned about someone with elevated access and/or sensitive situations.

But even before that service existed we had already included what others now call third-party monitoring as a standard SIEM service and suggested it in our tuning/deployment of new and existing Clients.

Vendor Management is another example though not poorly named, this service is now Third-Party Risk Management (TPRM).

Our SIEM started as Logmon (Dan likes to joke about how they just got back from a vacation to Jamaica). The latest version of our NG-SIEM was originally named SIEM3, as it was our 3rd major backend rebuild and we started developing it five years ago, so it just stuck internally (I actually like both of those but I’m far from impartial).

Our Vulnerability Management Program Development and Training services was once called Conference Room Scanning.

Don’t even get me started on Managed / Extended / Endpoint Detection and Response (M/X/EDR). We can’t take credit for this one though and as you know if you have read my other articles, we find this service invaluable to our Clients.

We do have a list of what we feel are wins. Rogue Device Detection doesn’t make us cringe and, like many of our other services and features, has been imitated since we introduced it in 2017.

I really like our new Incident Response Test service that we are calling Blue Team Exercises, where we are taking IRT’s to the next level by bringing in more technical and security professionals.

My joy today is to bring one of our legacy services into the NG-SIEM feature set properly. Without further ado, I’d like to announce that we are officially changing the name of our service from Put A Watch to what the industry might more easily recognize as Third-Party Monitoring and Reporting and have added for all NG-SIEM/MSOC Clients.

You can reach out to our 24×7 SOC to set up your Third-Party Monitoring and Reporting today!

Original article by Michael Hartke. Executive Vice President, infotex

Interested in any of our services? Visit to request more information!



Leave a Reply

Your email address will not be published. Required fields are marked *

Related Posts

Considerations – Why you should choose infotex, Inc. as your next MSOC!

Reasons why we should be considered! infotex provides a number of services that can be checked out if you click over to! We even made a movie with all the reasons why infotex...

The Magnificent Seven 2023

Seven Trends . . . …that small bank Information Security Officers face in 2023 Another one of those Dan’s New Leaf Posts, meant to inspire thought about IT Governance . . . . Welcom...