Application Management (part 3)

By Ashwin Venugopal -


 


To read part 1, please click here
To read part 2, please click here





Azure AD Application Proxy

The following diagram shows how Azure AD enables secure remote access to your on-premises applications:




Security Benefits

The following security benefits are provided by Azure AD application proxy:
  • Authenticated access- If you select Azure AD pre-authentication, then, authenticated connections only can access your network.

  • Conditional access- Apply richer policy controls before connections to your network are established. 

  • Traffic termination- All traffic can be terminated in the cloud.

  • All access is outbound- You are not required to open inbound connections to the corporate network. 

  • Cloud-scale analytics- as well as machine learning- Get cutting-edge security protection.

  • Remote access as a service- You don't have to worry about maintaining and patching on-premises servers.

  • DDOS prevention- Those applications who are published through Application Proxy are protected against Distributed Denial of Service (DDOS) attacks.     

Secure Hybrid Access

Nowadays, your on-premises and cloud legacy authentication applications can be protected by simply connecting them to Azure AD with existing application delivery controller or network which in turn, will help you to bridge the gap as well as strengthen your security posture across all applications with Azure AD capabilities such as Azure AD Conditional Access and Azure AD Identity Protection.

Hence, your legacy applications that are critical to your business processes can be easily protected with the help of your existing networking and delivery controller providing you with everything needed to start protecting these applications. 











To read part 1, please click here
To read part 2, please click here


Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more