How would a Security policy need to be written to allow outbound traffic using Secure Shell (SSH) to destination ports tcp/22 and tcp/4422?

Question

Options

• AThe admin creates a custom service object named "tcp-4422" with port tcp/4422.
• BThe admin creates a custom service object named "tcp-4422" with port tcp/4422.
• CThe admin creates a custom service object named "tcp-4422" with port tcp/4422.
• DThe admin creates a Security policy allowing application "ssh" and service "application-default".

• A
  6% (1)
• B
  12% (2)
• C
  76% (13)
• D
  6% (1)

Explanation

The built-in 'ssh' application uses 'application-default', which only permits tcp/22. To also allow SSH over the non-standard port tcp/4422, the administrator must create a custom Service object (e.g., 'tcp-4422') defining port tcp/4422, then reference both the 'ssh' application and the custom service in the Security policy. Using 'application-default' alone (choice D) would block tcp/4422 since it is not a default port for SSH. The correct approach combines explicit application identification with a custom service object to cover both ports.

No community discussion yet for this question.