Users connect to a server in the data center for file sharing. The organization wants to decrypt the traffic to this server in order to scan the files being uploaded and downloaded to determine if…

Question

Options

• ASCP Proxy
• BSSL Inbound Proxy
• CSSH Forward Proxy
• DSSL Forward Proxy

• A
  4% (1)
• B
  81% (21)
• C
  12% (3)
• D
  4% (1)

Explanation

SSL Inbound Proxy is correct because the traffic in question flows inward to a server the organization owns and controls. Since the organization has access to the server's private key, the inbound proxy can decrypt incoming SSL/TLS sessions, inspect file content for malware or data exfiltration, and re-encrypt before forwarding to the server - all transparently to users.

SSL Forward Proxy (D) is the wrong direction: it intercepts outbound connections from internal users to external servers (e.g., internet browsing), not traffic destined for an internal server. SSH Forward Proxy (C) handles SSH protocol tunneling for outbound connections - a completely different protocol and direction than what's described. SCP Proxy (A) is a distractor referencing SCP (Secure Copy over SSH), which is not a standard proxy inspection mechanism for general file-sharing traffic scanning.

Memory tip: Think "Inbound = I own the destination." When YOUR server is the endpoint and you hold its private key, use SSL Inbound Proxy. When your users are the source connecting outward to the internet, use SSL Forward Proxy.

No community discussion yet for this question.