'access key' 검색 결과

Inspect Linux scheduled tasks, services, shell profiles, shared library settings, and SSH keys for mechanisms that maintain attacker access. Correlate findings with audit logs to produce a timeline, risk scores, and remediation commands.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating how attackers maintained access to a Linux host
• Hunting for suspicious scheduled tasks and services
• Building a timeline from persistence-related audit events

Analyze Kubernetes API server audit logs to identify pod access, secret reads, permission changes, privileged pods, and anonymous requests. Use the event patterns to reconstruct suspicious activity and develop detection rules for security monitoring systems.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Tracing API activity during a suspected cluster compromise
• Reviewing access to Kubernetes secrets
• Investigating permission changes and privileged pods

Review Handsontable code changes for architecture, code quality, performance, accessibility, and test coverage. Findings include severity, confidence, and file locations, helping developers assess whether changes follow project rules and demonstrate the intended behavior.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review a Handsontable branch or pull request
• Check architecture before or during core changes
• Review keyboard access and performance concerns

Guides authentication and access permissions for Google Cloud users and applications. It helps choose credentials for local development, production services, or external clouds, with guidance on short-lived credentials and avoiding downloaded service account keys.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set up credentials for local Python development
• Configure Cloud Run access to Cloud SQL
• Connect workloads on AWS or Azure to Google Cloud

Audit Solidity contracts in Foundry projects before deployment using code analysis, randomized tests, manual review, and private key checks. Produces a JSON report with findings, remediation, test coverage, and a pass or fail deployment decision.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Auditing Solidity contracts before deployment
• Adding fuzz and invariant tests for contracts that move funds
• Reviewing private key storage and deployment scripts

Guides security testing of Android and iOS apps through file inspection and observation while the app runs. Covers network traffic, stored secrets, external app interfaces, authentication, and backend APIs, with tool examples and a testing checklist.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Inspecting APK or IPA files for endpoints and embedded secrets
• Observing app behavior and traffic with Frida
• Reviewing deep links and externally accessible components

Review and improve UI accessibility, including color contrast, keyboard operation, visible focus, and clear status messages. A contrast checker supports color checks, while guidance also covers text zoom and form fields obscured by mobile keyboards.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking contrast between text and background colors
• Improving keyboard navigation and visible focus
• Clarifying empty, loading, and error states

Assess Laravel applications for exposed secrets, accessible dashboards, and authentication or permission flaws. The skill guides checks of debug settings, signed URLs, cookies, and model updates, with validation criteria for understanding the impact of findings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing Laravel debug settings and exposed configuration files
• Checking access controls on Telescope and Horizon dashboards
• Testing signed URLs and unintended profile field updates

