Page MenuHomePhabricator

Audit members of acl*security for more than x duration of no activity (Jan 2022)
Closed, ResolvedPublic

Description

Same as T241781.
See output of SELECT DISTINCT(userName) FROM phabricator_user.user WHERE phid NOT IN (SELECT trs.authorPHID FROM phabricator_maniphest.maniphest_transaction trs INNER JOIN phabricator_user.user u WHERE FROM_UNIXTIME(trs.dateModified) >= (NOW() - INTERVAL 1 YEAR) AND trs.authorPHID = u.phid) AND phid IN (SELECT e.src FROM phabricator_user.edge e WHERE e.dst = "PHID-PROJ-koo4qqdng27q7r65x3cw" AND e.type= 14); on phab1001 (not sure if I should directly post here in public?).

Ideally this wouldn't require a human to think of it and file this manual ticket.

Event Timeline

I can take this on, but I don't think I have access to run the query. I don't see a way to get the equivalent result through the Phabricator GUI.. Can the query results be added here, or should I pursue trying to get the least amount of access I would need to run that query myself?

@Dsharpe: I've pasted P18895. (Note that this list of folks who have not had any task related activity at all in the last 12 months also includes deactivated accounts, and bots.)

Thanks for that list! Skipping over some folks who need access but might not actually update a task, I removed access for anyone that showed up somehow under the security acl who no longer need that level of access. Some accounts listed didn't show up under any of those groups under the security acl. and I had no edit to make for those.

Thanks. I see that three accounts were removed.

Some accounts listed didn't show up under any of those groups under the security acl.

Hmm, that makes me wonder if my query is correctly constructed... sigh. Anyway, thanks! :)

Dsharpe removed a project: Security-Team.

Because I couldn't think of a better way to do it, I added a personal calendar entry for myself to do this again next year. Thank you!

Because I couldn't think of a better way to do it, I added a personal calendar entry for myself to do this again next year. Thank you!

@Dsharpe: Thanks! Would it make sense to create a followup Phab ticket which mentions 2023 in the title, set stalled status, and set a Due Date, so remembering this would not depend on a single person's calendar but would be future work on a list/workboard that an entire team could become aware of?