Douglas Bodden

Raw telemetry can overwhelm more than it informs. That’s why organizations are leaning on PacketRanger to make SNMP and NetFlow practical, cost-effective, and compatible with modern monitoring tools. Three ways PacketRanger helps: 🔹 Filter Before You Forward – Keep dashboards meaningful and reduce data costs. 🔹 Translate for Compatibility – Convert SNMP traps into syslog for SIEMs and aggregators. 🔹 Spot Anomalies at the Source – Catch misconfigurations and outages in real time. When SNMP and NetFlow are implemented intentionally, they become powerful tools for clarity and control.

3

Boston-area towns are being hit with more cyber threats – and many still rely on outdated systems and overworked staff 🛠️ Keep your services running: https://lnkd.in/eqsRS6_G #MunicipalIT #BostonGov #Cybersecurity

3

#HostingJournalist #Colocation DataBank has acquired the physical facility that houses its EWR2 data center in Piscataway, New Jersey, signaling a strategic shift from leasing to ownership within its infrastructure portfolio. The move underscores DataBanks long-term investment strategy and aims to increase operational control, scalability, and reliability for clients relying on the site for mission-critical applications. EWR2, one of several edge data centers operated by DataBank across the U.S., provides colocation, connectivity, and managed services for enterprise and institutional clients. Among its key tenants is the New Jersey Institute of Technology, which runs its Wulver High-Performance Computing (HPC) environment within the facility. The acquisition is expected to enhance DataBanks ability to meet the growing demand for compute-intensive workloads by offering improved stability and room for infrastructure expansion. Network Interconnection Points CEO Raul K. Martynek described the acquisition as part of a broader plan to gain control over the real estate supporting DataBanks edge footprint. Ownership allows us to control our destiny, ensuring we can continue to invest in and evolve our facilities in step with our customers' growing infrastructure needs. Located just outside New York City and near major network interconnection points, the New Jersey site would play a strategic role in supporting East Coast digital infrastructure for sectors including finance, education, and research.

1

ATF and Flow Designer live on the same layer. That’s why they work so well together. When you’re testing a flow, you’re validating execution logic: • Does it trigger when Priority = Critical? • Does it route to the correct assignment group? • Does your “Get Manager Details” subflow handle multiple scenarios cleanly? This is all server-side logic and that’s exactly what ATF is designed to validate. Once you’re clear on what layer you’re testing, flow testing becomes simple and structured, not guesswork. This carousel breaks down: ✔ What belongs in a flow test ✔ What doesn’t ✔ Real example test structures you can apply immediately If you’re building flows and want cleaner, more reliable validation patterns, it’s worth a look → #ServiceNow #ATF #FlowDesigner #Testing

6

1 Comment

Networks aren’t just pipes; they’re the lifeblood of digital resilience. The new Splunk ITSI Content Pack for Cisco Data Center Networking completes the picture, giving NOC and ITOps teams unified visibility from branch to data center. Reduce alert noise and gain predictive insights all in one platform. Learn how to power a resilient digital enterprise: https://splk.it/47ooR9b

300

2 Comments

I recently spent six years working on the Tofino security appliance. It is effective, partially because attackers do not know it is there. It is what is called a BUMP-ON-THE-WIRE device. It does not have an IP address. It forwards all traffic that comes in out the other side. It is detectable as a small additional latency on the network. Before I left the company, I wanted to add my background in machine learning so the device would "learn" what normal network traffic looks like, and alert on unusual behavior--the mechanism that Secret Service agents use to protect Mr. Trump in a large crowd. However, the new managers in Germany decided to lay off half of the team without asking us our plans. As far as hardware security goes in the cloud, I was invited to a meeting between Ruby Lee of Princeton University and the VP of research at Intel. Dr. Lee told the VP (he replaced my boss at Intel Labs, Konrad Lai) how to put a "root of trust" in a microprocessor. This root of trust is augmented by TrustForge, which in the property of Agita Labs, one of the companies started by Todd Austin. It changes the key 20 times a second so that if someone finds a way to exfiltrate data from the cloud to break the cryptography, 50msec later, the broken key is useless. This is called _temporal_ security. Cheers! ☕ Todd B. Bittally

1

𝐆𝐞𝐭𝐭𝐢𝐧𝐠 𝐂𝐀𝐍 𝐛𝐮𝐬 𝐝𝐚𝐭𝐚 𝐢𝐧𝐭𝐨 𝐦𝐨𝐝𝐞𝐫𝐧 𝐬𝐲𝐬𝐭𝐞𝐦𝐬 𝐡𝐚𝐬 𝐚𝐥𝐰𝐚𝐲𝐬 𝐛𝐞𝐞𝐧 𝐦𝐨𝐫𝐞 𝐜𝐨𝐦𝐩𝐥𝐞𝐱 𝐭𝐡𝐚𝐧 𝐢𝐭 𝐬𝐡𝐨𝐮𝐥𝐝 𝐛𝐞. Proprietary drivers, vendor-specific gateways, and low-level C code. Just to move data from a vehicle or machine into a dashboard or database. Most teams accept this as the norm. It doesn't have to be. SocketCAN exposes CAN interfaces as standard Linux network interfaces, eliminating much of the hardware-specific complexity. FlowFuse then handles everything on the integration side. MQTT, REST APIs, databases, dashboards, SCADA. All through a visual, flow-based environment. No low-level C code. No proprietary drivers. Just clean, maintainable integrations. I published a full tutorial walking through: 🔹 Setting up SocketCAN on Linux 🔹 Configuring virtual and physical CAN interfaces 🔹 Sending and receiving CAN frames in FlowFuse 🔹 Connecting CAN infrastructure to industrial and cloud systems If you work in automotive, industrial automation, or embedded systems, this is worth a read. https://lnkd.in/e2CWWkhA #IIoT #IndustrialAutomation #CANbus #FlowFuse #Manufacturing #EdgeComputing

20

Clock Domain Crossing; one of those silent killers in chip design I've been thinking about how often we chase complex bugs, only to find they trace back to something as fundamental as CDC issues. Metastability, data corruption, problems that can haunt you all the way to silicon and beyond. What strikes me about modern CDC verification is how it's evolved from a checklist item to a critical verification layer. The structural analysis, the automatic assertion generation, it's not just about finding problems anymore. It's about understanding the architecture deeply enough to prevent them. What I appreciate is the pragmatic approach of Questa CDC: identify the clock domains, understand the synchronizers, catch the issues early. No magic, just solid engineering methodology backed by the right tools. The real challenge isn't just having the technology, it's knowing how to apply it in a way that makes sense for your specific design. That's where the conversation between tool capability and design intent becomes crucial. Anyone else dealing with increasingly complex CDC scenarios in their designs? Would be interested to hear how you're tackling it. https://dub.sh/32U8QyJ #ClockDomainCrossing #Verification #Bugs #Questa

15