Org-grade attack-surface mapping: given a company's legal identity, discover its ENTIRE owned internet footprint — corporate family -> owned domains -> owned netblocks/ASN -> live assets — with attribution discipline, not just DNS breadth. The org-first attribution pyramid (legal entity -> LEI/registration -> corporate family -> owned domains -> owned netblocks/ASN -> live assets). Corporate-identity resolution via the GLEIF LEI API (legal name -> LEI, exact-LEI direct-children expansion, downward-only depth-capped BFS, NEVER a name re-resolution), SEC-EDGAR full-text search + Exhibit-21 subsidiary entity names, OpenCorporates entity corroboration, Wikidata SPARQL corporate graph (P856/P355/P749/P1830). Domain attribution via reverse-WHOIS (WhoisXML preview-then-purchase quota guard, SecurityTrails associated-domains — both paid), crt.sh O= certificate-transparency organization pivot (keyless), infrastructure correlation (shared NS/MX/SaaS-TXT, netblock membership, reverse-DNS PTR), and the independent-evidence combiner (1-prod(1-w_i), rule of three, OwnerTier NONE/WEAK/MODERATE/STRONG/CONFIRMED) — discover-only `related:` candidates are NEVER auto-scanned. Netblock/ASN attribution via org-first RIR queries (ARIN Whois-RWS org-handle search, RIPE DB organisation + inverse-org search) that recover 'dark netblocks' with no DNS link to the seed, ASN discovery (RIPEstat + BGPView union), the HYPERSCALER-SCOPE GUARD (never attribute a whole AWS/GCP/Azure/Cloudflare announced range to a tenant — keep only the seed-containing block, tag shared_hosting_cdn), and org-identity-seeded internet-scan-index queries (Shodan/Censys/ZoomEye/FOFA/BinaryEdge org: filters + an always-on keyless crt.sh fallback). Promote-to-scan triage ranks forgotten discover-only netblocks by remote-access exposure (gateway-vendor/KEV/control-plane/datastore port scoring) into an operator queue. Attribution confidence rubric + anti-patterns (namesake grafting via GLEIF name re-resolution, single-signal ownership, hyperscaler over-attribution, privacy-WHOIS pivot poisoning, RIR org-name collisions). Passive/keyless-first OSINT only — every paid-key dependency is enrichment on top of a keyless core, never a hard requirement. Use when mapping an organization's full corporate-family internet footprint, resolving a legal entity to its LEI/subsidiaries, discovering domains/netblocks/ASNs an org owns beyond its one seed domain, auditing M&A/shadow-IT sprawl, or scoping an engagement that starts from a company NAME rather than a domain.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Provides web accessibility best practices for semantic HTML, ARIA, keyboard navigation, color contrast, and screen reader patterns. Use when building UI components, reviewing accessibility, or when user mentions 'a11y', 'accessibility', 'ARIA', 'screen reader', 'keyboard navigation', 'WCAG'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when reviewing or improving frontend accessibility, semantic structure, keyboard support, focus management, ARIA labels, screen reader behavior, WCAG 2.2 issues, touch accessibility, or assistive-technology regressions; Chinese triggers include accessibility, accessibility, a11y, WCAG, screen reader.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when choosing between Salesforce record-access mechanisms or reviewing the access model end to end. Trigger keywords: OWD, org-wide defaults, sharingModel, externalSharingModel, record access model, sharing architecture, which sharing mechanism, UserRecordAccess, __Share, RowCause, why can user see too much. NOT for sharing rules - use admin/sharing-rules. NOT for role hierarchy - use admin/role-hierarchy-design.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when designing or maintaining the role hierarchy as a record-access mechanism. Trigger keywords: role hierarchy, manager cannot see subordinate records, grant access using hierarchies, role reparenting, portal role, how deep should the role hierarchy be, design the role hierarchy. NOT for territory models - use admin/enterprise-territory-management. NOT for rule-based grants - use admin/sharing-rules. NOT for the overall model - use admin/sharing-and-visibility.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Accessibility Engineer IA — Expert en accessibilité (WCAG 2.1, screen readers, ARIA, keyboard nav). Rend les applications utilisables par tous.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build WCAG 2.1 AA compliant web applications for University of Sheffield. Covers semantic HTML, ARIA patterns, form accessibility, keyboard navigation, color contrast, alt text, captions, and automated testing. Use when creating websites, web apps, forms, interactive components, or auditing accessibility for WCAG compliance, screen readers, keyboard access, or inclusive design.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build accessible web applications following WCAG 2.1/2.2 guidelines with proper semantic HTML, ARIA attributes, keyboard navigation, screen reader support, and inclusive design. Use when implementing ARIA labels and roles, ensuring keyboard navigation, supporting screen readers, providing text alternatives for images, managing focus, creating accessible forms, building inclusive UI components, testing with accessibility tools, meeting WCAG compliance levels, or designing for users with disabilities.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

React 18/19 화면 구성 요소의 구현과 검토를 지원합니다. 상태 관리, 데이터 조회, 폼, 로딩·오류 표시, 서버와 브라우저의 경계, 접근성 설계를 다룹니다.

• React 화면 구성 요소 검토하기
• 공유 상태를 둘 위치 결정하기
• 폼과 데이터 조회 방식 설계하기

Set up and check OmniRoute authentication for API access and dashboard sessions. Use Bearer credentials for remote requests, manage login cookies, inspect authentication status, and configure OIDC, a standard for signing in through an identity provider.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up API key authentication for OmniRoute
• Logging in to and out of dashboard sessions
• Checking authentication status and CSRF tokens

Create and manage secure tunnels that make OmniRoute accessible over the internet. Use ngrok, Cloudflare Tunnel, or a custom tunnel to share access with remote agents and automated build and test pipelines.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Expose OmniRoute through a secure tunnel
• Share access with remote agents
• Connect CI pipelines to OmniRoute

Review form fields for code that blocks pasting, then remove those restrictions. The skill helps check password manager use, keyboard interactions, and accessibility so people can paste passwords and other long values into inputs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking why passwords cannot be pasted
• Reviewing credit card fields for paste restrictions
• Improving form accessibility

Review decorative images and icons to prevent unnecessary screen reader announcements. Check empty alt text, aria-hidden, and relevant keyboard behavior, then suggest fixes for concrete accessibility issues without flagging decorative assets solely because they exist.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking decorative images for unnecessary announcements
• Reviewing accessibility of SVGs and icons
• Checking shared decorative component patterns

Review file upload interfaces for clear labels, accepted formats, size limits, and accessible progress and error messages. Check that keyboard and screen reader users can complete uploads, including alternatives to drag and drop.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review labels and instructions on file upload forms
• Check keyboard alternatives to drag and drop
• Improve upload progress and error announcements

Review rotating slideshows for accessibility and guide fixes to pause controls, keyboard navigation, and screen reader announcements. Check the rendered HTML and ensure the carousel respects users who request reduced motion in their device settings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review pause controls for autoplay slideshows
• Check carousel navigation using only a keyboard
• Review screen reader announcements of slide changes