<story><title>Restrict Access to your internal websites on AWS with BeyondCorp</title><url>https://transcend.io/blog/restrict-access-to-internal-websites-with-beyondcorp</url></story><parent_chain></parent_chain><comment><author>Znafon</author><text>The BeyondCorp paper explicitly mentions that the device state is taken into consideration when giving access to a user, i.e. that the device is identified and controlled, not just the user. It seems to me like it is an important part in the BeyondCorp access model, otherwise wouldn&amp;#x27;t this just be a SSO portal?</text></comment>
<story><title>Restrict Access to your internal websites on AWS with BeyondCorp</title><url>https://transcend.io/blog/restrict-access-to-internal-websites-with-beyondcorp</url></story><parent_chain></parent_chain><comment><author>code4tee</author><text>A lot of companies that care deeply about security are moving to this “trust no one” approach which has the added benefit for end users of allowing access to “secure internal sites” over the plain old internet. If done right this can all be a big boost for security and improved end user experience. That said, the old “you need to be on the VPN” approach is going to stick around for some time.</text></comment>