[GH-ISSUE #795] FEATURE REQUEST: Passwordless authentication policy application and audit #397

Closed
opened 2026-03-02 12:41:54 +03:00 by kerem · 2 comments
Owner

Originally created by @baitsops on GitHub (Feb 27, 2022).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/795

We've been using the password-less authentication for some time and feel the latest iteration of 'number matching' method to be the gold standard in reducing MFA brute force attacks. This is a standard we'd like to apply to our clients over time and feel that CIPP is going to be the best way to apply and audit it's application.

This article shows some of the PS & graph commands and context etc. https://call4cloud.nl/2021/10/mfa-authenticator-forever/

Ideally it would be great to have two modes of implementation. One with the 'displayAppInformationRequiredState' that shows the location and IP and the other just purely the numberMatchingRequiredState. We might choose to not impliment the AppInformation to avoid helpdesk calls over confusion of location/IP etc.

I appreciate it's fairly early (preview) stage of the development.

We remain completely in awe of your support of this project to date.

Originally created by @baitsops on GitHub (Feb 27, 2022). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/795 We've been using the password-less authentication for some time and feel the latest iteration of 'number matching' method to be the gold standard in reducing MFA brute force attacks. This is a standard we'd like to apply to our clients over time and feel that CIPP is going to be the best way to apply and audit it's application. This article shows some of the PS & graph commands and context etc. https://call4cloud.nl/2021/10/mfa-authenticator-forever/ Ideally it would be great to have two modes of implementation. One with the 'displayAppInformationRequiredState' that shows the location and IP and the other just purely the numberMatchingRequiredState. We might choose to not impliment the AppInformation to avoid helpdesk calls over confusion of location/IP etc. I appreciate it's fairly early (preview) stage of the development. We remain completely in awe of your support of this project to date.
Author
Owner

@github-actions[bot] commented on GitHub (Mar 9, 2022):

This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://cipp.app/GettingStarted/Contributions/ . Please notify the team if you are working on this yourself.

<!-- gh-comment-id:1062476667 --> @github-actions[bot] commented on GitHub (Mar 9, 2022): This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://cipp.app/GettingStarted/Contributions/ . Please notify the team if you are working on this yourself.
Author
Owner

@KelvinTegelaar commented on GitHub (Mar 15, 2022):

Implemented in Dev

<!-- gh-comment-id:1068072924 --> @KelvinTegelaar commented on GitHub (Mar 15, 2022): Implemented in Dev
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#397
No description provided.