'vulnerabilities' 검색 결과

Test an authorized web application, map its exposed pages and inputs, and verify suspected vulnerabilities with reproducible evidence. Produce a security report covering confirmed findings, their impact, reproduction steps, and suggested fixes.

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

• Check a staging web application for vulnerabilities
• Verify whether a suspected vulnerability is reproducible
• Compile evidence and fixes into a security report

Audit project dependencies for known vulnerabilities and outdated packages. Organize findings by severity, review proposed package changes before optional automatic fixes, and rerun the audit to check whether the reported vulnerability count decreased.

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

• Auditing third-party packages before a release
• Checking dependencies after installation or lockfile changes
• Investigating reported CVE advisories

Review pending code changes for newly introduced security vulnerabilities with clear exploitation paths. Focus on concrete, significant risks and filter likely false alarms, then report affected files, line numbers, severity, attack scenarios, and recommended fixes in Markdown.

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

• Review a PR for newly introduced security vulnerabilities
• Check authentication and authorization changes
• Trace user input for injection risks

Use Strix to test web apps, APIs, and source code for exploitable security flaws. Choose local or cloud execution, set testing scope and budget, and review validated findings with reproducible examples and structured reports.

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

• Security testing an application or API
• Testing source code alongside a deployed application
• Choosing between local and cloud execution

Set up Strix security checks in CI/CD to test pull request changes, report verified vulnerabilities, and gate merges. Covers both a CLI running on your own infrastructure and a managed service with pull request comments.

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

• Check pull request changes for vulnerabilities before merging
• Add Strix scans to GitHub Actions or GitLab CI
• Choose between managed reviews and scans on your own runners

Analyze firmware from routers, cameras, and other IoT devices, from extracting internal files to running services in an emulator. Follow a staged workflow to investigate vulnerabilities and reproduce findings with firmware analysis and testing tools.

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

• Auditing router or camera firmware
• Inspecting firmware update packages
• Running firmware without physical hardware

Review concrete code for exploitable security defects, including missing access checks, unsafe input handling, and exposed secrets. Report verified issues with file locations, reachable attack paths, severity, and suggested fixes.

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

• Review a code change for exploitable vulnerabilities
• Check authentication and access controls
• Trace unsafe input handling and secret exposure

Review and write Solidity smart contracts with security in mind. Address reentrancy, where external calls trigger repeated execution, along with numeric overflow and access control issues, using implementation patterns, security tests, and documentation for audit preparation.

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

• Review existing smart contracts for vulnerabilities
• Implement withdrawal logic that resists reentrancy
• Test overflow protection and access restrictions

Configure GitHub Dependabot to keep dependencies, the packages a project relies on, updated. Organize update pull requests into groups, set schedules and exclusion rules, and configure security updates across projects with multiple packages or package systems.

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

• Create or revise dependabot.yml
• Group dependency updates into fewer pull requests
• Configure updates across a monorepo

Assess iOS and Android app security using OWASP MASTG, a mobile security testing guide. Examine app files, runtime behavior, stored data, authentication, and API traffic, then document vulnerabilities, their impact, and suggested fixes.

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

• Assess mobile app security before release
• Check sensitive data storage and network traffic
• Test authentication and resistance to runtime manipulation

Set up repeatable security tests for LLM apps with Promptfoo and DeepTeam. Connect them to automated build pipelines, detect renewed vulnerabilities to malicious instructions or data leakage, and compare results across model or prompt changes.

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

• Running automated attack tests on every code change
• Blocking merges when security tests fail
• Comparing security across model or prompt versions

Build a GitLab CI/CD pipeline with automated checks for vulnerable code, dependencies, container images, running applications, and exposed secrets. Covers scanner configuration, consolidated findings, and approval policies for serious vulnerabilities before production deployment.

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

• Add automated security scans to .gitlab-ci.yml
• Check dependencies and container images for known vulnerabilities
• Detect credentials and API keys committed to source control

