{"meta":{"title":"組織のセキュリティ","intro":"組織内の脆弱性を防ぎ、アラートに対処するのに役立つスキルを構築します。","product":"セキュリティとコードの品質","breadcrumbs":[{"href":"/ja/enterprise-server@3.16/code-security","title":"セキュリティとコードの品質"},{"href":"/ja/enterprise-server@3.16/code-security/tutorials","title":"Tutorials"},{"href":"/ja/enterprise-server@3.16/code-security/tutorials/secure-your-organization","title":"組織をセキュリティで保護する"}],"documentType":"subcategory"},"body":"# 組織のセキュリティ\n\n組織内の脆弱性を防ぎ、アラートに対処するのに役立つスキルを構築します。\n\n## Links\n\n* [組織でのデータ漏洩を防ぐためのベスト プラクティス](/ja/enterprise-server@3.16/code-security/tutorials/secure-your-organization/best-practices-for-preventing-data-leaks-in-your-organization)\n\n  組織内に存在するプライベートまたは機密データが公開されないようにするためのガイダンスと推奨事項について説明します。\n\n* [/best-practice-fix-alerts-at-scale](/ja/enterprise-server@3.16/best-practice-fix-alerts-at-scale)\n\n* [/prioritize-alerts-in-production-code](/ja/enterprise-server@3.16/prioritize-alerts-in-production-code)\n\n* [/interpreting-secret-risk-assessment-results](/ja/enterprise-server@3.16/interpreting-secret-risk-assessment-results)\n\n* [/interpreting-code-security-risk-assessment-results](/ja/enterprise-server@3.16/interpreting-code-security-risk-assessment-results)\n\n* [/organizing-remediation-efforts-for-leaked-secrets](/ja/enterprise-server@3.16/organizing-remediation-efforts-for-leaked-secrets)\n\n* [Protecting against security threats](/ja/enterprise-server@3.16/code-security/tutorials/secure-your-organization/protect-against-threats)\n\n  What steps should I take now, in the near future, and on an ongoing basis to reduce exposure to security threats across my organizations on GitHub?\n\n* [Preparing for a security incident](/ja/enterprise-server@3.16/code-security/tutorials/secure-your-organization/preparing-for-security-incidents)\n\n  Ensure you have the tools and processes in place to respond effectively to a security incident.\n\n* [Responding to a security incident](/ja/enterprise-server@3.16/code-security/tutorials/secure-your-organization/responding-to-security-incidents)\n\n  Respond strategically to a security incident affecting organizations or repositories in your GitHub enterprise."}