SG UTM

Suggest, discuss, and vote on new ideas for SG UTM. The ultimate network security package.

SG UTM

Suggest, discuss, and vote on new ideas for SG UTM. The ultimate network security package.

Suggest an Idea...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Support for Industrial Protocols in DPI / IDS

    We are fairly recent Sophos partner, our business is in industrial automation and control systems customers.

    Security for industrial automation, critical infrastructure, and industry 4.0 is very much a hot topic right now.

    We would like to see some development to include capability for Deep Packet Inspection and control of industrial control protocols such as:

    Modbus TCP
    Ethernet/IP (CIP)
    OPC Classic (DCOM / RPC)
    Siemens S7
    etc.

    Inclusion of rules for these into IDS would also be welcomed.

    A number of vendors approaching us are starting to get into this specialist area of the market and it would be great…

    6 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
  2. Uplink Balancing & NAT Masq

    Problem: You may create NAT Masq rules for your ISP and segment off portions of your network to specific addresses under Network Protection > NAT. If you obtain a secondary ISP and turn on uplink balancing under Interfaces & Routing > Uplink Balancing, your NAT MASQ rules change to uplink interfaces. The NAT MASQ rules only MASQ the primary interface. The current interface doesn't allow for changing to multiple interfaces.

    Solution: Allow uplink balancing to be used and allow multiple interfaces to be configured under the MASQ ruleset so that traffic may use either configured interface to NAT MASQ.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow us to enable Firewall and NAT rules from within the Edit rule

    By default you don't enable the rules yet you don't have the option to enable the rule when you create it... ! Please add this option at the bottom so we don't have to remember to click the rule on after we create the rule we obviously want on.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
  4. Ability to whitelist interfaces from strict TCP session handling

    A customer needs to block spoofed ACK packets on their WAN interfaces in order to pass security policies. In order to do this, they need to enable strict TCP session handling so they can avoid TCP session pickup. This works, however, it's global and causes problems for one of their applications on the LAN side.
    By allowing a whitelist of interfaces to allow TCP session pickup, the customer can meet security requirements without disturbing their application.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
  5. VoIP helper & TLS

    Deutsche Telekom provides TLS-Support with their "SIP-Trunk". This can't be used with the SG's VoIP helper and telephony systems connected to the LAN.
    Please enable SSL/TLS interception for the VoIP helper.

    6 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
  6. Notify me when unauthorised devices appears in default VLAN - when DHCP is used

    Unconfigured Switch ports have the default VLAN, which is not in use - but the UTM has a DHCP to hand out IP Addresses. When this happens, this must be unauthorized - so I would like to get a notification.

    3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
  7. Packet filter: allow wildcard subdomains

    Firewall packet filtering based on wildcard subdomains and reverse DNS resolution.

    Would like to allow/deny connections, using the packet filter, based on a wildcard subdomain (think *.example.com).

    10 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
  8. Detect port scans using an XG and automatically block the source IP

    The XG firewall should be able to detect port scans when they occur and then have the ability to block the source IP.

    3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
  9. L2TP over IPsec via IPv6

    L2TP over IPsec is currently only working via IPv4. Please support IPv6 as well.

    5 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
  10. Pi-Hole

    I'd like to see Pi-Hole integrated into the UTM. Pi-Hole is an application that allows you to filter DNS requests based on settings you can set yourself. Its very light weight and should integrate very well within the UTM.

    15 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
  11. Security heartbeat for utm 9.x

    It would be great if you iplement the new security heartbeat into the utm 9.x also.

    14 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
  12. Block IP's using Blacklist/Blocklist Service

    Support the use of Blacklists/blocklists. Note that this feature was requested at link below and apparently Sophos thought that ATP would satisfy the need, however it does not provided the requested functionality, Therefore I am re-posting this as a new suggestion.

    The old suggestion was marked as implemented by the ATP feature; however ATP is not what was wanted and generates too many false alerts. This is the prior feature request: http://feature.astaro.com/forums/17359-utm-formerly-asg-feature-requests/suggestions/1982075-network-security-block-malicious-botnet-bad-ip-s

    Plain and simple: We want support for blocklists. Such as those found here: https://www.iblocklist.com. I would also like to specify a blocklist per network. So for example…

    73 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    18 comments  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
  13. Better Firewall Rule Search

    In the search area, it would help to find a Rule, if we can filter from Source net to Destination net.
    For example: Show me all Rules from internal to DMZ, or internal to Any, DMZ to VPN...

    5 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
  14. Expire date for firewall rules

    Firewall rules should have an optional expiry date. This is useful, if a firewall rule has only been approved for a certain period of time.

    With this feature the firewall admin no longer needs to schedule in a separate calendar the removal of a temporary rule and then perform a manual task.

    This results in a cleaner ruleset and less effort for the firewall admin.

    31 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
  15. Firewall Rules counter

    Add a feature that is common and very useful on most firewalls, The display of active counters on firewall rules. This is a quick and useful way to trouble shoot firewall rule issues.

    5 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
  16. NOT filtering for firewall rules (and anywhere else with rules)

    Could we have the Firewall interface modified to allow us to apply an inverse rule - that is, filter traffic that does not match the criteria we have put forward. Especially since IPtables can do inverse filtering just fine.

    It'd be nice if we could also do the same in the Exceptions tab for various protections, that would make them much more powerful.

    2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
  17. Allow user-defined rules to be applied before built-in rules

    There is a strong need to be able to prevent access to several protocols that have proxies implemented in ASL (e.g. SMTP).

    Currently, the fact that built-in rules are always applied before user-defined ones has the following consequences:
    - It is impossible to prevent access to one of these proxied services alone. The only option is use blackhole routing (which prevents all trafic from and to the targeted networks).
    - It is very much unclear to the user why a given rule isn't applied. Instinctively, an explicit "deny" rule should always apply before any and all "allow" rules. This rather…

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
  18. Country Blocking By Top Level Domain Not IP

    Right now country blocking only blocks by IP address, so if I block .ga (Gabon), but the website is registered with a U.S. ip address, the website is allowed for end users.

    Solution: add an option to block countries by top level domain (ex. .ga for country Gabon) without having to create a rule to create a black list and try to use a expression to block based on every domain. Reference ticket #8225803 - Kerry Albert
    Channel Sales Engineer
    Kerry.albert @ sophos.com

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
  19. Introduce Behavior and Reputation Based IPS Signatures

    There are Snort based IDS rule sets that provide behavior and reputation based rules which do not currently appear to be available in the UTM. Current IPS rules are insufficient to detect connections from known malicious hosts. Further, we have experienced fairly large brute force attacks against open RDP ports (business requirement) , that went undetected by the UTM IPS.

    Example Rules:
    Emerging Threats - ET CINS Active Threat Intelligence Poor Reputation series signatures
    Emerging Threats - ET SCAN Behavioral Unusually fast Terminal Server Traffic

    2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
  20. Implement DNS Blacklist in the DNS Server, not the IPS subsystem.

    IPS blocks queries to resolve untrusted host names. This tells the client that the DNS server has failed, not that the query should not be resolved. Consequently, the client immediately re-attempts the query using a different path. The consequences of having no response from all DNS servers will be implementation specific and therefore unpredictable.

    Instead, we need UTM to return a non-existent domain result (NXDOMAIN), so the client stops trying to resolve the name at all. This is how Quad9 is described to work. To produce this result, the blacklist has to be moved out of IPS and into the…

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Network Protection  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 9 10
  • Don't see your idea?

Feedback and Knowledge Base

icon-data-protection icon-endpoint-protection icon-phish-threat icon-sophos-central icon-sophos-central icon-sophos-central icon-sophos-central icon-sophos-central icon-sophos-central icon-sophos-central icon-sophos-mobile icon-sophos-utm icon-sophos-utm icon-sophos-utm icon-web-appliance icon-xg-firewall icon-xg-firewall icon-avid-secure icon-lightbulbCreated with Sketch.