<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SecurEnds Deployment Archives - SecurEnds</title>
	<atom:link href="https://www.securends.com/documentation-category/securends-deployment/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.securends.com/documentation-category/securends-deployment/</link>
	<description>SecurEnds - User Access / Entitlement Reviews, Identity Access Management, Cloud Access Management, Identity Governance, IGA, IAM</description>
	<lastBuildDate>Thu, 27 Feb 2025 09:50:10 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://www.securends.com/wp-content/uploads/2022/02/cropped-se-favicon-new-32x32.png</url>
	<title>SecurEnds Deployment Archives - SecurEnds</title>
	<link>https://www.securends.com/documentation-category/securends-deployment/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Architecture Overview</title>
		<link>https://www.securends.com/documentation/architecture-overview/</link>
					<comments>https://www.securends.com/documentation/architecture-overview/#respond</comments>
		
		<dc:creator><![CDATA[Bathool Mohd]]></dc:creator>
		<pubDate>Fri, 11 Dec 2020 16:55:36 +0000</pubDate>
				<guid isPermaLink="false">https://www.securends.com/?post_type=docs&#038;p=6126</guid>

					<description><![CDATA[<p>SecurEnds application is built using&#160;Spring Boot. Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can “just run”. We have multiple instances of Spring Boot. The end users interact with SecurEnds through web-based User Interface, which communicates over HTTPS. The UI is developed by using React JS. SecurEnds Application is typically deployed on&#160;AWS EC2&#160;Instance but can be deployed on other IAAS such as Azure. We employ Elastic Load Balancing to&#160;automatically distribute incoming traffic across multiple targets, such as EC2 instances, containers, and IP addresses, in one or more Availability Zones. To access AWS , IAM policy with&#160;MFA&#160;(Multi Factor Authentication) is used and Rotate Access Keys are enabled. MFA, or extra authentication controls, is used to combat increasing levels of identity theft.&#160; The Data Base Server is deployed on&#160;AWS RDS. We have two RDS MySQL instances:&#160;CEM&#160;and&#160;CEM Controller. The CEM Controller is a bridge between CEM Application and Agent(Connectors) for event management and data push management. Amazon RDS encrypted DB instances provide an additional layer of data protection by securing data from unauthorized access to the underlying storage. It handles authentication of access and decryption of data transparently with a minimal impact on performance. Amazon RDS encrypted DB instances use the industry standard AES-256 encryption algorithm. Connection between On Premise and Cloud Instances are secured. Generic Agent Installation is required to connect SecurEnds to an on- premise Application Connector. Key Components of SecurEnds SecurEnds allows administrators to perform typical system administration functions including Onboarding SOR/Applications, Campaign creations and performing User Access Reviews. File Uploads, Connectors and Flex Connectors are used to interact with other IT systems. Identity governance&#160;controls user permissions on resources and provides a clear picture of allowed access and potential security risks. SecurEnds gives access to external auditors to view proof of review completion. Campaign reports houses all data related to the campaigns. Identity Analytics features Identity Mind map, Application Mind Map and Entitlement Mind Map which shows the graphical representation of Identities, Applications, Credentials and Entitlements.</p>
<p>The post <a href="https://www.securends.com/documentation/architecture-overview/">Architecture Overview</a> appeared first on <a href="https://www.securends.com">SecurEnds</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>SecurEnds application is built using&nbsp;<strong>Spring Boot</strong>. Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can “just run”. We have multiple instances of Spring Boot. The end users interact with SecurEnds through web-based User Interface, which communicates over HTTPS. The UI is developed by using React JS.</p>



<p>SecurEnds Application is typically deployed on&nbsp;<strong>AWS EC2</strong>&nbsp;Instance but can be deployed on other IAAS such as Azure. We employ <strong>Elastic Load Balancing</strong> to&nbsp;automatically distribute incoming traffic across multiple targets, such as EC2 instances, containers, and IP addresses, in one or more Availability Zones. To access AWS , IAM policy with&nbsp;<strong>MFA</strong>&nbsp;(Multi Factor Authentication) is used and Rotate Access Keys are enabled. MFA, or extra authentication controls, is used to combat increasing levels of identity theft.&nbsp;</p>



<p>The Data Base Server is deployed on&nbsp;<strong>AWS RDS</strong>. We have two RDS MySQL instances:&nbsp;<strong>CEM</strong>&nbsp;and&nbsp;<strong>CEM Controller</strong>. The CEM Controller is a bridge between CEM Application and Agent(Connectors) for event management and data push management. Amazon RDS encrypted DB instances provide an additional layer of data protection by securing data from unauthorized access to the underlying storage. It handles authentication of access and decryption of data transparently with a minimal impact on performance. Amazon RDS encrypted DB instances use the industry standard AES-256 encryption algorithm. Connection between On Premise and Cloud Instances are secured. Generic Agent Installation is required to connect SecurEnds to an on- premise Application Connector.</p>



<div class="wp-block-image"><figure class="aligncenter size-large"><img fetchpriority="high" decoding="async" width="1024" height="638" src="https://www.securends.com/wp-content/uploads/2021/05/Image2.1-1024x638.png" alt="" class="wp-image-8458" srcset="https://www.securends.com/wp-content/uploads/2021/05/Image2.1-1024x638.png 1024w, https://www.securends.com/wp-content/uploads/2021/05/Image2.1-300x187.png 300w, https://www.securends.com/wp-content/uploads/2021/05/Image2.1-768x478.png 768w, https://www.securends.com/wp-content/uploads/2021/05/Image2.1-1536x957.png 1536w, https://www.securends.com/wp-content/uploads/2021/05/Image2.1.png 1734w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure></div>



<h5 class="wp-block-heading" id="0-toc-title">Key Components of SecurEnds</h5>



<ul class="wp-block-list"><li>SecurEnds allows administrators to perform typical system administration functions including Onboarding SOR/Applications, Campaign creations and performing User Access Reviews.</li><li>File Uploads, Connectors and Flex Connectors are used to interact with other IT systems.</li><li>Identity governance&nbsp;controls user permissions on resources and provides a clear picture of allowed access and potential security risks.</li><li>SecurEnds gives access to external auditors to view proof of review completion.</li><li>Campaign reports houses all data related to the campaigns.</li><li>Identity Analytics features Identity Mind map, Application Mind Map and Entitlement Mind Map which shows the graphical representation of Identities, Applications, Credentials and Entitlements.</li></ul>
<p>The post <a href="https://www.securends.com/documentation/architecture-overview/">Architecture Overview</a> appeared first on <a href="https://www.securends.com">SecurEnds</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.securends.com/documentation/architecture-overview/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
