Verification: Is this the known user who is presenting the endpoint for enrollment? Is this the same endpoint that we have in our inventory? Inventory Inspection: Does it conform with our security requirements? (Note: enrollment isnРІР‚в„ўt the only time youРІР‚в„ўll inspect the endpoint it should happen automatically with every access decision.) Inventory: What corporate-owned or managed endpoints do you have, and who are the authorized users? What other endpoints are you going to allow? You can use bulk enrollment - that is, you can use the list to create entries for each one without your users having to do anything - or you can use self-enrollment, where the users make contact and supply shared data so that you can recognize them. You create a list of entities to be entered into the system that youРІР‚в„ўll use to authenticate them and grant them access (in this case, a list of authorized users and a list of endpoints theyРІР‚в„ўre using).

What Does Enrollment Involve?Р”В®nrollment usually involves a combination of inventory, inspection and verification. In this post, weРІР‚в„ўll talk about enrolling users and their endpoints. Setting up the access proxy and its policies.Marking trusted devices with certificates.Enrolling your users and their endpoints.The steps may not happen in sequential order, but they are generally:

In our previous blog post introducing the BeyondCorp concept, we also discussed what organizations should think about when trying it for themselves. Industry News March 1st, 2017 Wendy Nather BeyondCorp: Enrolling Users andР’В Endpoints

Google beyondcorp paper