# セキュリティ・アクセス管理

> このサービスに関する実績を抜粋してご紹介します。

- [Linuxサーバーを守る1,000件のRBACルールを作成](https://engineer.company/ja/portfolio/wrote-1000-rbac-rules-to-secure-linux-servers/) — security-access
- [M365・SSO全体のアクセス管理を主導](https://engineer.company/ja/portfolio/led-access-management-across-m365-and-sso/) — security-access
- [WireGuard・IPsec VPN接続8本を管理](https://engineer.company/ja/portfolio/managed-8-wireguard-and-ipsec-vpn-connections/) — security-access
- [チームの意思疎通と協働を改善](https://engineer.company/ja/portfolio/improved-team-communication-and-collaboration/) — security-access
- [ネットワークインフラを管理](https://engineer.company/ja/portfolio/administered-network-infrastructure/) — security-access
- [Dockerアプリ100個のSSL/TLS証明書を自動化](https://engineer.company/ja/portfolio/automated-ssl-tls-certs-for-100-docker-apps/) — security-access
- [利用者の組織コンテキスト切り替えを構築](https://engineer.company/ja/portfolio/built-organization-context-switching-for-users/) — security-access
- [切り替えと配信ログを備えるメール機能を構築](https://engineer.company/ja/portfolio/built-email-with-failover-and-delivery-logging/) — security-access
- [Azureインフラをコードとして構築](https://engineer.company/ja/portfolio/provisioned-azure-infrastructure-as-code/) — security-access
- [nonce付きCSPでアプリケーションを堅牢化](https://engineer.company/ja/portfolio/hardened-the-application-with-nonce-based-csp/) — security-access
- [チームの協働を自動化](https://engineer.company/ja/portfolio/automated-team-collaboration/) — security-access
- [全社共通のパスワード管理を導入](https://engineer.company/ja/portfolio/integrated-a-company-wide-password-manager/) — security-access
- [Stripe・アプリ内購入の利用権限を構築](https://engineer.company/ja/portfolio/built-stripe-and-in-app-purchase-entitlements/) — security-access
- [異常時拒否のレート制限・不正利用対策を構築](https://engineer.company/ja/portfolio/built-fail-closed-rate-limiting-and-anti-abuse/) — security-access
- [企業所有権の申請・審査を構築](https://engineer.company/ja/portfolio/built-company-ownership-claims-and-adjudication/) — security-access
- [継続的なセキュリティ検査を運用](https://engineer.company/ja/portfolio/ran-a-continuous-security-scanning-programme/) — security-access
- [3つあったが、どれも機能していなかった防御](https://engineer.company/ja/portfolio/three-locks-on-the-door-none-of-them-locked/) — security-access
- [SSHの24設定項目を検証・堅牢化](https://engineer.company/ja/portfolio/hardened-ssh-to-24-validated-directives/) — security-access
- [実行ごとに侵入元の遮断を実証](https://engineer.company/ja/portfolio/proved-the-intrusion-ban-works-every-run/) — security-access
- [ファイアウォールルールを位置で検証](https://engineer.company/ja/portfolio/verified-firewall-rules-by-position/) — security-access
- [秘密情報の1秒の事前検査を追加](https://engineer.company/ja/portfolio/added-a-one-second-preflight-for-secrets/) — security-access
- [20レコードのDNSゾーンをコードで照合](https://engineer.company/ja/portfolio/reconciled-a-20-record-dns-zone-as-code/) — security-access
- [全ユニットのsystemdサンドボックス露出を低減](https://engineer.company/ja/portfolio/cut-systemd-sandbox-exposure-on-every-unit/) — security-access
- [PodmanとQuadletでコンテナを運用](https://engineer.company/ja/portfolio/ran-containers-on-podman-and-quadlet/) — security-access
- [2台目のサーバーをコードで構築](https://engineer.company/ja/portfolio/provisioned-a-second-server-from-code/) — security-access
- [認証情報漏出後に対象範囲の規則を記述](https://engineer.company/ja/portfolio/wrote-a-scope-rule-after-a-credential-leak/) — security-access
- [すべての運用秘密情報をホストごとに分離](https://engineer.company/ja/portfolio/split-every-operational-secret-per-host/) — security-access
- [未使用だったコアの半分の機能を実装](https://engineer.company/ja/portfolio/reached-the-unused-half-of-the-core/) — security-access
- [公開するすべての部品のライセンスを把握](https://engineer.company/ja/portfolio/know-the-licence-of-everything-you-ship/) — security-access
- [追跡せずに13アドレスを測定](https://engineer.company/ja/portfolio/measured-13-addresses-with-no-tracking/) — security-access
- [読みやすいTor onionミラーを公開](https://engineer.company/ja/portfolio/published-a-readable-tor-onion-mirror/) — security-access

<https://engineer.company/ja/services/security-access/>
