Organizations
Open Unified Identities › Resources, filter Providers to GitHub › Organization, then select a row to open its details.

Organization Details
Opening an organization shows the Risk and Exposure Point in the header, and the page contains the Information pane and, when the organization has issues, the Issues pane.

Information
Information Pane can contain different badges to highlight important attributes.
Tier 0
Indicates that the object is a Tier 0 asset. Organizations are always Tier 0: control over an organization is equivalent to full control of every repository, team and member it contains.
Privileged
Indicates that the object is privileged.
Shadow
Indicates that the object can compromise admin objects with at least one attack path.
Information Pane contains Details, Members, Repositories and Teams tabs respectively. Each relationship tab label shows its row count.
Details
Details tab contains attributes below about the organization object.
Login
The unique account name (handle) of the organization (e.g., fs-forestall).
Name
The name of the organization as recorded by Forestall.
Public Repos
The number of public repositories owned by the organization (e.g., 12).
Private Repos
The number of private repositories owned by the organization (e.g., 48). Derived from the repositories actually collected in the scan, so it reflects what was in scope rather than the raw counter reported by GitHub.
Plan
The GitHub subscription plan of the organization (e.g., free, team, enterprise).
Object ID
The GitHub node identifier of the organization.
2FA Required
Whether two-factor authentication is enforced for all members. Displayed as Required, Not required, or Unknown.
Default Repo Permission
The base permission every member receives on repositories (e.g., read, write, admin, none). Displayed as Unknown when the setting could not be read.
Members Can Create Public Repos
Whether members are allowed to create public repositories. Displayed as Yes, No, or Unknown.
Members Can Create Private Repos
Whether members are allowed to create private repositories. Displayed as Yes, No, or Unknown.
Unknown means the scanning credential could not read the setting: GitHub returns these organization settings only to organization owners. It does not mean the setting is disabled. Findings that depend on an unknown value are suppressed rather than raised, so an organization is never reported as insecure on the basis of a permission gap. To resolve Unknown values, re-scan with a credential that has
admin:org.
Members
Members tab contains a list of users that belong to this organization.

Name: The name of the user object. Login: The unique account name (handle) of the user. Role: The user's role within the organization (admin or member).
Repositories
Repositories tab contains a list of repositories owned by this organization.

Name: The name of the repository object. Visibility: The visibility level of the repository (private, internal, public). Default Branch: The default branch of the repository.
Teams
Teams tab contains a list of teams defined in this organization.

Name: The name of the team object. Slug: The unique URL identifier of the team. Permission: The default permission the team is granted on its repositories (pull, triage, push, maintain, admin).
Issues
Issues pane contains identified issues on the organization object.

Last updated
Was this helpful?