[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1779052711943.jpg (112.53 KB, 1080x720, img_1779052703037_h8udf92m.jpg)ImgOps Exif Google Yandex

d00d2 No.1611

Ever asked your EDR vendor for an SBOM or source code access? A recent study did it for 14 of them. Most security teams evaluate EDR-EPP based on detection rates and remediation features. But what about transparency? What data actually leaves your network? Can you review the code? Do you control updates? AV-Comparatives (commissioned by the Austrian Economic Chambers) looked at 14 leading cybersecurity vendors - including CrowdStrike, Microsoft, SentinelOne, Trellix, Kaspersky, Cisco, and others - on criteria that rarely make it into product brochures: Ability to review source code SBOM (Software Bill of Materials) availability Telemetry control and opt-out options Staged update rollouts On-prem reputation services Data residency and legal compliance The results are uneven. Only 3 vendors allow enterprise customers to review source code. Only a handful provide SBOMs. Just 8 out of 14 offer staged updates - which matters a lot after the CrowdStrike incident. The full report (including a breakdown by vendor) is available through AV-Comparatives. Link in the first comment if anyone wants to dig through the methodology.

https://dev.to/danielvisovsky/what-14-edr-vendors-wont-tell-you-about-source-code-sboms-and-update-controls-4680

36466 No.1612

File: 1779053353610.jpg (75.77 KB, 629x800, img_1779053339052_qgqpbs6x.jpg)ImgOps Exif Google Yandex

what if more transparency leads to security risks? do you think vendors should balance between openness and protection in their source code access policies?
>for a hypothetical trade-off consideration.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">