GitHub Administration flashcards
GitHub Administration · Build recall with a focused review session.
24 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Code-owner approval
- A review requirement that needs an applicable enforcing protection/ruleset as well as valid ownership mapping, distinct from merely requesting a reviewer.
- Fine-grained token
- A personal access credential further limited by selected resource owner, repositories and permissions within its owner’s existing authority and actual organization policies.
- Ruleset bypass
- An actual configured permission to bypass specified repository restrictions under relevant conditions, which must be considered before claiming an absolute merge prohibition.
- Runner trust boundary
- The code, host state, credentials and network reachability exposed when a job executes on a runner, distinct from repository eligibility alone.
- Job token permissions
- The actual allowed repository/API actions of the workflow token under job and enclosing policy configuration, not unrestricted account authority.
- Reusable workflow
- A supported callable workflow arrangement packaging jobs and explicit inputs/secrets, distinct from every action or arbitrary shared repository file.
- Least Privilege
- The principle that users and systems should be granted only the minimum access rights necessary to perform their tasks, reducing the potential damage from accidents or malicious activity.
- Separation of Duties
- A control that divides critical tasks among different individuals so that no single person can complete a sensitive action alone, helping to prevent fraud and errors.
- Role-Based Access Control (RBAC)
- An access control model where permissions are assigned to roles rather than individual users, and users are assigned to roles based on their job responsibilities.
- Multi-Factor Authentication (MFA)
- An authentication method that requires two or more independent credentials from different categories (something you know, have, or are) to verify a user's identity.
- Authentication
- The process of verifying the identity of a user, device, or system, typically through credentials such as passwords, tokens, or biometrics.
- Authorization
- The process of determining what actions or resources an authenticated entity is permitted to access, often enforced through access control policies.
- Single Sign-On (SSO)
- A mechanism that allows a user to log in once and access multiple applications or systems without re-entering credentials, improving usability and centralizing access control.
- Encryption
- The process of converting plaintext into ciphertext using an algorithm and a key, so that only authorized parties can read the original information.
- Symmetric Encryption
- An encryption method that uses the same secret key for both encryption and decryption, offering speed but requiring secure key distribution.
- Asymmetric Encryption
- Encryption using a suitable public-key scheme and a corresponding private key for decryption. Authenticated key distribution and the specified padding/protocol remain essential; signatures and key agreement are distinct constructions.
- Hash Function
- A digest construction mapping input to an output under its defined algorithm, with cryptographic versions designed for appropriate resistance properties. Password storage needs a suitable salted password-hashing/KDF scheme rather than a bare fast digest.
- Digital Signature
- An electronic signature that uses asymmetric cryptography to verify the authenticity and integrity of a message or document.
- Access control
- The policies and mechanisms that determine who can access which systems, data, or facilities and under what conditions.
- Security Information and Event Management (SIEM)
- A system that collects, aggregates, and analyzes log data from various sources to detect security incidents and support compliance reporting.
- Incident Response
- A structured approach to handling security incidents, typically including preparation, detection, containment, eradication, recovery, and lessons learned.
- Business Continuity Plan (BCP)
- A document that outlines how an organization will continue critical operations during and after a disruption, including strategies for recovery and restoration.
- Disaster Recovery Plan (DRP)
- A plan focused on restoring IT infrastructure and operations after a disaster, including backup restoration and recovery time objectives.
- Backup
- The process of copying data to a secondary location or medium to enable recovery in case of data loss or corruption.