English
Open in Telegram

Post 🔗 Third-Party Risk — Part 3

20 September 2026
N
netbotter
🔗 Third-Party Risk — Part 3 𝗧𝗵𝗲 𝗵𝘆𝗴𝗶𝗲𝗻𝗲 𝘁𝗲𝘀𝘁 If a vendor can't keep its certificates valid, what else isn't being maintained? Basic security hygiene is the most reliable indicator of how a vendor runs its operation. 🧹 Certificates renewed on time → someone is maintaining the infrastructure. 🧹 Current software versions → patches are being applied. 🧹 No default credentials or test pages → services are configured for production. The inverse is equally telling: 🚩 Expired certs across multiple hosts → systemic neglect. 🚩 Software versions years behind → no patch management. 🚩 Factory-default admin pages on the internet → no hardening process. This isn't about catching one mistake. Everyone has a bad day. It's about 𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀. A vendor with consistent hygiene is a very different risk profile from one with systemic gaps.
83 ·

Nearby in the feed

Nnetbotter🔗 Third-Party Risk — Part 1 𝗬𝗼𝘂𝗿 𝘃𝗲𝗻𝗱𝗼𝗿𝘀' 𝗮𝘁𝘁𝗮𝗰𝗸 𝘀𝘂𝗿𝗳𝗮𝗰𝗲 𝗶𝘀 𝘆𝗼𝘂𝗿𝘀 A new series. You did everything right. Your vendor didn't. The breach is still your problem. Nnetbotter𝗢𝗯𝘀𝗲𝗿𝘃𝗮𝗯𝗹𝗲 𝘀𝗶𝗴𝗻𝗮𝗹𝘀 A questionnaire tells you what the vendor claims. Their infrastructure tells you what's true. You don't need a vendor's permission to see the
this message
Nnetbotter🔗 Third-Party Risk — Part 4 𝗦𝗵𝗮𝗿𝗲𝗱 𝗶𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 Your vendor shares an IP with six other companies. One of them is compromised. Now what? Not every vendor runsNnetbotter🔗 𝗧𝗵𝗶𝗿𝗱-𝗣𝗮𝗿𝘁𝘆 𝗥𝗶𝘀𝗸 — 𝗣𝗮𝗿𝘁 𝟱: 𝗧𝗵𝗲 𝗰𝗵𝗮𝗶𝗻 𝗯𝗲𝗵𝗶𝗻𝗱 𝘁𝗵𝗲 𝗰𝗵𝗮𝗶𝗻 𝘠𝘰𝘶𝘳 𝘷𝘦𝘯𝘥𝘰𝘳 𝘢𝘴𝘴𝘦𝘴𝘴𝘦𝘥 𝘵𝘩𝘦𝘪𝘳 𝘷𝘦𝘯𝘥𝘰𝘳𝘴. 𝘉𝘶𝘵 𝘥𝘪𝘥 𝘵𝘩𝘦𝘪𝘳 𝘷𝘦𝘯𝘥𝘰𝘳𝘴 𝘢𝘴𝘴𝘦𝘴𝘴 𝘵𝘩𝘦𝘪𝘳𝘴? Third-party risk doesn't stop a
Nnetbotternetbotter@netbotter · channel · Tech
280subscribers160posts in the index
Venue feed Open in Telegram

An open public feed from the search index ChatCrawler — “Google for public Telegram”; refreshed as the venue is crawled. Times are UTC.

Public content only, official Telegram API. About · FAQ · Index limits · Remove a page · Catalog · Search · How we count