Software development platform repository and account discovery
Systems and methods for detecting SDP user accounts that are associated with a company include querying a software development platform for account and repository data based on a customer name for each account analyzing associated account and repository data, generating a score for each account of the plurality of accounts based on the analyzing, the score being indicative of an account belonging to the customer, and labeling one or more accounts of the plurality of accounts as belonging to the customer based on the score.
1 . A method implemented by a cloud-based system, the method comprising steps of:
querying a software development platform for account and repository data, the querying being based on a customer name, wherein the account and repository data include usernames, verification flags, profile photos, website links, a creation date, an update date, and associated repositories, and wherein the repository data comprises a creation date, an update date, and contributors;
for each account of a plurality of accounts, analyzing associated account and repository data;
generating a score for each account of the plurality of accounts based on the analyzing, the score being indicative of an account belonging to the customer, wherein the score is a composite score derived from a combination of attribute scores for a plurality of the profile photo, the username, the website link, and the creation date, and wherein presence of the verification flag or a contributor associated with the customer assigns a maximum score;
labeling one or more accounts of the plurality of accounts as belonging to the customer based on the score; and
responsive to labeling, scanning one or more repositories associated with the labeled one or more accounts for sensitive information to prevent data leakage, and upon detecting the sensitive information, generating an alert or initiating a remedial action.
2 . The method of claim 1 , wherein the account and repository data further include a username, and wherein the analyzing further comprises comparing the username to a customer name via one or more name comparison models.
3 . The method of claim 1 , wherein the account and repository data include a verification flag, and wherein the analyzing further comprises determining, for each of the plurality of accounts, if the verification flag is present.
4 . The method of claim 1 , wherein the account and repository data include a profile photo, and wherein the analyzing further comprises comparing the profile photo to a list of photos of a logo associated with the customer via a photo comparison model.
5 . The method of claim 1 , wherein the account and repository data include a website link, and wherein the analyzing further comprises checking the website link to a known customer website link.
6 . The method of claim 1 , wherein the account and repository data include a creation date, and wherein the analyzing further comprises comparing the creation date to a current date and determining an age of the account and repository data.
7 . The method of claim 1 , wherein the account and repository data include an update date, and wherein the analyzing further comprises comparing the update date to a current date and determining a duration between the current date and update date.
8 . The method of claim 1 , wherein the account and repository data include one or more contributor details, and wherein the analyzing further comprises determining if the one or more contributor details belong to the client via a verification contributor detail model.
9 . A non-transitory computer-readable medium comprising instructions that, when executed, cause one or more processors to perform steps of:
querying a software development platform for account and repository data, the querying being based on a customer name, wherein the account and repository data include usernames, verification flags, profile photos, website links, a creation date, an update date, and associated repositories, and wherein the repository data comprises a creation date, an update date, and contributors;
for each account of a plurality of accounts, analyzing associated account and repository data;
generating a score for each account of the plurality of accounts based on the analyzing, the score being indicative of an account belonging to the customer, wherein the score is a composite score derived from a combination of attribute scores for a plurality of the profile photo, the username, the website link, and the creation date, and wherein presence of the verification flag or a contributor associated with the customer assigns a maximum score;
labeling one or more accounts of the plurality of accounts as belonging to the customer based on the score; and
responsive to labeling, scanning one or more repositories associated with the labeled one or more accounts for sensitive information to prevent data leakage, and upon detecting the sensitive information, generating an alert or initiating a remedial action.
10 . The non-transitory computer-readable medium of claim 9 , wherein the account and repository data further include a username, and wherein the analyzing further comprises comparing the username to a customer name via one or more name comparison models.
11 . The non-transitory computer-readable medium of claim 9 , wherein the account and repository data include a verification flag, and wherein the analyzing further comprises determining, for each of the plurality of accounts, if the verification flag is present.
12 . The non-transitory computer-readable medium of claim 9 , wherein the account and repository data include a profile photo, and wherein the analyzing further comprises comparing the profile photo to a list of photos of a logo associated with the customer via a photo comparison model.
13 . The non-transitory computer-readable medium of claim 9 , wherein the account and repository data include a website link, and wherein the analyzing further comprises checking the website link to a known customer website link.
14 . The non-transitory computer-readable medium of claim 9 , wherein the account and repository data include a creation date, and wherein the analyzing further comprises comparing the creation date to a current date and determining an age of the account and repository data.
15 . The non-transitory computer-readable medium of claim 9 , wherein the account and repository data include an update date, and wherein the analyzing further comprises comparing the update date to a current date and determining a duration between the current date and update date.
16 . The non-transitory computer-readable medium of claim 9 , wherein the account and repository data include one or more contributor details, and wherein the analyzing further comprises determining if the one or more contributor details belong to the client via a verification contributor detail model.