Build a tracking system for vulnerabilities that cannot be fixed on time. Define exception requests, approval workflows, alternative protective measures, expiration checks, and audit records so teams can track accepted risks and support compliance reviews.

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

• Standardizing exception requests for delayed vulnerability fixes
• Recording alternative protections and risk acceptance
• Checking expired exceptions and producing monthly reports

Assess cybersecurity risks using NIST SP 800-30 Rev 1 by examining threats, weaknesses, likelihood, and business impact. Produce a ranked risk register, a structured record of risks and recommended responses, with a summary for leadership.

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

• Preparing documented risk analysis for compliance frameworks
• Assessing a new system before launch
• Reporting the highest risks to leadership

Build a repeatable process for Microsoft monthly security updates, from reviewing advisories and ranking vulnerabilities to testing, staged deployment, and verification. Helps teams set response deadlines based on risk and report remaining unpatched systems.

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

• Establishing a monthly Microsoft security update workflow
• Prioritizing vulnerabilities by exploitation risk
• Planning pilot and production deployment stages

Build dashboards that show how long vulnerabilities remain unresolved and compare remediation times with severity-based deadlines. Define response policies, automate escalation notices, and report compliance rates and other measures of remediation progress.

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

• Define vulnerability remediation deadlines
• Visualize overdue vulnerabilities
• Automate reminders and management escalations

Assess REST, GraphQL, and gRPC APIs for authentication, access control, input validation, and business logic weaknesses. Use OWASP API Security Top 10, a framework of common API risks, to organize testing and document findings with reproduction steps and remediation.

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

• Comparing API access across user roles
• Checking token handling and request rate limits
• Assessing GraphQL access control and data exposure

Analyze Solidity smart contracts with Slither and Mythril before Ethereum deployment. Combine code inspection with execution path analysis, review potential vulnerabilities, remove duplicate findings, and produce an audit report with severity ratings and suggested fixes.

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

• Checking Solidity contracts before deployment
• Investigating reentrancy and access control weaknesses
• Consolidating findings from Slither and Mythril

Review websites for security, browser compatibility, and code quality. Identify issues in HTTPS settings, third-party libraries, HTML, and error handling, then apply concrete improvements using checklists and implementation examples.

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

• Reviewing website security settings
• Checking third-party libraries for vulnerabilities
• Replacing deprecated browser APIs

Review code for security vulnerabilities using a checklist covering unsafe input, authentication, access permissions, secrets, and data exposure. Classify findings into four severity levels to distinguish exploitable flaws, issues needing investigation, and smaller improvements.

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

• Review SQL, shell commands, and HTML for unsafe input
• Check authentication and access permissions
• Find exposed credentials and sensitive log data

Helps address Google Cloud Security Command Center findings by planning targeted fixes for permissions, misconfigurations, vulnerabilities, and combined attack paths. It includes impact checks, verification, rollback steps, and execution after user approval.

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

• Fix excessive permissions flagged by Security Command Center
• Plan fixes for exposed buckets or firewall rules
• Address attack paths involving multiple security issues

Helps review application code, authentication, access controls, and dependencies for security flaws. Uses OWASP guidance and CVE reports, records of known vulnerabilities, to assess impact and recommend practical fixes.

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

• Reviewing application code for security flaws
• Assessing known vulnerabilities in dependencies
• Checking authentication and data access controls

Analyze Solidity smart contracts with Slither and Mythril before Ethereum deployment. Combine code inspection with execution path analysis, review potential vulnerabilities, remove duplicate findings, and produce an audit report with severity ratings and suggested fixes.

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

• Checking Solidity contracts before deployment
• Investigating reentrancy and access control weaknesses
• Consolidating findings from Slither and Mythril

Review dependency manifests and lockfiles to find outdated packages and known security vulnerabilities. Group proposed updates by version change, report current and suggested versions, and identify updates that need human review.

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

• Reviewing outdated dependencies
• Checking known vulnerabilities and update options
• Separating patch, minor, and major updates