{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/veeam-manual-linux-hardened-repository-credentials/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/veeam-manual-linux-hardened-repository-credentials/",
        "slug": "veeam-manual-linux-hardened-repository-credentials",
        "url": "https://update.dsesecurity.com/updates/veeam-manual-linux-hardened-repository-credentials/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/veeam-manual-linux-hardened-repository-credentials.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/veeam-manual-linux-hardened-repository-credentials/"
        },
        "title": "Separate Veeam Linux onboarding credentials from ongoing access",
        "summary": "Review single-use SSH credentials specifically for manually prepared Linux hardened repositories.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "physical-security",
            "label": "Physical security",
            "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "business-continuity",
                "name": "Business Continuity",
                "url": "https://update.dsesecurity.com/topic/business-continuity/"
            },
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-10-15T00:43:21+00:00",
        "modified_at": "2026-10-15T00:44:33+00:00",
        "reviewed_on": "2026-10-14",
        "reading_minutes": 2,
        "word_count": 236,
        "potentially_affected": "This article concerns the manual Linux path in the cited guide. Do not apply its SSH onboarding instructions to a different repository deployment method without checking that method’s documentation.",
        "dse_recommendation": "DSE recommends documenting the temporary onboarding authority separately from the repository’s continuing service and maintenance requirements.",
        "primary_source": {
            "name": "Veeam — Adding Hardened Repositories, version 13",
            "url": "https://helpcenter.veeam.com/docs/vbr/userguide/hardened_repository_add.html?ver=13",
            "published_on": null,
            "authority": "helpcenter.veeam.com"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<p>Review single-use SSH credentials specifically for manually prepared Linux hardened repositories.</p>\n<h2>Source facts</h2>\n<p>For a manually prepared Linux hardened repository, Veeam’s version 13 guide describes initial setup using single-use SSH credentials. The account must be non-root and have a home directory. Veeam states that these single-use credentials are not stored in the backup server’s configuration database. If the account belongs to sudoers, the guide directs administrators to remove it from sudoers after the Linux server is added.</p>\n<p>Source: <a href=\"https://helpcenter.veeam.com/docs/vbr/userguide/hardened_repository_add.html?ver=13\">Veeam — Adding Hardened Repositories, version 13</a>.</p>\n<h2>Applicability</h2>\n<p>This article concerns the manual Linux path in the cited guide. Do not apply its SSH onboarding instructions to a different repository deployment method without checking that method’s documentation.</p>\n<h2>DSE recommendation</h2>\n<p>DSE recommends documenting the temporary onboarding authority separately from the repository’s continuing service and maintenance requirements. Before setup, record the account owner and the planned privilege-removal checkpoint. After successful addition, review the actual operating-system account and its remaining rights; the phrase single-use should not substitute for that review. Keep credentials out of tickets, screenshots, and evidence bundles. Agree a supported maintenance and recovery process with the backup owner before removing access that process requires.</p>\n<h2>Verification</h2>\n<p>Record successful Linux-server addition, then confirm removal of the temporary sudoers membership where applicable. Check the supported backup and repository-management operations after setup. Retain sanitized outcomes and ownership details rather than the onboarding password.</p>\n<h2>Official reference</h2>\n<p><a href=\"https://helpcenter.veeam.com/docs/vbr/userguide/hardened_repository_add.html?ver=13\">Veeam — Adding Hardened Repositories, version 13</a>. Reviewed October 14, 2026.</p>",
        "content_text": "Review single-use SSH credentials specifically for manually prepared Linux hardened repositories.\nSource facts\nFor a manually prepared Linux hardened repository, Veeam’s version 13 guide describes initial setup using single-use SSH credentials. The account must be non-root and have a home directory. Veeam states that these single-use credentials are not stored in the backup server’s configuration database. If the account belongs to sudoers, the guide directs administrators to remove it from sudoers after the Linux server is added.\nSource: Veeam — Adding Hardened Repositories, version 13.\nApplicability\nThis article concerns the manual Linux path in the cited guide. Do not apply its SSH onboarding instructions to a different repository deployment method without checking that method’s documentation.\nDSE recommendation\nDSE recommends documenting the temporary onboarding authority separately from the repository’s continuing service and maintenance requirements. Before setup, record the account owner and the planned privilege-removal checkpoint. After successful addition, review the actual operating-system account and its remaining rights; the phrase single-use should not substitute for that review. Keep credentials out of tickets, screenshots, and evidence bundles. Agree a supported maintenance and recovery process with the backup owner before removing access that process requires.\nVerification\nRecord successful Linux-server addition, then confirm removal of the temporary sudoers membership where applicable. Check the supported backup and repository-management operations after setup. Retain sanitized outcomes and ownership details rather than the onboarding password.\nOfficial reference\nVeeam — Adding Hardened Repositories, version 13. Reviewed October 14, 2026.",
        "content_markdown": "Review single-use SSH credentials specifically for manually prepared Linux hardened repositories.\n\n## Source facts\n\nFor a manually prepared Linux hardened repository, Veeam’s version 13 guide describes initial setup using single-use SSH credentials. The account must be non-root and have a home directory. Veeam states that these single-use credentials are not stored in the backup server’s configuration database. If the account belongs to sudoers, the guide directs administrators to remove it from sudoers after the Linux server is added.\n\nSource: [Veeam — Adding Hardened Repositories, version 13](https://helpcenter.veeam.com/docs/vbr/userguide/hardened_repository_add.html?ver=13).\n\n## Applicability\n\nThis article concerns the manual Linux path in the cited guide. Do not apply its SSH onboarding instructions to a different repository deployment method without checking that method’s documentation.\n\n## DSE recommendation\n\nDSE recommends documenting the temporary onboarding authority separately from the repository’s continuing service and maintenance requirements. Before setup, record the account owner and the planned privilege-removal checkpoint. After successful addition, review the actual operating-system account and its remaining rights; the phrase single-use should not substitute for that review. Keep credentials out of tickets, screenshots, and evidence bundles. Agree a supported maintenance and recovery process with the backup owner before removing access that process requires.\n\n## Verification\n\nRecord successful Linux-server addition, then confirm removal of the temporary sudoers membership where applicable. Check the supported backup and repository-management operations after setup. Retain sanitized outcomes and ownership details rather than the onboarding password.\n\n## Official reference\n\n[Veeam — Adding Hardened Repositories, version 13](https://helpcenter.veeam.com/docs/vbr/userguide/hardened_repository_add.html?ver=13). Reviewed October 14, 2026."
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/veeam-manual-linux-hardened-repository-credentials/",
                "url": "https://update.dsesecurity.com/updates/veeam-manual-linux-hardened-repository-credentials/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-10-14"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/veeam-manual-linux-hardened-repository-credentials/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Separate Veeam Linux onboarding credentials from ongoing access",
                        "item": "https://update.dsesecurity.com/updates/veeam-manual-linux-hardened-repository-credentials/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/veeam-manual-linux-hardened-repository-credentials/#article",
                "identifier": "https://update.dsesecurity.com/updates/veeam-manual-linux-hardened-repository-credentials/",
                "url": "https://update.dsesecurity.com/updates/veeam-manual-linux-hardened-repository-credentials/",
                "headline": "Separate Veeam Linux onboarding credentials from ongoing access",
                "description": "Review single-use SSH credentials specifically for manually prepared Linux hardened repositories.",
                "abstract": "Review single-use SSH credentials specifically for manually prepared Linux hardened repositories.",
                "articleBody": "Review single-use SSH credentials specifically for manually prepared Linux hardened repositories.\nSource facts\nFor a manually prepared Linux hardened repository, Veeam’s version 13 guide describes initial setup using single-use SSH credentials. The account must be non-root and have a home directory. Veeam states that these single-use credentials are not stored in the backup server’s configuration database. If the account belongs to sudoers, the guide directs administrators to remove it from sudoers after the Linux server is added.\nSource: Veeam — Adding Hardened Repositories, version 13.\nApplicability\nThis article concerns the manual Linux path in the cited guide. Do not apply its SSH onboarding instructions to a different repository deployment method without checking that method’s documentation.\nDSE recommendation\nDSE recommends documenting the temporary onboarding authority separately from the repository’s continuing service and maintenance requirements. Before setup, record the account owner and the planned privilege-removal checkpoint. After successful addition, review the actual operating-system account and its remaining rights; the phrase single-use should not substitute for that review. Keep credentials out of tickets, screenshots, and evidence bundles. Agree a supported maintenance and recovery process with the backup owner before removing access that process requires.\nVerification\nRecord successful Linux-server addition, then confirm removal of the temporary sudoers membership where applicable. Check the supported backup and repository-management operations after setup. Retain sanitized outcomes and ownership details rather than the onboarding password.\nOfficial reference\nVeeam — Adding Hardened Repositories, version 13. Reviewed October 14, 2026.",
                "datePublished": "2026-10-15T00:43:21+00:00",
                "dateModified": "2026-10-15T00:44:33+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/veeam-manual-linux-hardened-repository-credentials/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/veeam-manual-linux-hardened-repository-credentials/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Separate Veeam Linux onboarding credentials from ongoing access"
                },
                "articleSection": [
                    "Business Continuity",
                    "Cybersecurity"
                ],
                "keywords": [
                    "Business Continuity",
                    "Cybersecurity",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Business Continuity",
                        "url": "https://update.dsesecurity.com/topic/business-continuity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    }
                ],
                "wordCount": 236,
                "timeRequired": "PT2M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "Veeam — Adding Hardened Repositories, version 13",
                    "url": "https://helpcenter.veeam.com/docs/vbr/userguide/hardened_repository_add.html?ver=13"
                }
            }
        ]
    }
}