SecurityInsight settings · Settings > Collection scope & limits
Users' sign-in methods: read again after (days)
| Key | SI_Identity_SignInMethodsMaxAgeDays |
|---|---|
| Where | Settings > Collection scope & limits > Users' sign-in methods in full |
| Type | int |
| Default | 90 days |
| Edition | Community |
What it does
How old a user's full sign-in method detail may get before the background read reads that user again, even when the registration report says nothing changed (it also catches changes the report does not show, such as a renamed device).
When set
Lower: details are fresher, and more of each 15-minute slice goes to reading users again (at 150,000 users and 90 days, about 1,700 users a day). Higher: fewer reads. A user whose registered methods changed is read again at once, whatever this is.
When blank or default
Left blank, the default applies: 90 days
Risk and how to reverse it
A long age keeps details such as device names and app versions older; a short one spends more of the background reading on users that did not change. No data is lost either way. Reversible at once.
Requires
SI_Identity_SignInMethodsPerUser all or privileged. Works only while "Users' sign-in methods in full: which users are read" is on.
Recommended
90 days (the default).
Documented for SecurityInsight 3.0.79. Written by the SecurityInsight team; Invardia publishes it. · All settings · Security review pack