Web application

There are various options for protecting your web application using Knocknoc

~~Firewall~~Local Linux firewall orchestration on the host (eg: using IPSets)

In-line firewall/control device orchestration (Fortigate, etc), via an adjacent Knocknoc Agent deployment

HAproxy can sit in front of the web application(s) and forward authorised traffic

Public cloud orchestration (AWS, Azure)

~~Provide~~One ~~reference~~major ~~examples~~advantage ~~using~~of ~~relevant~~Knocknoc ~~backends~~particularly for ~~example~~legacy ~~haproxy,~~web ~~ipset~~applications without single-sign-on or ~~AWS~~where ~~Security~~shared ~~Groups~~passwords are forced (eg: ICS/OT network equipment, embedded systems, soho routers etc) is that SSO and MFA are quickly added to these back-ends without change.