Making PicoPaaS harder to abuse: egress blocks, a bandwidth cap, and terms
We made the platform harder to abuse: more outbound ports and address ranges are blocked, each app gets an outbound bandwidth cap, and there are now terms of use.
Tenant apps run arbitrary public images, so the realistic abuse is outbound traffic: scanning, floods, relaying. We shipped three layers.
Egress rules
The internet rule now excludes reserved ranges (CGNAT, multicast, loopback and others) as well as private and metadata addresses. We also block scanner, worm and botnet ports (telnet, SMB, RDP, NetBIOS/RPC, IRC) and UDP amplification vectors (SNMP, SSDP, memcached, CLDAP and friends). SMTP was already blocked. We left SSH and NTP open on purpose, since blocking SSH breaks real apps.
20 Mbit/s outbound cap
Every app is now limited to 20 Mbit/s of outbound traffic, enforced on the pod with Cilium's bandwidth manager. It counts everything your app sends, including responses to visitors, so download-heavy apps will feel it. Inbound is uncapped. Admins can raise it per app, up to 160 Mbit/s.
Terms
There are now terms of use with an acceptable use section and an abuse reporting contact, linked from signup and the footer.