insecurelycans

Insecurelycans is a term used in cybersecurity discourse to describe a class of insecure Controller Area Networks (CANs) deployed in embedded and automotive systems. The term captures configurations in which core security controls—such as message authentication, access control, and secure firmware update mechanisms—are missing, weak, or improperly implemented. The concept emphasizes how the CAN protocol’s emphasis on real-time reliability and simplicity can leave networks vulnerable to abuse if not properly secured.

Characteristics of insecure CAN deployments typically include a lack of encryption, absence of integrity checks on messages, and a fully broadcast bus that permits arbitrary nodes to observe or inject traffic. The environment often includes legacy hardware, limited compute resources, and constrained bandwidth, making retrofits and cryptographic protections challenging. The term is not standardized and appears mainly in informal discussions and some research papers to contrast insecure configurations with secure CAN architectures.

History and usage: the phrase began appearing in security discussions as researchers highlighted widespread legacy CAN deployments with limited or no security features. Demonstrations in academic and industry talks have shown how unauthorized devices connected to diagnostic interfaces or gateways can influence vehicle and industrial-control systems by injecting falsified messages, spoofing nodes, or delaying legitimate communications.

Mitigation and response: reducing the risk of insecurelycans involves adopting security enhancements for CAN environments, such as implementing message authentication or cryptographic checks, introducing gateways that enforce policy between CAN and external networks, segmenting critical networks, deploying intrusion detection, and ensuring secure boot and firmware updates. Transitioning from legacy CAN to more secure architectures remains resource-intensive but is widely regarded as essential for safety-critical applications.