Is standard RADIUS safe enough to use?
For EAP-TLS, yes, if you look after two things. The certificate and the keys from it are exchanged inside the TLS handshake, so someone watching the RADIUS packets can't read them. They can see which device asked, which access point or switch it came through and the result.
The two things are the shared secret and the network path. Treat the secret like a password. Passbeam generates a long one for you. Don't reuse it between sites or paste it into a ticket. And use a network path you control where you can.
Passbeam ignores requests from any address that isn't registered for a site, before doing any other work, so a scan from the internet gets nowhere. Even so, RADSec is the better choice. Use standard RADIUS where the equipment doesn't support RADSec.
Related questions
- RADIUS or RADSec: which should I use?
- What address and port do I point my equipment at?
- How do I set up Cisco Meraki with Passbeam?
- A printer keeps failing with a TLS error. Why would I let a site accept older TLS?
- A camera or printer is still refused after I allowed older TLS. What now?
- Can Passbeam authenticate our VPN as well as the network?
- Our VPN concentrator serves several clients from one address. Will Passbeam tell them apart?
- Can I let only some people use the VPN, but everyone use the office network?
- Can I require a second factor on the VPN?
- Do you support PEAP, MSCHAPv2 or EAP-TTLS?
- Do you support RADIUS accounting?
- How do I disconnect a device that is already connected?
- What firewall rules does the connector need?
Still stuck? Ask us, or read the rest of the knowledge base.