Menu
TRASA Logo
CommunitySecurityDocsTry Now
TRASA Logo
  • Community
  • Security
  • Docs
  • Try Now
  • Getting Started
    • Overview
    • Concepts
    • How does it work ?
    • Glossary
  • Install
    • Installation
    • Initial Setup
  • Tutorial
    • Introduction
    • Part 1 - Setup TRASA server and root account
    • Part 2 - Create User
    • Part 3 - Create Policy
    • Part 4 - Protect Services
    • Part 5 - Test access to services
    • Part 6 - Monitoring Access
    • Advance Configurations
  • How to Access ?
    • Dashboard Login
    • Second Step Verification (2FA)
    • SSH
    • Windows/RDP
    • Web Service (https)
  • Providers
    • Introduction
    • users
      • LDAP
    • vault
      • TsxVault
  • Users
    • Introduction
    • Creating and updating users
    • Account Setup
    • Change Password
  • Device Trust
    • Enrol 2fa Device
    • Enrol Workstation
  • Services
    • Overview
    • Privilege
    • Web Service (HTTPs)
    • RDP
    • SSH
    • Radius Server
  • Policies
    • Introduction
    • Basic Policy
    • Device Policy
    • Adhoc Policy
  • Access Map
    • Access Mapping
    • Dynamic Access
    • Adhoc Access
  • Access Proxy
    • Introduction
    • Access Proxy vs Direct Access
  • Two Factor Authentication
    • Introduction
    • Windows
    • Linux
  • System Configurations
    • FCM Setup
    • Email Setup
    • Config

Access Proxy

Access proxies are core server components in TRASA. Users typically access protected services via access proxies. Access proxies give us full visibility at the application layer (Layer 7 OSI) and enforce more granular policies.

Currently, TRASA supports four types of protocol.

  1. HTTPs
  2. SSH
  3. RDP
  4. Database (beta, Mysql only)

You need to configure firewall rules to enforce remote access to servers only from TRASA.

Edit this page
Previous
« Adhoc Access
Next
Access Proxy vs Direct Access »
Copyright © 2021 TRASA by Seknox Pte. Ltd.