looks sane to me…
I have a few questions being the secure network geek I am…
- How is the remote monitoring/control and logging of this SAFE NPM Module health state planned/designed to be managed/debugged interactively by support staff when the need arises?
fyi- Apstra claims they have autonomous networking all figured out with L2 VXLANS over Secure IP in the DC, however I can tell you there will always be a need for the above.
Has anyone looked at Log4j like type capability a la Winston having what this module will generate as health/state info in log form to have it equipped with a false positive filter on a smart restful api which can send module generated health/state data as accumulated to 2 or more running Management App Nodes living in a Support Network CUG using mcast/groupcasts organized as Layer 5/4 to send it out so the info can be accessed/analysed and re-routed stored other Vaults for later reference/analysis/reporting by support staff via their Browsers?
Any thoughts using C2 like management of this module logging of health info/state to ensure a secure chain of custody through the network so the log info cant be faked by a rogue module?
Other info which might be useful:
Also if anyone is interested there is a LGPL V2 licensed project still accessible on sourceforge.net (sf.net) called “Sherlock” that we (ex-Platespin core founding engineering group) created back in 2004 using Log4J to collect syslog relay data from network devices which was C2 compliant (milspec stuff) and stored in C2 compliant and organized flat file hierarchy with a back end post-processor written in Perl using Regex to dump to a RDBMS so we could get at it with a report server, it might be useful as a reference…