Level up your business security with free, on-demand training and certification. Explore 1Password Academy today β
Feature Request - Step Up Auth Geo-restrictions
We are starting to have more users working overseas temporarily from locations outside our usual allow list. We'd like a middle ground option to allow these locations but only with an additional authentication factor, or allow them for a small number of users.
Kolide Custom Checks?
Hi everyone, We have rolled out 1Password XAM and are really liking the Kolide Device checks. However we are running into edge-cases where we need to configure some custom checks and are struggling a bit. For example, we want to allow people with devices owned by other (partner) organisations access to some of our Kolide-protected apps. They have been allowed by their admins to install Kolide but they use a different EDR product that is not covered by the supplied checks. (Ie we use Crowdstrike Falcon, they use Palo Alto Cortex) Has anyone worked out a way to implement this sort of thing? Both in terms of a custom checks for Cortex and an either/or setup for EDR.
Kolide Check Templates
Hi everyone! Can moderators in this community create a space for Kolide Admins to share checks and templates that they use in their environments? This would be similar to the way that Jamf uses Jamf Nation to allow admins to collaborate and share to better secure and protect our environments. Thanks, StevePassword entropy
I would like to see the password entropy when creating a password. For example, What is the strength of this? Consider this article: https://blog.syss.com/posts/passphrases/ It would be very helpful to have some confidence of the strength. Note this password generator doesn't provide any sort of length information. While the specific length may reveal too much information, if this could at least provide a some idea what the entropy is, its better than nothing. Even the character count of the generated password is good feedback. As it is, this feature is designed for novice users and doesn't provide significant confidence when looking for fitting in with technical requirements. Finally, this random password: was generated by 1Password. Rather than simply putting "Weak", given that the generation specs were known, it would be really helpful to include the entropy alongside of this. How "weak" is "weak"? Thank you for the consideration.
BloodHound OpenGraph
Exploring a 1Password instance to map user access to vaults SpecterOps BloodHound is a tool for mapping identities and attack paths for Microsoft products, but has added OpenGraph to do the same for other products , with one of the first examples being 1Password. What is our Bloodhound users' experience with this new tool? How does this compare to using the native tools? I have no affiliation with SpecterOps or experience with their products, but am interested in identity and access discovery in an information security context.
