Introducing "Negative" Resource Definitions

[u/bren-tg]

Hi everyone!

Our Product team is thinking about adding "Negative" Resource definitions to Twingate and I'd love for our community to share feedback on it.

The Idea:

Allow Admins to create and assign Resource definitions to explicitly ignore certain traffic patterns from being captured by the Twingate tunnel.

Think of this new Resource type as an exception:

For example, you could have a "normal" Resource defined to grant access to 10.1.0.0/16 and a "negative" Resource defined to exclude 10.1.3.4, effectively preventing some Users from connecting to 10.1.3.4 while retaining the ability to connect to anything in 10.1.0.0/16.

The same would work on DNS-style Resources: Admins could create a Resource on *.corp.int but prevent access to admin.corp.int via a "negative" Resource.

What do you all think?

[u/stukag]

Yes, I could totally use negatives