CINXE.COM

<!doctype html> <html lang="en" data-n-head-ssr lang="en-US" data-n-head="%7B%22lang%22:%7B%22ssr%22:%22en-US%22%7D%7D"> <head > <meta data-n-head="ssr" charset="utf-8"><meta data-n-head="ssr" name="viewport" content="width=device-width, initial-scale=1"><meta data-n-head="ssr" data-hid="i18n-og" property="og:locale" content="en_US"><meta data-n-head="ssr" data-hid="i18n-og-alt-cs-CZ" property="og:locale:alternate" content="cs_CZ"><meta data-n-head="ssr" data-hid="i18n-og-alt-de-DE" property="og:locale:alternate" content="de_DE"><meta data-n-head="ssr" data-hid="i18n-og-alt-de-AT" property="og:locale:alternate" content="de_AT"><meta data-n-head="ssr" data-hid="i18n-og-alt-en-GB" property="og:locale:alternate" content="en_GB"><meta data-n-head="ssr" data-hid="i18n-og-alt-es-ES" property="og:locale:alternate" content="es_ES"><meta data-n-head="ssr" data-hid="i18n-og-alt-fr-FR" property="og:locale:alternate" content="fr_FR"><meta data-n-head="ssr" data-hid="i18n-og-alt-it-IT" property="og:locale:alternate" content="it_IT"><meta data-n-head="ssr" data-hid="i18n-og-alt-ja-JP" property="og:locale:alternate" content="ja_JP"><meta data-n-head="ssr" data-hid="i18n-og-alt-ko-KR" property="og:locale:alternate" content="ko_KR"><meta data-n-head="ssr" data-hid="i18n-og-alt-nl-NL" property="og:locale:alternate" content="nl_NL"><meta data-n-head="ssr" data-hid="i18n-og-alt-pl-PL" property="og:locale:alternate" content="pl_PL"><meta data-n-head="ssr" data-hid="i18n-og-alt-pt-BR" property="og:locale:alternate" content="pt_BR"><meta data-n-head="ssr" data-hid="i18n-og-alt-ru-KZ" property="og:locale:alternate" content="ru_KZ"><meta data-n-head="ssr" data-hid="i18n-og-alt-sv-SE" property="og:locale:alternate" content="sv_SE"><meta data-n-head="ssr" data-hid="i18n-og-alt-zh-Hans" property="og:locale:alternate" content="zh_Hans"><meta data-n-head="ssr" data-hid="i18n-og-alt-zh-Hant" property="og:locale:alternate" content="zh_Hant"><title>AXIS OS Portal</title><link data-n-head="ssr" href="/favicon.svg" rel="icon" sizes="16x16 32x32 64x64 128x128 256x256 512x512 1024x1024" type="image/svg+xml"><link data-n-head="ssr" data-hid="i18n-alt-cs" rel="alternate" href="https://help.axis.com/cs/axis-os" hreflang="cs"><link data-n-head="ssr" data-hid="i18n-alt-cs-CZ" rel="alternate" href="https://help.axis.com/cs-cz/axis-os" hreflang="cs-CZ"><link data-n-head="ssr" data-hid="i18n-alt-de" rel="alternate" href="https://help.axis.com/de/axis-os" hreflang="de"><link data-n-head="ssr" data-hid="i18n-alt-de-DE" rel="alternate" href="https://help.axis.com/de-de/axis-os" hreflang="de-DE"><link data-n-head="ssr" data-hid="i18n-alt-de-AT" rel="alternate" href="https://help.axis.com/de-at/axis-os" hreflang="de-AT"><link data-n-head="ssr" data-hid="i18n-alt-en" rel="alternate" href="https://help.axis.com/en/axis-os" hreflang="en"><link data-n-head="ssr" data-hid="i18n-alt-en-US" rel="alternate" href="https://help.axis.com/en-us/axis-os" hreflang="en-US"><link data-n-head="ssr" data-hid="i18n-alt-en-GB" rel="alternate" href="https://help.axis.com/en-gb/axis-os" hreflang="en-GB"><link data-n-head="ssr" data-hid="i18n-alt-es" rel="alternate" href="https://help.axis.com/es/axis-os" hreflang="es"><link data-n-head="ssr" data-hid="i18n-alt-es-ES" rel="alternate" href="https://help.axis.com/es-es/axis-os" hreflang="es-ES"><link data-n-head="ssr" data-hid="i18n-alt-fr" rel="alternate" href="https://help.axis.com/fr/axis-os" hreflang="fr"><link data-n-head="ssr" data-hid="i18n-alt-fr-FR" rel="alternate" href="https://help.axis.com/fr-fr/axis-os" hreflang="fr-FR"><link data-n-head="ssr" data-hid="i18n-alt-it" rel="alternate" href="https://help.axis.com/it/axis-os" hreflang="it"><link data-n-head="ssr" data-hid="i18n-alt-it-IT" rel="alternate" href="https://help.axis.com/it-it/axis-os" hreflang="it-IT"><link data-n-head="ssr" data-hid="i18n-alt-ja" rel="alternate" href="https://help.axis.com/ja/axis-os" hreflang="ja"><link data-n-head="ssr" data-hid="i18n-alt-ja-JP" rel="alternate" href="https://help.axis.com/ja-jp/axis-os" hreflang="ja-JP"><link data-n-head="ssr" data-hid="i18n-alt-ko" rel="alternate" href="https://help.axis.com/ko/axis-os" hreflang="ko"><link data-n-head="ssr" data-hid="i18n-alt-ko-KR" rel="alternate" href="https://help.axis.com/ko-kr/axis-os" hreflang="ko-KR"><link data-n-head="ssr" data-hid="i18n-alt-nl" rel="alternate" href="https://help.axis.com/nl/axis-os" hreflang="nl"><link data-n-head="ssr" data-hid="i18n-alt-nl-NL" rel="alternate" href="https://help.axis.com/nl-nl/axis-os" hreflang="nl-NL"><link data-n-head="ssr" data-hid="i18n-alt-pl" rel="alternate" href="https://help.axis.com/pl/axis-os" hreflang="pl"><link data-n-head="ssr" data-hid="i18n-alt-pl-PL" rel="alternate" href="https://help.axis.com/pl-pl/axis-os" hreflang="pl-PL"><link data-n-head="ssr" data-hid="i18n-alt-pt" rel="alternate" href="https://help.axis.com/pt/axis-os" hreflang="pt"><link data-n-head="ssr" data-hid="i18n-alt-pt-BR" rel="alternate" href="https://help.axis.com/pt-br/axis-os" hreflang="pt-BR"><link data-n-head="ssr" data-hid="i18n-alt-ru" rel="alternate" href="https://help.axis.com/ru/axis-os" hreflang="ru"><link data-n-head="ssr" data-hid="i18n-alt-ru-KZ" rel="alternate" href="https://help.axis.com/ru-ru/axis-os" hreflang="ru-KZ"><link data-n-head="ssr" data-hid="i18n-alt-sv" rel="alternate" href="https://help.axis.com/sv/axis-os" hreflang="sv"><link data-n-head="ssr" data-hid="i18n-alt-sv-SE" rel="alternate" href="https://help.axis.com/sv-se/axis-os" hreflang="sv-SE"><link data-n-head="ssr" data-hid="i18n-alt-zh" rel="alternate" href="https://help.axis.com/zh/axis-os" hreflang="zh"><link data-n-head="ssr" data-hid="i18n-alt-zh-Hans" rel="alternate" href="https://help.axis.com/zh-hans/axis-os" hreflang="zh-Hans"><link data-n-head="ssr" data-hid="i18n-alt-zh-Hant" rel="alternate" href="https://help.axis.com/zh-tw/axis-os" hreflang="zh-Hant"><link data-n-head="ssr" data-hid="i18n-xd" rel="alternate" href="https://help.axis.com/en-us/axis-os" hreflang="x-default"><link data-n-head="ssr" data-hid="i18n-can" rel="canonical" href="https://help.axis.com/en-us/axis-os"><style data-n-head="vuetify" type="text/css" id="vuetify-theme-stylesheet" nonce="undefined">.v-application a { color: #1976d2; } .v-application .primary { background-color: #1976d2 !important; border-color: #1976d2 !important; } .v-application .primary--text { color: #1976d2 !important; caret-color: #1976d2 !important; } .v-application .primary.lighten-5 { background-color: #c7fdff !important; border-color: #c7fdff !important; } .v-application .primary--text.text--lighten-5 { color: #c7fdff !important; caret-color: #c7fdff !important; } .v-application .primary.lighten-4 { background-color: #a8e0ff !important; border-color: #a8e0ff !important; } .v-application .primary--text.text--lighten-4 { color: #a8e0ff !important; caret-color: #a8e0ff !important; } .v-application .primary.lighten-3 { background-color: #8ac5ff !important; border-color: #8ac5ff !important; } .v-application .primary--text.text--lighten-3 { color: #8ac5ff !important; caret-color: #8ac5ff !important; } .v-application .primary.lighten-2 { background-color: #6aaaff !important; border-color: #6aaaff !important; } .v-application .primary--text.text--lighten-2 { color: #6aaaff !important; caret-color: #6aaaff !important; } .v-application .primary.lighten-1 { background-color: #488fef !important; border-color: #488fef !important; } .v-application .primary--text.text--lighten-1 { color: #488fef !important; caret-color: #488fef !important; } .v-application .primary.darken-1 { background-color: #005eb6 !important; border-color: #005eb6 !important; } .v-application .primary--text.text--darken-1 { color: #005eb6 !important; caret-color: #005eb6 !important; } .v-application .primary.darken-2 { background-color: #00479b !important; border-color: #00479b !important; } .v-application .primary--text.text--darken-2 { color: #00479b !important; caret-color: #00479b !important; } .v-application .primary.darken-3 { background-color: #003180 !important; border-color: #003180 !important; } .v-application .primary--text.text--darken-3 { color: #003180 !important; caret-color: #003180 !important; } .v-application .primary.darken-4 { background-color: #001e67 !important; border-color: #001e67 !important; } .v-application .primary--text.text--darken-4 { color: #001e67 !important; caret-color: #001e67 !important; } .v-application .secondary { background-color: #424242 !important; border-color: #424242 !important; } .v-application .secondary--text { color: #424242 !important; caret-color: #424242 !important; } .v-application .secondary.lighten-5 { background-color: #c1c1c1 !important; border-color: #c1c1c1 !important; } .v-application .secondary--text.text--lighten-5 { color: #c1c1c1 !important; caret-color: #c1c1c1 !important; } .v-application .secondary.lighten-4 { background-color: #a6a6a6 !important; border-color: #a6a6a6 !important; } .v-application .secondary--text.text--lighten-4 { color: #a6a6a6 !important; caret-color: #a6a6a6 !important; } .v-application .secondary.lighten-3 { background-color: #8b8b8b !important; border-color: #8b8b8b !important; } .v-application .secondary--text.text--lighten-3 { color: #8b8b8b !important; caret-color: #8b8b8b !important; } .v-application .secondary.lighten-2 { background-color: #727272 !important; border-color: #727272 !important; } .v-application .secondary--text.text--lighten-2 { color: #727272 !important; caret-color: #727272 !important; } .v-application .secondary.lighten-1 { background-color: #595959 !important; border-color: #595959 !important; } .v-application .secondary--text.text--lighten-1 { color: #595959 !important; caret-color: #595959 !important; } .v-application .secondary.darken-1 { background-color: #2c2c2c !important; border-color: #2c2c2c !important; } .v-application .secondary--text.text--darken-1 { color: #2c2c2c !important; caret-color: #2c2c2c !important; } .v-application .secondary.darken-2 { background-color: #171717 !important; border-color: #171717 !important; } .v-application .secondary--text.text--darken-2 { color: #171717 !important; caret-color: #171717 !important; } .v-application .secondary.darken-3 { background-color: #000000 !important; border-color: #000000 !important; } .v-application .secondary--text.text--darken-3 { color: #000000 !important; caret-color: #000000 !important; } .v-application .secondary.darken-4 { background-color: #000000 !important; border-color: #000000 !important; } .v-application .secondary--text.text--darken-4 { color: #000000 !important; caret-color: #000000 !important; } .v-application .accent { background-color: #82b1ff !important; border-color: #82b1ff !important; } .v-application .accent--text { color: #82b1ff !important; caret-color: #82b1ff !important; } .v-application .accent.lighten-5 { background-color: #ffffff !important; border-color: #ffffff !important; } .v-application .accent--text.text--lighten-5 { color: #ffffff !important; caret-color: #ffffff !important; } .v-application .accent.lighten-4 { background-color: #f8ffff !important; border-color: #f8ffff !important; } .v-application .accent--text.text--lighten-4 { color: #f8ffff !important; caret-color: #f8ffff !important; } .v-application .accent.lighten-3 { background-color: #daffff !important; border-color: #daffff !important; } .v-application .accent--text.text--lighten-3 { color: #daffff !important; caret-color: #daffff !important; } .v-application .accent.lighten-2 { background-color: #bce8ff !important; border-color: #bce8ff !important; } .v-application .accent--text.text--lighten-2 { color: #bce8ff !important; caret-color: #bce8ff !important; } .v-application .accent.lighten-1 { background-color: #9fccff !important; border-color: #9fccff !important; } .v-application .accent--text.text--lighten-1 { color: #9fccff !important; caret-color: #9fccff !important; } .v-application .accent.darken-1 { background-color: #6596e2 !important; border-color: #6596e2 !important; } .v-application .accent--text.text--darken-1 { color: #6596e2 !important; caret-color: #6596e2 !important; } .v-application .accent.darken-2 { background-color: #467dc6 !important; border-color: #467dc6 !important; } .v-application .accent--text.text--darken-2 { color: #467dc6 !important; caret-color: #467dc6 !important; } .v-application .accent.darken-3 { background-color: #2364aa !important; border-color: #2364aa !important; } .v-application .accent--text.text--darken-3 { color: #2364aa !important; caret-color: #2364aa !important; } .v-application .accent.darken-4 { background-color: #004c90 !important; border-color: #004c90 !important; } .v-application .accent--text.text--darken-4 { color: #004c90 !important; caret-color: #004c90 !important; } .v-application .error { background-color: #ff5252 !important; border-color: #ff5252 !important; } .v-application .error--text { color: #ff5252 !important; caret-color: #ff5252 !important; } .v-application .error.lighten-5 { background-color: #ffe4d5 !important; border-color: #ffe4d5 !important; } .v-application .error--text.text--lighten-5 { color: #ffe4d5 !important; caret-color: #ffe4d5 !important; } .v-application .error.lighten-4 { background-color: #ffc6b9 !important; border-color: #ffc6b9 !important; } .v-application .error--text.text--lighten-4 { color: #ffc6b9 !important; caret-color: #ffc6b9 !important; } .v-application .error.lighten-3 { background-color: #ffa99e !important; border-color: #ffa99e !important; } .v-application .error--text.text--lighten-3 { color: #ffa99e !important; caret-color: #ffa99e !important; } .v-application .error.lighten-2 { background-color: #ff8c84 !important; border-color: #ff8c84 !important; } .v-application .error--text.text--lighten-2 { color: #ff8c84 !important; caret-color: #ff8c84 !important; } .v-application .error.lighten-1 { background-color: #ff6f6a !important; border-color: #ff6f6a !important; } .v-application .error--text.text--lighten-1 { color: #ff6f6a !important; caret-color: #ff6f6a !important; } .v-application .error.darken-1 { background-color: #df323b !important; border-color: #df323b !important; } .v-application .error--text.text--darken-1 { color: #df323b !important; caret-color: #df323b !important; } .v-application .error.darken-2 { background-color: #bf0025 !important; border-color: #bf0025 !important; } .v-application .error--text.text--darken-2 { color: #bf0025 !important; caret-color: #bf0025 !important; } .v-application .error.darken-3 { background-color: #9f0010 !important; border-color: #9f0010 !important; } .v-application .error--text.text--darken-3 { color: #9f0010 !important; caret-color: #9f0010 !important; } .v-application .error.darken-4 { background-color: #800000 !important; border-color: #800000 !important; } .v-application .error--text.text--darken-4 { color: #800000 !important; caret-color: #800000 !important; } .v-application .info { background-color: #2196f3 !important; border-color: #2196f3 !important; } .v-application .info--text { color: #2196f3 !important; caret-color: #2196f3 !important; } .v-application .info.lighten-5 { background-color: #d4ffff !important; border-color: #d4ffff !important; } .v-application .info--text.text--lighten-5 { color: #d4ffff !important; caret-color: #d4ffff !important; } .v-application .info.lighten-4 { background-color: #b5ffff !important; border-color: #b5ffff !important; } .v-application .info--text.text--lighten-4 { color: #b5ffff !important; caret-color: #b5ffff !important; } .v-application .info.lighten-3 { background-color: #95e8ff !important; border-color: #95e8ff !important; } .v-application .info--text.text--lighten-3 { color: #95e8ff !important; caret-color: #95e8ff !important; } .v-application .info.lighten-2 { background-color: #75ccff !important; border-color: #75ccff !important; } .v-application .info--text.text--lighten-2 { color: #75ccff !important; caret-color: #75ccff !important; } .v-application .info.lighten-1 { background-color: #51b0ff !important; border-color: #51b0ff !important; } .v-application .info--text.text--lighten-1 { color: #51b0ff !important; caret-color: #51b0ff !important; } .v-application .info.darken-1 { background-color: #007cd6 !important; border-color: #007cd6 !important; } .v-application .info--text.text--darken-1 { color: #007cd6 !important; caret-color: #007cd6 !important; } .v-application .info.darken-2 { background-color: #0064ba !important; border-color: #0064ba !important; } .v-application .info--text.text--darken-2 { color: #0064ba !important; caret-color: #0064ba !important; } .v-application .info.darken-3 { background-color: #004d9f !important; border-color: #004d9f !important; } .v-application .info--text.text--darken-3 { color: #004d9f !important; caret-color: #004d9f !important; } .v-application .info.darken-4 { background-color: #003784 !important; border-color: #003784 !important; } .v-application .info--text.text--darken-4 { color: #003784 !important; caret-color: #003784 !important; } .v-application .success { background-color: #4caf50 !important; border-color: #4caf50 !important; } .v-application .success--text { color: #4caf50 !important; caret-color: #4caf50 !important; } .v-application .success.lighten-5 { background-color: #dcffd6 !important; border-color: #dcffd6 !important; } .v-application .success--text.text--lighten-5 { color: #dcffd6 !important; caret-color: #dcffd6 !important; } .v-application .success.lighten-4 { background-color: #beffba !important; border-color: #beffba !important; } .v-application .success--text.text--lighten-4 { color: #beffba !important; caret-color: #beffba !important; } .v-application .success.lighten-3 { background-color: #a2ff9e !important; border-color: #a2ff9e !important; } .v-application .success--text.text--lighten-3 { color: #a2ff9e !important; caret-color: #a2ff9e !important; } .v-application .success.lighten-2 { background-color: #85e783 !important; border-color: #85e783 !important; } .v-application .success--text.text--lighten-2 { color: #85e783 !important; caret-color: #85e783 !important; } .v-application .success.lighten-1 { background-color: #69cb69 !important; border-color: #69cb69 !important; } .v-application .success--text.text--lighten-1 { color: #69cb69 !important; caret-color: #69cb69 !important; } .v-application .success.darken-1 { background-color: #2d9437 !important; border-color: #2d9437 !important; } .v-application .success--text.text--darken-1 { color: #2d9437 !important; caret-color: #2d9437 !important; } .v-application .success.darken-2 { background-color: #00791e !important; border-color: #00791e !important; } .v-application .success--text.text--darken-2 { color: #00791e !important; caret-color: #00791e !important; } .v-application .success.darken-3 { background-color: #006000 !important; border-color: #006000 !important; } .v-application .success--text.text--darken-3 { color: #006000 !important; caret-color: #006000 !important; } .v-application .success.darken-4 { background-color: #004700 !important; border-color: #004700 !important; } .v-application .success--text.text--darken-4 { color: #004700 !important; caret-color: #004700 !important; } .v-application .warning { background-color: #fb8c00 !important; border-color: #fb8c00 !important; } .v-application .warning--text { color: #fb8c00 !important; caret-color: #fb8c00 !important; } .v-application .warning.lighten-5 { background-color: #ffff9e !important; border-color: #ffff9e !important; } .v-application .warning--text.text--lighten-5 { color: #ffff9e !important; caret-color: #ffff9e !important; } .v-application .warning.lighten-4 { background-color: #fffb82 !important; border-color: #fffb82 !important; } .v-application .warning--text.text--lighten-4 { color: #fffb82 !important; caret-color: #fffb82 !important; } .v-application .warning.lighten-3 { background-color: #ffdf67 !important; border-color: #ffdf67 !important; } .v-application .warning--text.text--lighten-3 { color: #ffdf67 !important; caret-color: #ffdf67 !important; } .v-application .warning.lighten-2 { background-color: #ffc24b !important; border-color: #ffc24b !important; } .v-application .warning--text.text--lighten-2 { color: #ffc24b !important; caret-color: #ffc24b !important; } .v-application .warning.lighten-1 { background-color: #ffa72d !important; border-color: #ffa72d !important; } .v-application .warning--text.text--lighten-1 { color: #ffa72d !important; caret-color: #ffa72d !important; } .v-application .warning.darken-1 { background-color: #db7200 !important; border-color: #db7200 !important; } .v-application .warning--text.text--darken-1 { color: #db7200 !important; caret-color: #db7200 !important; } .v-application .warning.darken-2 { background-color: #bb5900 !important; border-color: #bb5900 !important; } .v-application .warning--text.text--darken-2 { color: #bb5900 !important; caret-color: #bb5900 !important; } .v-application .warning.darken-3 { background-color: #9d4000 !important; border-color: #9d4000 !important; } .v-application .warning--text.text--darken-3 { color: #9d4000 !important; caret-color: #9d4000 !important; } .v-application .warning.darken-4 { background-color: #802700 !important; border-color: #802700 !important; } .v-application .warning--text.text--darken-4 { color: #802700 !important; caret-color: #802700 !important; }</style><script data-n-head="ssr" data-hid="gtm-script">if(!window._gtm_init){window._gtm_init=1;(function(w,n,d,m,e,p){w[d]=(w[d]==1||n[d]=='yes'||n[d]==1||n[m]==1||(w[e]&&w[e][p]&&w[e][p]()))?1:0})(window,navigator,'doNotTrack','msDoNotTrack','external','msTrackingProtectionEnabled');(function(w,d,s,l,x,y){w[x]={};w._gtm_inject=function(i){if(w.doNotTrack||w[x][i])return;w[x][i]=1;w[l]=w[l]||[];w[l].push({'gtm.start':new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],j=d.createElement(s);j.async=true;j.src='https://www.googletagmanager.com/gtm.js?id='+i;f.parentNode.insertBefore(j,f);};w[y]('GTM-M2J3TD6')})(window,document,'script','dataLayer','_gtm_ids','_gtm_inject')}</script><link rel="preload" href="/_nuxt/56ecfb3.js" as="script"><link rel="preload" href="/_nuxt/d93abf5.js" as="script"><link rel="preload" href="/_nuxt/css/041a87d.css" as="style"><link rel="preload" href="/_nuxt/0daeb4c.js" as="script"><link rel="preload" href="/_nuxt/css/11095d2.css" as="style"><link rel="preload" href="/_nuxt/767dc84.js" as="script"><link rel="preload" href="/_nuxt/css/1064788.css" as="style"><link rel="preload" href="/_nuxt/a0410e8.js" as="script"><link rel="preload" href="/_nuxt/css/89c7b3a.css" as="style"><link rel="preload" href="/_nuxt/0f2f0fe.js" as="script"><link rel="preload" href="/_nuxt/css/70bd42f.css" as="style"><link rel="preload" href="/_nuxt/15149e8.js" as="script"><link rel="stylesheet" href="/_nuxt/css/041a87d.css"><link rel="stylesheet" href="/_nuxt/css/11095d2.css"><link rel="stylesheet" href="/_nuxt/css/1064788.css"><link rel="stylesheet" href="/_nuxt/css/89c7b3a.css"><link rel="stylesheet" href="/_nuxt/css/70bd42f.css"> </head> <body > <noscript data-n-head="ssr" data-hid="gtm-noscript" data-pbody="true"><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M2J3TD6&" height="0" width="0" style="display:none;visibility:hidden" title="gtm"></iframe></noscript><div data-server-rendered="true" id="__nuxt"><div id="__layout"><div data-app="true" id="app" class="v-application manual v-application--is-ltr theme--light"><div class="v-application--wrap"><header class="v-sheet theme--light v-toolbar v-toolbar--extended v-app-bar v-app-bar--fixed" style="height:104px;margin-top:0px;transform:translateY(0px);left:0px;right:0px;background-color:var(--color-ui-01);z-index:10;"><div class="v-toolbar__content" style="height:56px;"><div class="row align-center justify-center"><div class="col-sm-4 col-lg-3 col-xl-2 col"></div> <div class="text-center col-sm-4 col-lg-4 col-xl-6 col"><a href="/en-us"><img height="28" preload="" src="/_nuxt/img/logo.27d6096.svg"></a></div> <div class="col-sm-4 col-md-4 col-lg-3 col-xl-2 col"></div></div></div><div class="v-toolbar__extension" style="height:48px;"><div class="row align-center"><div class="text-center col col-12 py-0"><h1 doc-id="T10202650" class="title-attention">AXIS OS Portal</h1></div></div></div></header>  <main class="v-main" style="padding-top:56px;padding-right:0px;padding-bottom:0px;padding-left:0px;"><div class="v-main__wrap"><div class="container manual container--fluid"><div class="row justify-center"><div class="col-md-4 col-xl-3 col"><a href="/en-us" class="mb-2 ml-8 px-2 v-btn v-btn--outlined v-btn--text theme--light v-size--default"><span class="v-btn__content"><span aria-hidden="true" class="v-icon notranslate theme--light"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" role="img" aria-hidden="true" class="v-icon__svg"><path d="M15.41,16.58L10.83,12L15.41,7.41L14,6L8,12L14,18L15.41,16.58Z"></path></svg></span>Go to Axis documentation</span></a> <a href="/download/release_notes_os_t10202650_2503.pdf" class="mb-2 px-2 v-btn v-btn--outlined v-btn--text theme--light v-size--default ml-2"><span class="v-btn__content"><span aria-hidden="true" class="v-icon notranslate theme--light"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" role="img" aria-hidden="true" class="v-icon__svg"><path d="M5,20H19V18H5M19,9H15V3H9V9H5L12,16L19,9Z"></path></svg></span> <span aria-hidden="true" class="v-icon notranslate theme--light"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" role="img" aria-hidden="true" class="v-icon__svg"><path d="M19 3H5C3.9 3 3 3.9 3 5V19C3 20.1 3.9 21 5 21H19C20.1 21 21 20.1 21 19V5C21 3.9 20.1 3 19 3M9.5 11.5C9.5 12.3 8.8 13 8 13H7V15H5.5V9H8C8.8 9 9.5 9.7 9.5 10.5V11.5M14.5 13.5C14.5 14.3 13.8 15 13 15H10.5V9H13C13.8 9 14.5 9.7 14.5 10.5V13.5M18.5 10.5H17V11.5H18.5V13H17V15H15.5V9H18.5V10.5M12 10.5H13V13.5H12V10.5M7 10.5H8V11.5H7V10.5Z"></path></svg></span></span></a>  <form novalidate="novalidate" class="v-form mb-2 mx-9"><div class="v-input search-field v-input--hide-details v-input--dense theme--light v-text-field v-text-field--enclosed v-text-field--outlined v-text-field--rounded"><div class="v-input__control"><div class="v-input__slot"><fieldset aria-hidden="true"><legend style="width:0px;"><span class="notranslate"></span></legend></fieldset><div class="v-text-field__slot"><label for="input-51163379" class="v-label theme--light" style="left:0px;right:auto;position:absolute;">Search</label><input id="input-51163379" type="text" value=""></div><div class="v-input__append-inner"><div></div></div><div class="v-input__append-inner"><div class="v-input__icon v-input__icon--append"><span aria-hidden="true" class="v-icon notranslate theme--light"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" role="img" aria-hidden="true" class="v-icon__svg"><path d="M9.5,3A6.5,6.5 0 0,1 16,9.5C16,11.11 15.41,12.59 14.44,13.73L14.71,14H15.5L20.5,19L19,20.5L14,15.5V14.71L13.73,14.44C12.59,15.41 11.11,16 9.5,16A6.5,6.5 0 0,1 3,9.5A6.5,6.5 0 0,1 9.5,3M9.5,5C7,5 5,7 5,9.5C5,12 7,14 9.5,14C12,14 14,12 14,9.5C14,7 12,5 9.5,5Z"></path></svg></span></div></div></div></div></div></form> <div class="v-treeview sticky v-treeview--hoverable v-treeview--dense theme--light"><div aria-expanded="false" class="v-treeview-node v-treeview-node--leaf v-treeview-node--click v-treeview-node--rounded"><div class="v-treeview-node__root"><div class="v-treeview-node__level"></div><div class="v-treeview-node__content"><div class="v-treeview-node__label"><a href="#about-axis-os"><span class="slim-link-cta slim-link-cta__underline toc__level-h1">About</span></a> </div></div></div></div><div aria-expanded="false" class="v-treeview-node v-treeview-node--leaf v-treeview-node--click v-treeview-node--rounded"><div class="v-treeview-node__root"><div class="v-treeview-node__level"></div><div class="v-treeview-node__content"><div class="v-treeview-node__label"><a href="#release-schedule"><span class="slim-link-cta slim-link-cta__underline toc__level-h1">Release schedule</span></a> </div></div></div></div><div aria-expanded="false" class="v-treeview-node v-treeview-node--click v-treeview-node--rounded"><div class="v-treeview-node__root"><button type="button" class="v-icon notranslate v-treeview-node__toggle v-icon--link theme--light"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" role="img" aria-hidden="true" class="v-icon__svg"><path d="M7.41,8.58L12,13.17L16.59,8.58L18,10L12,16L6,10L7.41,8.58Z"></path></svg></button><div class="v-treeview-node__content"><div class="v-treeview-node__label"><a href="#upcoming-breaking-changes"><span class="slim-link-cta slim-link-cta__underline toc__level-h1">Breaking changes</span></a> </div></div></div></div><div aria-expanded="false" class="v-treeview-node v-treeview-node--leaf v-treeview-node--click v-treeview-node--rounded"><div class="v-treeview-node__root"><div class="v-treeview-node__level"></div><div class="v-treeview-node__content"><div class="v-treeview-node__label"><a href="#next-axis-os-version"><span class="slim-link-cta slim-link-cta__underline toc__level-h1">Next AXIS OS version</span></a> </div></div></div></div><div aria-expanded="false" class="v-treeview-node v-treeview-node--leaf v-treeview-node--click v-treeview-node--rounded"><div class="v-treeview-node__root"><div class="v-treeview-node__level"></div><div class="v-treeview-node__content"><div class="v-treeview-node__label"><a href="#current-axis-os-version"><span class="slim-link-cta slim-link-cta__underline toc__level-h1">Current AXIS OS version</span></a> </div></div></div></div><div aria-expanded="false" class="v-treeview-node v-treeview-node--leaf v-treeview-node--click v-treeview-node--rounded"><div class="v-treeview-node__root"><div class="v-treeview-node__level"></div><div class="v-treeview-node__content"><div class="v-treeview-node__label"><a href="#open-source-library-support"><span class="slim-link-cta slim-link-cta__underline toc__level-h1">Open source library support</span></a> </div></div></div></div><div aria-expanded="false" class="v-treeview-node v-treeview-node--leaf v-treeview-node--click v-treeview-node--rounded"><div class="v-treeview-node__root"><div class="v-treeview-node__level"></div><div class="v-treeview-node__content"><div class="v-treeview-node__label"><a href="#software-bill-of-materials"><span class="slim-link-cta slim-link-cta__underline toc__level-h1">Software Bill of Materials</span></a> </div></div></div></div><div aria-expanded="false" class="v-treeview-node v-treeview-node--click v-treeview-node--rounded"><div class="v-treeview-node__root"><button type="button" class="v-icon notranslate v-treeview-node__toggle v-icon--link theme--light"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" role="img" aria-hidden="true" class="v-icon__svg"><path d="M7.41,8.58L12,13.17L16.59,8.58L18,10L12,16L6,10L7.41,8.58Z"></path></svg></button><div class="v-treeview-node__content"><div class="v-treeview-node__label"><a href="#axis-os-lifecycle"><span class="slim-link-cta slim-link-cta__underline toc__level-h1">AXIS OS lifecycle management</span></a> </div></div></div></div></div></div> <div class="mt-9 col-md-7 col-xl-5 col"><div id="search-result" class="mb-9 v-card v-sheet theme--light elevation-4 rounded-0 white" style="max-height:50vh;overflow-y:auto;z-index:4;"></div> <div class="row"><div class="col"><section id="navigation" toc-id="t10207450"> <div class="section__body"><p><span class="keep"><a class="link" href="https://help.axis.com/axis-os-release-notes">AXIS OS Release Notes</a></span> | <span class="keep"><a class="link" href="https://help.axis.com/axis-os-knowledge-base">AXIS OS Knowledge base</a></span> | <span class="keep"><a class="link" href="https://youtube.com/playlist?list=PLds2O4jvLhI5tdifpixi91-flQrOn6S1h&si=vsS3etHWYN_QxwoN">AXIS OS YouTube playlist </a></span>| <span class="keep"><a class="link" href="https://help.axis.com/axis-os-hardening-guide">AXIS OS Hardening Guide</a></span> | <span class="keep"><a class="link" href="https://help.axis.com/security-advisories">Security Advisories</a></span></p></div></section><section toc-id="t10220642"><div class="section__title"><h2 id="about-axis-os" toc-id="t10220642" class="title-attention">About</h2></div> <div class="section__body"><p>AXIS OS is our operating system for edge devices. It’s used in more than 400 products with the broadest partner application reach in the security industry. It’s a Linux-based OS that’s built around openness, transparency and cybersecurity.</p><p>We have three support tracks: <a class="anchor link" data-anchor="active-track" href="#active-track">Active track</a>, <a class="anchor link" data-anchor="lts-track" href="#lts-track">Long-term support track</a>, and <a class="anchor link" data-anchor="pss" href="#pss">Product-specific support</a>. <br>See <a class="anchor link" data-anchor="axis-os-lifecycle" href="#axis-os-lifecycle">AXIS OS lifecycle management</a> for more details.</p><p><span style="font-style: italic;"><span style="font-weight: bold;">AXIS OS support overview</span></span></p><img alt="" height="706" src="/image/t10208092.png" width="2316"><figcaption><sub>The active track releases a new version every 2–3 months where only the latest version is supported. The LTS tracks are created every two years and are supported and maintained for about 5 years.</sub></figcaption></div></section><section toc-id="t10186724"><div class="section__title"><h2 id="release-schedule" toc-id="t10186724" class="title-attention">Release schedule</h2></div> <div class="section__body"><p>In the schedule below you can find information about upcoming releases on the active track and the LTS tracks.</p><table class="knowledge-table table table-bordered"><tbody><tr class="knowledge-table-row"><td class="knowledge-table-cell"><span style="font-weight: bold;">Version</span></td><td class="knowledge-table-cell"><span style="font-weight: bold;">Track</span></td><td class="knowledge-table-cell"><span style="font-weight: bold;">Preliminary release date</span></td><td class="knowledge-table-cell"><span style="font-weight: bold;">Planned features and updates</span></td></tr><tr class="knowledge-table-row"><td class="knowledge-table-cell"><span class="keep">12.4</span></td><td class="knowledge-table-cell">Active</td><td class="knowledge-table-cell">April 2025</td><td class="knowledge-table-cell"><ul class="knowledge-list knowledge-list-bullets"><li><p>cURL version 8.12.0</p></li><li><p>AXIS CVE: CVE-2025-0325</p></li></ul></td></tr><tr class="knowledge-table-row"><td class="knowledge-table-cell"><span class="keep">11.11</span></td><td class="knowledge-table-cell"><span class="keep">LTS 2024</span></td><td class="knowledge-table-cell">March 2025</td><td class="knowledge-table-cell"><ul class="knowledge-list knowledge-list-bullets"><li><p>OpenSSL vesion 3.0.16 and 1.1.1zb</p></li><li><p>cURL version 8.12.0</p></li><li><p> AXIS CVE: CVE-2025-0324, CVE-2025-0361 and CVE-2024-47261</p></li></ul></td></tr><tr class="knowledge-table-row"><td class="knowledge-table-cell"><span class="keep">10.12</span></td><td class="knowledge-table-cell"><span class="keep">LTS 2022</span></td><td class="knowledge-table-cell">March/April 2025</td><td class="knowledge-table-cell"><ul class="knowledge-list knowledge-list-bullets"><li><p>OpenSSL vesion 1.1.1zb</p></li><li><p>cURL version 8.12.0</p></li><li><p> AXIS CVE: CVE-2024-47261</p></li></ul></td></tr><tr class="knowledge-table-row"><td class="knowledge-table-cell"><span class="keep">9.80</span></td><td class="knowledge-table-cell"><span class="keep">LTS 2020</span></td><td class="knowledge-table-cell">April 2025</td><td class="knowledge-table-cell"><ul class="knowledge-list knowledge-list-bullets"><li><p>OpenSSL version 1.1.1zb</p></li><li><p>cURL version 8.12.0</p></li><li><p> AXIS CVE: CVE-2024-47261</p></li></ul></td></tr><tr class="knowledge-table-row"><td class="knowledge-table-cell"><span class="keep">8.40</span></td><td class="knowledge-table-cell"><span class="keep">Product-specific support</span></td><td class="knowledge-table-cell">May 2025</td><td class="knowledge-table-cell"><ul class="knowledge-list knowledge-list-bullets"><li><p>cURL version 8.12.0</p></li><li><p>OpenSSL version 1.1.1zb</p></li><li><p> AXIS CVE: CVE-2025-0325</p></li></ul></td></tr><tr class="knowledge-table-row"><td class="knowledge-table-cell"><span class="keep">6.50</span></td><td class="knowledge-table-cell"><span class="keep">Product-specific support</span></td><td class="knowledge-table-cell">March 2025</td><td class="knowledge-table-cell"><ul class="knowledge-list knowledge-list-bullets"><li><p>cURL version 8.11.1</p></li><li><p> AXIS CVE: CVE-2024-47262</p></li></ul></td></tr></tbody></table><p></p><ul class="knowledge-list knowledge-list-bullets"><li><p>For highlights and detailed release notes on AXIS OS releases, visit <a class="link" href="https://help.axis.com/axis-os-release-notes#axis-os-11">AXIS OS Release Notes</a>.</p></li><li><p>Subscribe to the <a class="link" href="https://youtube.com/playlist?list=PLds2O4jvLhI5tdifpixi91-flQrOn6S1h&si=vsS3etHWYN_QxwoN">AXIS OS YouTube playlist</a> to conveniently stay updated and informed.</p></li><li><p>Go to to read more about scheduled and current AXIS OS releases.</p></li><li><p>For downloads, visit <a class="link" href="https://www.axis.com/support/device-software">Download device software</a> page.</p></li><li><p> To get the latest updates to your RSS feed, subscribe to the <img alt="" class="inline" height="28" src="/image/t10146754.png" style="vertical-align:middle;" width="28"><a class="link" href="http://feeds.axis.com/axisfirmware">product firmware feed</a>.</p></li></ul></div></section><section toc-id="t10194568"><div class="section__title"><h2 id="upcoming-breaking-changes" toc-id="t10194568" class="title-attention">Breaking changes</h2></div> <div class="section__body"><p>Axis launches a new active track every two years, transitioning the previous active track into a long-term support (LTS) phase.<br> In September 2024, AXIS OS 11 entered the LTS 2024 phase, while the new active track, AXIS OS 12, was introduced. </p><p>Each new active track focuses on delivering innovative features to advance AXIS OS and enhance its cybersecurity.<br>In addition, pre-announced breaking changes are introduced at the start of the new track, communicated well in advance, with further changes during the lifecycle of the active track taking place but with limited impact.</p><img alt="" height="248" src="/image/t10198582.png" width="801"><p><br>A breaking change is an intentional modification which will break backwards compatibility. While Axis consistently strives to maintain backward compatibility, introducing breaking changes is sometimes necessary to:</p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;">Improve cybersecurity</span>: Axis may remove obsolete features or modify existing features to enhance security.</p></li><li><p><span style="font-weight: bold;">Update functionality and improve usability</span>: Axis enhances existing functionality by implementing new default settings or introducing more advanced features to expand use cases.</p></li></ul><p>In both scenarios, Axis provides an alternative method for accomplishing the same tasks and communicates these changes in advance. Furthermore,<span style="font-weight: bold;"><span style="font-style: italic;"> the active track is the only place where these changes can be made, as maintaining compatibility is the primary focus of LTS tracks.</span></span><span style="font-style: italic;"></span> These changes are usually implemented after a new LTS track has been established, giving users sufficient time to adapt while maintaining security measures.</p><div class="warning"><div class="note">Note</div><div class="information"><p class="warning-paragraph"> If you experience issues after upgrading to AXIS OS 12, utilize the rollback option to let the device revert back to its previous AXIS OS version. See guidelines <a class="link" href="https://help.axis.com/axis-os-knowledge-base#how-to-rollback">here</a>. We recommend that you keep at least one device running AXIS OS 12, generate a server report and contact Axis Technical Support for troubleshooting assistance or guidance.</p></div></div></div></section><section toc-id="t10204853"><div class="section__title"><h3 id="planned-breaking-changes" toc-id="t10204853">Planned</h3></div> <div class="section__body"><p></p></div></section><section toc-id="t10201943"><div class="section__title"><h4 id="changes-in-axis-os-13" toc-id="t10201943">Changes in AXIS OS 13</h4></div> <div class="section__body"><p>Changes that apply to the first version of AXIS OS 13, coming in September 2026. Please note that the changes can be adjusted in future.</p><p><span style="font-weight: bold;">ACAP related changes:</span></p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Signed ACAP applications</span></span></p><p>From AXIS OS 13.0, the option to allow unsigned applications is removed and only signed ACAP applications are allowed.</p><p><br><img alt="" class="inline" height="334" src="/image/t10207644.png" style="vertical-align:middle;" width="665"></p><p>VAPIX API parameters that will be removed :<br>/axis-cgi/applications/config.cgi?action=set&name=AllowUnsigned&value=true<br>/axis-cgi/applications/config.cgi?action=set&name=AllowUnsigned&value=false</p><p> Running unsigned ACAPs from any previous version of AXIS OS when upgrading to AXIS OS 13 will not be affected and the ACAP will continue to function normally. Only new ACAP installations in AXIS OS 13 are affected. </p><p><span style="font-weight: bold;">Why is this change introduced?</span> To increase trust in ACAP applications and comply with international regulations and best practices for secure software delivery. <br><span style="font-weight: bold;">How can it affect me?</span> New ACAPs to be installed in AXIS OS 13 must be signed, otherwise the ACAP installation will fail.</p></li></ul><p><br></p><p><span style="font-weight: bold;">Security:</span></p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Password complexity enforcement</span></span></p><p>The user is currently supported with a password strength indicator for selecting secure passwords for service accounts. However, the user might select insecure passwords anyway. It is planned to introduce a password complexity enforcement to enforce using secure-considered passwords when accessing an Axis device.</p><p><br>Afterward, it will not be possible to use insecure password combinations. It is expected that the password complexity enforcement will be standardized and will require a minimum password length of 14 characters including small and big letters, special signs and numbers, alternatively small and big letters with a password length of 64-characters. <br>More information to come. The decision on when to introduce password complexity has not been made yet but will be communicated in time.</p><p><br></p><p><img alt="" class="inline" height="400" src="/image/t10198465.png" style="vertical-align:middle;" width="439"></p><p><br></p><p><span style="font-weight: bold;">Why is this change introduced?</span> To increase the cybersecurity level.<br><img alt="" class="inline" height="609" src="/image/t10204638.png" style="vertical-align:middle;" width="2772"><br><span style="font-weight: bold;">How can it affect me?</span> Will be updated shortly.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">HTTPS-only enforcement</span></span></p><p>The current default behavior of Axis devices in factory defaulted state is that HTTP and HTTPS are both enabled allowing for a flexible choice on which protocol to use to connect to the Axis device. Axis, since many years, has given the recommendation to configure the Axis device to HTTPS-only during initial configuration according to the <a class="link" href="https://help.axis.com/axis-os-hardening-guide#https"> AXIS OS Hardening Guide</a>. Please see the current default settings below.</p><p><br><img alt="" class="inline" height="361" src="/image/t10198463.png" style="vertical-align:middle;" width="725"></p><p>This default behavior is likely to change in order to increase overall default security and protect communication between the Axis device and the human user as well as applications. Axis has plans to change the default behavior so that HTTP communication will be disabled, and HTTPS-only communication is the only enabled protocol to be used in factory defaulted state.</p><p><br><img alt="" class="inline" height="298" src="/image/t10198464.png" style="vertical-align:middle;" width="563"></p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> To increase the cybersecurity level.<br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using HTTP, it will not work correctly with AXIS OS 13 or higher.</p><p></p><p><br></p></li></ul></div></section><section toc-id="t10223152"><div class="section__title"><h4 id="changes-in-axis-os-14" toc-id="t10223152">Changes in AXIS OS 14</h4></div> <div class="section__body"><p>Changes that apply to the first version of AXIS OS 14, coming in September 2028. Please note that the changes can be adjusted in future.</p><p><span style="font-weight: bold;">API changes:</span></p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removal of unofficial certificate management</span></span></p><p>The unofficial and externally undocumented custom certificate management API with the VAPIX endpoints <span style="font-style: italic;">/axis-cgi/certappmgmt.cgi</span> and <span style="font-style: italic;">/axis-cgi/certmgmt.cgi</span> will be removed. For supported AXIS OS certificate management and enrollment APIs, please refer to the <a class="link" href="https://www.axis.com/vapix-library/subjects/t10175981/section/t10035974/display">VAPIX Library</a>. </p><p><span style="font-weight: bold;">Why is this change introduced?</span> Unofficial and undocumented APIs shall not be used due to the security risk. Thus, it is removed since there are other VAPIX APIs that can be used instead. <br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this API, it will not work correctly with AXIS OS 14 or higher.</p></li></ul></div></section><section toc-id="t10204852"><div class="section__title"><h3 id="applied-breaking-changes" toc-id="t10204852">Applied</h3></div> <div class="section__body"><p></p></div></section><section toc-id="t10214433"><div class="section__title"><h4 id="changes-in-axis-os-12-1" toc-id="t10214433">Changes in AXIS OS 12.1</h4></div> <div class="section__body"><p><span style="font-weight: bold;">Edge Storage:</span></p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removal of vFAT</span></span></p><p>The ability to format SD cards to the vFAT system file will be removed. However, they can still be used as before. A long time ago, SD cards were delivered with vFAT as the standard file system for cards up to 32GB. Since such SD cards are no longer used, the usefulness of vFAT is very limited.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> Axis has since start recommended Ext 4. vFat should never be used.<br><span style="font-weight: bold;">How can it affect me?</span>If necessary, you will need to format the SD card outside the device.</p><p><img alt="" class="inline" height="502" src="/image/t10207682.png" style="vertical-align:middle;" width="842"></p></li></ul><p><span style="font-weight: bold;">Network & Discovery:</span></p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Disabled UPnP discovery protocol</span></span></p><p>Axis devices currently have UPnP and Bonjour enabled in factory defaulted state for general device discovery. The Bonjour protocol allows for device detection within the local subnet where the device is located (example: 192.168.1.0/24). The UPnP protocol allows device discovery across networks (example: 192.168.1.0/24 and 192.168.2.0/24) but only if multicast-routing is properly configured. Axis believes that the device detection within the local subnet is the main use case for a discovery protocol and therefore will disable UPnP in factory defaulted devices moving forward. This will also lower the attack surface of the device and increase the overall network security. The UPnP protocol remains available in Axis devices with the option for the user to enable it if needed.</p><p>VAPIX API parameter: <span style="font-style: italic;">root.Network.UPnP.Enabled</span></p><p><br><img alt="" class="inline" height="292" src="/image/t10207647.png" style="vertical-align:middle;" width="851"></p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> To lower the attack surface of the device and increase the overall device security.<br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software only using UPnP for device discovery, it will not work correctly with AXIS OS 12.1 or higher and users need to enable UPnP first on the Axis device.</p></li></ul><p><span style="font-weight: bold;">Security:</span></p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Basic authentication for HTTPS connections</span></span></p><p>Axis devices perform digest authentication when serving both HTTP and HTTPS connections. Since HTTPS connections are preferred for increased security, Axis will change the default behavior so that basic authentication is used for HTTPS connections only by introducing a new authentication policy mode called "Recommended". The authentication policy for HTTP & the RTSP server will not change in this mode. More information about the authentication policy can be found in the <a class="link" href="https://www.axis.com/vapix-library/subjects/t10175981/section/t10007717/display?section=t10007717-t10158867">VAPIX Library</a>. Using basic authentication in HTTPS connections is IT-industry standard and allows Axis devices to operate in a well-defined and common practice as well. Digest authentication will still be kept for serving for unencrypted HTTP connections. Using HTTPS only is the recommended operational mode for Axis devices.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> To follow the IT-industry standard.<br><span style="font-weight: bold;">How can it affect me?</span> If you use digest authentication for HTTPS connection, it will not work correctly with AXIS OS 12.1 or higher.</p></li></ul></div></section><section toc-id="t10201932"><div class="section__title"><h4 id="changes-in-axis-os-12" toc-id="t10201932">Changes in AXIS OS 12.0</h4></div> <div class="section__body"><img alt="" height="465" src="/image/t10209761.png" width="676"><p><br>Check out the <a class="link" href="https://www.youtube.com/watch?v=964zGkbpkDY">AXIS OS 12 Technical Update - Breaking Changes</a> video, to learn more about the upcoming changes.</p><p></p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removal of the old web interface</span></span></p><p>The old web interface, also called “<a class="link" href="https://help.axis.com/en-us/axis-os-knowledge-base#axis-os-web-version-b">AXIS OS web version B</a>”, will be removed.</p><p><span style="font-weight: bold;">Why is this change introduced?</span> The old web interface is no longer needed since the <a class="link" href="https://help.axis.com/en-us/axis-os-knowledge-base#axis-os-web-version-c">new interface</a> has all implemented features . It is removed to save memory space on the device and to simplify both usage and maintenance. Additionally, the old web interface used a number of outdated libraries and removing it will make the device more secure.<br><span style="font-weight: bold;">How can it affect me?</span> The new web interface will be displayed after upgrade.</p><p><br></p></li></ul><p><span style="font-weight: bold;">Security:</span></p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Disabled HTTP Port 80 redirects</span></span></p><p>In previous security penetration tests, Axis was advised to disable HTTP Port 80 redirects in order to enhance security and to prevent information leakage. Currently, Axis devices are configured for HTTPS-only, but the HTTP port 80 redirects are enabled to inform users/clients that communication is not permitted on port 80 and redirecting them automatically to port 443 instead. Axis will follow the general recommendation provided by third-party penetration test laboratories and will deactivate HTTP port 80 redirects when the device is set to HTTPS-only mode.</p><p><br><img alt="" class="inline" height="408" src="/image/t10198469.png" style="vertical-align:middle;" width="1473"></p><p><br></p><p>To test the possible impact, configure your Axis device for HTTPS only and configure a firewall rule in AXIS OS 11.9 as shown below, where the Axis device would effectively block communication on port 80 for a specific client trying to connect.</p><p><br></p><p><img alt="" class="inline" height="443" src="/image/t10205440.png" style="vertical-align:middle;" width="1320"></p><p><img alt="" class="inline" height="608" src="/image/t10205441.png" style="vertical-align:middle;" width="1320"></p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> To lower the attack surface of the device and increase the overall device security.<br><span style="font-weight: bold;">How can it affect me?</span> If you access the Axis device via HTTP, it will not work correctly with AXIS OS 12.0 or higher. Please use HTTPS instead.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removed support for TLS 1.0/1.1 HTTPS connections</span></span></p><p>Axis devices support modern encryption technology through TLS 1.2/1.3, which is used by default for HTTPS connections. However, there is also an option to enable older, outdated and insecure TLS 1.0/1.1 versions for backward compatibility with legacy systems that cannot support more secure HTTPS connections. Axis will completely remove TLS 1.0/1.1 versions for HTTPS connections to increase overall security and prevent users from accidentally enabling these protocol versions.</p><p>VAPIX API Parameter: <span style="font-style: italic;">root.HTTPS.AllowTLS1 </span>and<span style="font-style: italic;"> root.HTTPS.AllowTLS11</span></p><p><br><img alt="" class="inline" height="1032" src="/image/t10198467.png" style="vertical-align:middle;" width="2189"></p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> It is obsolete, and keeping it might be a security threat.<br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using TLS 1.0/1.1 HTTPS connections, it will not work correctly with AXIS OS 12.0 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removed support for OpenSSL 1.1.1</span></span></p><p>Since AXIS OS 11.6 (August 2023), Axis devices support simultaneously version 1.1.1 and 3.0 of the cryptographic software backend OpenSSL. To allow for smooth transition, OpenSSL 1.1.1 will still be supported until LTS 2024 track is launched and in that track. With AXIS OS 12, OpenSSL 1.1.1 support will be removed. Patches and security updates of OpenSSL 1.1.1 will still be supported on active AXIS OS long-term support tracks as Axis has signed a support contract with the OpenSSL foundation to receive prolonged support. </p><p></p><p>Note that upcoming changes may affect ACAPs. To ensure compatibility and security, it is recommended to use <span class="keep"><a class="link" href="https://github.com/AxisCommunications/acap-native-sdk-examples/tree/main/curl-openssl">OpenSSL 3.X</a></span>, which is available in ACAP Native SDK 1.14 / AXIS OS 11.10. Alternatively, ACAPs can <a class="link" href="https://github.com/AxisCommunications/acap-native-sdk-examples/tree/main/utility-libraries/openssl_curl_example">embed a custom cryptographic library</a> to meet their specific needs.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> It is obsolete as the active track runs a newer version.<br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using OpenSSL 1.1.1, it will not work correctly with AXIS OS 12.0 or higher.</p></li></ul><p><br></p><p><span style="font-weight: bold;">Network & Discovery:</span></p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">IPv4 address changes</span></span></p><p>To date, Axis devices have never been IPv4 compliant following the corresponding RFC framework. That resulted in the Axis device having a default IP-address which is 192.168.0.90/24. This circumstance leads to network related issues that we want to resolve. For instance, if no DHCP server is available on the network, the default IP address of Axis devices currently is 192.168.0.90/24 regardless of whether anyone on the same network segment already uses the same IP address. This may cause service interruptions for other devices if such IP address conflict occurs. At the same time, the link-local address (169.254.x.x/16) is enabled by default regardless of whether it’s used, which is not in compliance with the RFC standard.</p><p><br></p><p>With the above changes in place, there will be no default IP addresses of AXIS OS devices anymore. The Axis OS devices will use the IP addresses either from a DHCP server or statically configured address. The devices will only fall back to link-local addresses if there is an IP address conflict detected, or a DHCP server is unavailable in the network. More information regarding the IPv4 addressing change can be found <a class="link" href="https://help.axis.com/axis-os-knowledge-base#ipv4-compliant-mode">here</a>. </p><p><br><span style="font-weight: bold;">Why is this change introduced?</span></p><li class="knowledge-list-item-skip knowledge-list-item-sublist"><ul class="knowledge-list knowledge-list-bullets"><li><p>To be completely RFC IPv4 compliant.</p></li><li><p>Disable link-local address when it is not used. </p></li><li><p>Better user experience for our customers when multiple factory-defaulted Axis devices are placed on the same network simultaneously.</p></li><li><p>Increase robustness and detect IP address conflicts.</p></li><li><p><span style="font-weight: bold;">How can it affect me?</span> Affects during installation, AXIS devices will request IP adress from the network it attaches to etc DHCP.<br><br></p></li></ul></li></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Disabled WS-Discovery protocol</span></span></p><p>Axis devices currently have the WS-Discovery (WebService-Discovery) protocol enabled in factory defaulted state as additional option for ONVIF-related device discovery. However, the ONVIF interface is not enabled in factory defaulted state which makes the availability of the WS-Discovery protocol by default obsolete. Axis will adapt the default behavior and will disable the WS-discovery protocol in factory defaulted state. This means a user need to enable the WS-discovery protocol if desired. </p><p>VAPIX API parameter: <span style="font-style: italic;">WebService.DiscoveryMode.Discoverable</span></p><p><br><img alt="" class="inline" height="292" src="/image/t10207647.png" style="vertical-align:middle;" width="851"></p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> To lower the network footprint and increase the cybersecurity level of an Axis device when ONVIF is not being used.<br><span style="font-weight: bold;">How can it affect me?</span> You will not be able to discover the device until WS-Discovery has been enabled.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Possibility to disable Basic Device Info VAPIX API</span></span><br>The <a class="link" href="https://www.axis.com/vapix-library/subjects/t10175981/section/t10132180/display">Basic Device Information</a> VAPIX API allows to retrieve general information about the Axis product with no authentication. This is useful for device discovery and profiling during network and application onboarding. Axis will implement an additional VAPIX parameter that will allow the user to disable the basic device information API if needed. The ability for the user to disable this VAPIX API may be considered a behavioral change if unknown.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> Provide the ability to reduce the attack surface and information leakage of the device, increasing the overall security resilience of the network.<br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this API after onboarding, it will not work correctly with AXIS OS 12.0 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removal of releaseinfo.cgi</span></span><br>The <span style="font-style: italic;">axis-release/releaseinfo.cgi</span> VAPIX API has been removed. It is recommended to use the Basic Device Information VAPIX API instead, see more info in the <a class="link" href="https://www.axis.com/vapix-library/">VAPIX Library</a>.</p><p> Example output of <span style="font-style: italic;">axis-release/releaseinfo.cgi</span>:</p><p><code class="text-code-example">part=6975649029</code></p><p><code class="text-code-example">version:11.2.53</code></p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> It is obsolete and replaced by a different API.<br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removal of getBrand.cgi</span></span><br>The previously deprecated VAPIX API <span style="font-style: italic;">axis-cgi/prod_brand_info/getbrand.cgi</span> has been removed. It is recommended to use the Basic Device Information VAPIX API instead, see more info in the <a class="link" href="https://www.axis.com/vapix-library/">VAPIX Library</a>. Please find below an example output of the information that was possible to receive through getBrand.cgi, all the information is still available and covered in the referenced Basic Device Information VAPIX API.</p><p> Example output of <span style="font-style: italic;">getBrand.cgi</span>:</p><p><code class="text-code-example">Brand.Brand=AXIS</code></p><p><code class="text-code-example">Brand.ProdFullName=AXIS P3265-LV Dome Camera</code></p><p><code class="text-code-example">Brand.ProdNbr=P3265-LV</code></p><p><code class="text-code-example">Brand.ProdShortName=AXIS P3265-LV</code></p><p><code class="text-code-example">Brand.ProdType=Dome Camera</code></p><p><code class="text-code-example">Brand.ProdVariant=</code></p><p><code class="text-code-example">Brand.WebURL=http://www.axis.com</code></p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> It is obsolete and replaced by a different API.<br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removal of network filter API</span></span></p><p>The current IP-filtering VAPIX API will be replaced by a more feature-rich firewall application that can be configured through JSON REST API. The new firewall service will be available in AXIS OS 11.8 (January 2024) and can be used from there on. <br><img alt="" class="inline" height="276" src="/image/t10207646.png" style="vertical-align:middle;" width="747"><br>The legacy network filter API with the following below parameters will be removed in AXIS OS 12:</p><p><span style="font-style: italic;">Network.Filter.Enabled</span></p><p><span style="font-style: italic;">Network.Filter.Input.AcceptAddresses</span></p><p><span style="font-style: italic;">Network.Filter.Input.Policy</span></p><p><span style="font-style: italic;">Network.Filter.Log.Enabled</span></p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> It is obsolete and replaced by the new host-based firewall.<br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.</p></li></ul><p><br></p><p><span style="font-weight: bold;">Edge Storage:</span></p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removed support for SMB 1.0 and 2.0</span></span></p><p>The Server Message Block Protocol (SMB) is widely used for mounting network shares when storing recordings. While secure versions of the SMB protocol are supported and available in Axis devices (2.1, 3.0, 3.02 and 3.1.1), the insecure versions (1.0 and 2.0) are still available to use but disabled in factory defaulted state. Axis will remove version 1.0 and 2.0 completely to increase the overall security and to prevent users from enabling these protocol versions by mistake.</p><p><img alt="" class="inline" height="445" src="/image/t10198468.png" style="vertical-align:middle;" width="491"></p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> It is obsolete, and keeping it might be a security threat.<br><span style="font-weight: bold;">How can it affect me?</span> If you have a storage connection requiring these versions, they will not work anymore.</p></li></ul><p><br></p><p><span style="font-weight: bold;">ACAP application related changes:</span></p><div class="warning"><div class="notice">NOTICE</div><div class="information"><p class="warning-paragraph">Before upgrading to AXIS OS 12.0 or higher, note that certain applications require updates. See the respective documentation for more information.</p><ul class="knowledge-list knowledge-list-bullets"><li><span style="font-weight: bold;">AXIS Perimeter Defender 3.6.0 required. </span>Versions 3.5.1 and earlier are not compatible with AXIS OS 12.0 or higher. Follow these <a class="link" href="https://www.axis.com/dam/public/0d/2c/0a/how-to-upgrade-to-axis-os-12-with-axis-perimeter-defenderpdf-en-US-452254.pdf">instructions</a> to perform the upgrade correctly.</li><li><span style="font-weight: bold;">AXIS License Plate Verifier 2.12.8 required.</span> Versions 2.8.4 or earlier are not compatible with AXIS 12 or higher. Follow these <a class="link" href="https://www.axis.com/dam/public/10/59/21/how-to-upgrade-to-axis-os-12-with-axis-license-plate-verifierpdf-en-US-452259.pdf">instructions</a> to perform the upgrade correctly.</li><li><span style="font-weight: bold;">AXIS People Counter 5.0.5 required. </span>Versions 4.6.108 and earlier are not compatible with AXIS OS 12 or higher. Follow these <a class="link" href="https://www.axis.com/dam/public/bf/ff/6c/how-to-upgrade-to-axis-os-12-with-axis-people-counterpdf-en-US-452253.pdf">instructions</a> to perform the upgrade correctly.</li></ul></div></div><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removal of root-privileges</span></span></p><p>Root-privileged access to Axis products and ACAP applications has been removed indefinitely without the possibility to enable it. The previously available parameter in AXIS OS 11 to enable root privileges has been removed. This change applies to the factory default settings as well as when upgrading to AXIS OS 12 from any previous version of AXIS OS. </p><p><br>This change increases ACAP confidentiality by better protecting their data and secrets, preventing information leakage and increasing AXIS OS system integrity. Please read the <a class="link" href="https://www.axis.com/developer-community/news/axis-os-root-acap-signing">full guide</a> for more information.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> To increase the security on the device. <br><span style="font-weight: bold;">How can it affect me?</span> <br>ACAPs that do not use root-privileges are not affected. <br>ACAPs with root privileges, will not work with AXIS OS 12.0 or higher. Check the installed ACAP applications carefully! Make sure they are working properly. If possible, select the LTS 2024 track.<br></p><p><br><span style="font-weight: bold;">Possible scenarios where failures could be expected are:</span><br>The ACAP cannot run because it tries to use the previously available root user with root privileges.<br>The post-install script may be using root-privileges, which prevents the ACAP from being installed or run. <br>The pre-uninstall script may be using root-privileges, which may prevent ACAP data from being cleaned up at installation.<br>The ACAP tries to access file system resources or functionality that is locked behind root-privileges.<br>The ACAP applications that include or need access to security-sensitive functionality will not work anymore. For example, VPN-capable solutions based on Tailscale, ZeroTier, IPsec, OpenVPN and WireGuard that may have been deployed as an ACAP previously, will not work in AXIS OS 12. Axis is looking into how and if a VPN-client can be embedded into the AXIS OS operating system natively.</p><p><br></p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Signed ACAP applications</span></span><br> From AXIS OS 12.0, the option to allow unsigned apps will be disabled in factory defaulted state. To upload unsigned ACAPs, users must enable this option. This only applies to factory-defaulted products running AXIS OS 12 or higher.</p><p><br><img alt="" class="inline" height="334" src="/image/t10207644.png" style="vertical-align:middle;" width="665"></p><p>VAPIX API parameters:<br><span style="font-style: italic;"> /axis-cgi/applications/config.cgi?action=set&name=AllowUnsigned&value=true<br> /axis-cgi/applications/config.cgi?action=set&name=AllowUnsigned&value=false </span></p><p><br>Running unsigned ACAPs from any previous version of AXIS OS when upgrading to AXIS OS 12 will have no impact and the ACAP will continue to function normally. For more information and a timeline, see <a class="link" href="https://www.axis.com/developer-community/news/axis-os-root-acap-signing">Additional security in AXIS OS and ACAP applications.</a><br><br><span style="font-weight: bold;">Why is this change introduced?</span> To lower the attack surface of the device and increase the overall device security.<br><span style="font-weight: bold;">How can it affect me?</span> For factory default devices, you will need to enable Allow unsigned apps.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">ACAP installation behaviour</span></span></p><p>The ACAP installation is now aborted if the post-install script exit on EX_NOPERM (77). Previously, the ACAP is installed nevertheless and warnings were printed in the log files. Uninstall will happen regardless of pre-uninstall script error and will write the error code to the log.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> To increase the ACAPS reliability on the market.<br><span style="font-weight: bold;">How can it affect me?</span> ACAP vendors are informed and should compile a new ACAP version without errors if affected.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removal of Basic analytics ACAP applications</span></span></p><p>Due to updates to our framework, it is not possible to support some older types of ACAP applications and they will therefore be removed. <br>This applies to Axis Basic Enter-Exit, Axis Basic Object Counter and Axis Basic Object Removed</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> Due to architectural changes.<br><span style="font-weight: bold;">How can it affect me?</span> If you are using any of these ACAPs, do not upgrade until the system has a verified replacer.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removal of libcapture library</span></span></p><p>The libcapture library for ACAPs is obsolete and will be removed. It is recommended to use the Video capture API instead. For more information, visit the <a class="link" href="https://axiscommunications.github.io/acap-documentation/docs/api/native-sdk-api.html#video-capture-api-vdo">ACAP SDK Documentation</a>.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> It is obsolete, and keeping it might be a security threat.<br><span style="font-weight: bold;">How can it affect me?</span> If you have an ACAP using this library, it will not work correctly with AXIS OS 12.0 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removal of vaconfig.cgi</span></span></p><p>The ACAP applications managed by the vaconfig.cgi API is no longer supported, this configuration and management API is therefore obsolete and will be removed.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> It is obsolete, and keeping it might be a security threat. <br><span style="font-weight: bold;">How can it affect me?</span> If you have an ACAP using this library, it will not work correctly with AXIS OS 12.0 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removal of ACAP Computer Vision SDK support</span></span></p><p>The ability to enable ACAP Computer Vision SDK support will be removed for the listed products because they only have 1 GB of memory. <br><span style="text-decoration: underline;">Applies to</span>: AXIS D2210–VE, AXIS M3215-LVE, AXIS M3216-LVE, AXIS M5526-E, AXIS P1465-LE, AXIS P1465-LE-3, AXIS P3265-LV/-LVE/-V and AXIS P3265-LVE-3</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> Running the Computer Vision SDK on the product will consume too much memory and may render the product inoperable.<br><span style="font-weight: bold;">How can it affect me?</span> If you have an ACAP using the Computer Vision SDK, it will not work correctly with AXIS OS 12.0 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">File execution on edge storage</span></span></p><p>In AXIS OS 12, to allow ACAPs to execute files or binaries from edge storage (such as an SD card or network share), the user must explicitly configure the Axis device. This can be achieved by setting up the Extra Mount Options in Plain Config, as described below.</p><p><br><img alt="" class="inline" height="622" src="/image/t10213399.png" style="vertical-align:middle;" width="1018"></p><p><br>As a result of this change, in the factory default state of AXIS OS 12, file execution from edge storage is disabled and must be explicitly configured.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> To increase the security on the device.<br><span style="font-weight: bold;">How can it affect me?</span> ACAPs requiring file execution on edge storage may not function properly if the device is not configured accordingly.<br></p></li></ul><p><span style="font-weight: bold;"> API changes:</span></p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Rate Control changes for RTSP</span></span><br>As the VAPIX Rate Control API has evolved over the years, the relationship between some of the URL options and <span style="font-style: italic;">param.cgi</span> parameters has become complicated. This will be simplified in upcoming versions of Axis OS. This was communicated earlier <a class="link" href="https://www.axis.com/developer-community/news/rate-control-api">here</a>.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> To simplify the Rate control API.<br><span style="font-weight: bold;">How can it affect me?</span> The new API is supported by the product when Properties.Image.RateControl.Version is 2.0 and higher. videobitrate and Image.I#.RateControl.TargetBitrate are deprecated from now No changes are made when it comes to Average Bitrate (ABR).</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Remove Legacy Overlays</span></span></p><p>The possibility to create overlays via the parameter CGI will be completely deprecated. This was communicated earlier <a class="link" href="https://www.axis.com/developer-community/news/legacy-overlays">here</a>. An example of the old overlay is provided below.</p><p><br><img alt="" class="inline" height="802" src="/image/t10198460.png" style="vertical-align:middle;" width="1430"></p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> Overlays have their own API, dynamicoverlay CGI, with direct access to the overlay system. There for should this old way be deprecated.<br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Added path restrictions for dynamicoverlay.cgi</span></span></p><p>The <a class="link" href="https://www.axis.com/vapix-library/subjects/t10175981/section/t10007638/display?section=t10007638-t10119641">Dynamic Overlay</a> VAPIX API that allows to configure the path to the overlay image to display has been limited to /etc/overlays/. It is not possible anymore to alter the path through VAPIX API.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> Supporting to alter the path trough API is not best practice and keeping it might be a security threat.<br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Changes in dynamicoverlay.cgi</span></span></p><p>Optional values, “source” and “sensor” will be removed from the <a class="link" href="https://www.axis.com/vapix-library/subjects/t10175981/section/t10007638/display?section=t10007638-t10119641">Dynamic Overlay</a>in AXIS OS 12.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> The options are obsolete and no longer used and should therefore be removed to follow best practice.<br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">New version of privacymask.cgi. </span></span></p><p>Unused functionality or parameters have been removed, while those utilized in the previous version have been preserved.</p><p><br>The following will be removed in privacymask.cgi:<br><span style="font-style: italic;">preview_on <br>preview_off<br>query list <br>query position<br>ptpolygon <br>imagerotation <br>imageresolution<br>zoomlowlimit </span></p><p><br>The following will be removed in param.cgi:<br><span style="font-style: italic;">parameter Image.I[source].Overlay.MaskWindows.PtPolygon</span></p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> Supporting capabilities that are not used is not best practice and keeping them might be a security threat. <br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removal of "ClassCandidate" from Analytics Scene description for ONVIF</span></span></p><p>In the analytics scene description, both "tt:ClassDescriptor/tt:ClassCandidate" and "tt:ClassDescriptor/tt:Type" are used today for backward comparability, but they say the same information. ONVIF recommends the use of "tt:ClassDescriptor/tt:Type", see <a class="link" href="https://www.onvif.org/ver10/schema/metadatastream.xsd">metadatastream.xsd</a>—</p><p><span style="font-weight: bold;">AXIS OS 11.11 and lower</span><br><img alt="" class="inline" height="470" src="/image/t10208091.png" style="vertical-align:middle;" width="644"></p><p><span style="font-weight: bold;">AXIS OS 12.0 and higher</span><br><img alt="" class="inline" height="398" src="/image/t10208090.png" style="vertical-align:middle;" width="648"></p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> Axis should be in compliant with ONVIF. <br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Updating terminology from “Vehical” to “Vehicle” for ONVIF</span></span></p><p>Due to an error in the ONVIF Metadata Spec, “Vehicle” has been incorrectly represented as “Vehical”, in the Analytics Scene description. As of AXIS OS 12, the correct term “vehicle” will be used instead.<br>See code example at <a class="link" href="https://www.axis.com/developer-community/news/metadata-stream-os-12">Changes in the analytics metadata stream in AXIS OS 12.0</a>.</p><p><span style="font-weight: bold;">Why is this change introduced?</span> Axis should be in compliant with ONVIF. <br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Updating terminology from “Bicycle” to “Bike” in VehicleType for ONVIF</span></span></p><p>Currently in the Analytics Scene description, the term “Bicycle” is used to describe both a bicycle and a motorcycle within the context of “VehicleType”. As of AXIS OS 12.0, “Bike” will be used instead of “Bicycle” to describe both bicycles and motorcycles according to the ONVIF Standard, and it will be represented as an “ObjectType”. <br>See code example at <a class="link" href="https://www.axis.com/developer-community/news/metadata-stream-os-12">Changes in the analytics metadata stream in AXIS OS 12.0</a>.</p><p><span style="font-weight: bold;">Why is this change introduced?</span> Axis should be in compliant with ONVIF. <br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removal of the lightcontrol web service API</span></span></p><p>The lightcontrol web service API (implemented in ws/wsd/impl/ali) has been deprecated for many years and is replaced by the lightcontrol-cgi JSON API. Information about this change has been sent out previously to partners.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> It is obsolete, and keeping it might be a security threat. <br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.</p><p><br></p></li></ul><p><span style="font-weight: bold;">Product specific:</span></p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Remove support for AXIS T6101/T6112</span></span></p><p>Support for AXIS T6101 and AXIS T6112 will be removed. Read more about compatible products on <a class="link" href="https://www.axis.com/products/axis-t6101-audio-and-io-interface/support#compatible-products">axis.com</a></p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> AXIS T6101 and AXIS T6112 are discontinued.<br><span style="font-weight: bold;">How can it affect me?</span> AXIS T6101 and AXIS T6112 does not work with Axis devices running AXIS OS 12.0 or higher. Please use AXIS OS LTS 2024 instead.</p><p><br></p></li></ul></div></section><section toc-id="t10201933"><div class="section__title"><h4 id="changes-in-axis-os-11" toc-id="t10201933">Changes in AXIS OS 11</h4></div> <div class="section__body"><p>Please note that some breaking was done AXIS OS 11, but with limited impact. </p><p>The changed default behavior in AXIS OS 11 will affect the product after a<span style="font-weight: bold;"> factory reset</span>, as well as new products launched with that specific version, but will not affect an upgrade, i.e. if you upgrade AXIS OS without a factory reset, your products will not change their behavior.</p><p><span style="font-weight: bold;">Security:</span></p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Remove access via FTP protocol</span></span></p><p>Since AXIS OS 11.1, we have removed the possibility to access the device via the FTP protocol, to increase overall minimum cybersecurity level. <br>For troubleshooting purposes it is recommended to use secure SSH access. Note that upload from the device to an FTP server is still possible. For more information, visit SSH access in the AXIS OS Knowledge base.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> To increase overall security.<br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this feature, it will not work correctly with AXIS OS 11.1 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removed support for proxy SOCKS version 4 and 5</span></span></p><p>Since AXIS OS 11.0, support for proxy SOCKS version 4 and 5 has been removed.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> It is obsolete, and keeping it might be a security threat. <br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this feature, it will not work correctly with AXIS OS 11.0 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">No dedicated root user in factory defaulted state</span></span></p><p>Since AXIS OS 11.5, no dedicated root user is pre-configured in factory defaulted state. To ease <span class="keep">O3C-related</span> integrations and to allow time to adapt, Axis made a modification that currently creates this root user for O3C onboarding/integration. From LTS 2024, O3C integrations shall not rely on the previously available admin user named “root”. If a separate (admin) user is deemed necessary for some purpose, this user shall be specifically created during the initial onboarding/integration.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> To lower the attack surface of the device and increase the overall device security.<br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using root as hardcoded username, it will not work correctly with AXIS OS 11.5 or higher unless you create a user root.</p><p><br></p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Root-privilege is disabled in factory defaulted state</span></span></p><p>Root-privileged access is disabled by default in Axis products and ACAP applications to increase ACAP confidentiality by better protecting their data and secrets, to prevent information leakage and to increase AXIS OS system integrity by removing system-wide root-privileged access for users and applications. In AXIS OS 11, this can still be enabled by parameter if required, see screenshots below for reference:</p><p><img alt="" class="inline" height="320" src="/image/t10207645.png" style="vertical-align:middle;" width="658"></p><p><img alt="" class="inline" height="213" src="/image/t10207661.png" style="vertical-align:middle;" width="647"></p><p>Please read the <a class="link" href="https://www.axis.com/developer-community/news/axis-os-root-acap-signing">full guide</a> for more information. The changes in AXIS OS 11 are summarized below.<br></p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> To increase the security on the device.<br><span style="font-weight: bold;">How can it affect me?</span> Affected ACAPs has been communicated about this and should create a new version if they are affected regarding this change.</p><p><br></p></li><li class="knowledge-list-item-skip knowledge-list-item-table"><table class="knowledge-table table table-bordered"><tbody><tr class="knowledge-table-row"><td class="knowledge-table-cell"><span style="font-weight: bold;">AXIS OS</span></td><td class="knowledge-table-cell"><span style="font-weight: bold;">Timeline</span></td><td class="knowledge-table-cell"><span style="font-weight: bold;">Changes</span></td></tr><tr class="knowledge-table-row"><td class="knowledge-table-cell">11.5</td><td class="knowledge-table-cell">June 2023</td><td class="knowledge-table-cell"><ul class="knowledge-list knowledge-list-bullets"><li><p>VAPIX/Web Access: The user “root” is an ordinary administrator. </p></li><li><p>ACAP Privileges: Root privileges can be disabled.</p></li></ul></td></tr><tr class="knowledge-table-row"><td class="knowledge-table-cell">11.6</td><td class="knowledge-table-cell">September 2023</td><td class="knowledge-table-cell"><ul class="knowledge-list knowledge-list-bullets"><li><p>SSH Access: Root user access can be disabled.</p></li></ul></td></tr><tr class="knowledge-table-row"><td class="knowledge-table-cell">11.8</td><td class="knowledge-table-cell"> January 2024</td><td class="knowledge-table-cell"><ul class="knowledge-list knowledge-list-bullets"><li><p>SSH Access: Root user access is disabled by default but can be enabled. </p></li><li><p>ACAP Privileges: Root privileges is disabled by default but can be enabled.</p></li></ul></td></tr><tr class="knowledge-table-row"><td class="knowledge-table-cell">11.11</td><td class="knowledge-table-cell">June 2024</td><td class="knowledge-table-cell"><ul class="knowledge-list knowledge-list-bullets"><li><p>Axis devices only accept installation of signed ACAP applications by default. Devices can be configured to accept unsigned applications</p></li></ul></td></tr><tr class="knowledge-table-row"><td class="knowledge-table-cell"> LTS 2024</td><td class="knowledge-table-cell"> H2 2024</td><td class="knowledge-table-cell"><p>Support: 2024-2029. Can be used as a stop-gap solution until an ACAP application is fully adapted.</p><ul class="knowledge-list knowledge-list-bullets"><li><p>SSH Access: Root user access is disabled by default but can be enabled.</p></li><li><p>ACAP Privileges: Root privileges is disabled by default but can be enabled.</p></li></ul></td></tr></tbody></table></li></ul><p><br></p><p><span style="font-weight: bold;">VAPIX API changes:</span></p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">PTZ VAPIX API version 2</span></span></p><p>Since AXIS OS 11.0, there is a new version of the PTZ VAPIX API. For more information, visit the <a class="link" href="https://www.axis.com/vapix-library">VAPIX library</a>.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removal of date.cgi</span></span></p><p>Since AXIS OS 11.0, the date.cgi has been removed and replaced by time.cgi. For more information, visit the <a class="link" href="https://www.axis.com/vapix-library">VAPIX library</a>l </p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> It is obsolete, and keeping it might be a security threat. <br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this API, it will not work correctly with AXIS OS 11.0 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Support removed for BMP format</span></span></p><p>Since AXIS OS 11.0, support to request an image in BMP file format has been removed. For more information, visit the <a class="link" href="https://www.axis.com/vapix-library">VAPIX library</a>.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> It is obsolete, and keeping it might be a security threat. <br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this feature, it will not work correctly with AXIS OS 11.0 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removed support of recording mediaclip through Mediaclip AP</span></span>I</p><p>Since AXIS OS 11.0, support to record a mediaclip using the Mediaclip API has been removed. For more information, visit the <a class="link" href="https://www.axis.com/vapix-library">VAPIX library</a>.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> It is obsolete, and keeping it might be a security threat. <br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this feature, it will not work correctly with AXIS OS 11.0 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Parameters in the root.PTZ parameter group changes</span></span></p><p>Since AXIS OS 11.0, changed access for a number of parameters in the root.PTZ parameter group. For more information, visit the <a class="link" href="https://www.axis.com/vapix-library">VAPIX library</a>.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> Due to architectural changes. <br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this, it will not work correctly with AXIS OS 11.0 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removal of edit.cgi</span></span></p><p>Since AXIS OS 11.1, the edit.cgi has been removed. For more information, visit the <a class="link" href="https://www.axis.com/vapix-library">VAPIX library</a>.</p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> It is obsolete, and keeping it might be a security threat. <br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this API, it will not work correctly with AXIS OS 11.1 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removal of libvidcap</span></span></p><p>The libvidcap has been removed. Use Video capture API instead. For more information, visit the <a class="link" href="https://help.axis.com/acap-3-developer-guide#video-capture-api">ACAP developer guide</a></p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> It is obsolete, and keeping it might be a security threat. <br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this API, it will not work correctly with AXIS OS 11.1 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removal of overlay-cgi.</span></span></p><p>The overlay-cgi has been removed in AXIS OS 11.10. It is recommended to use overlayimage-cgi instead, see more info in the <a class="link" href="https://www.axis.com/vapix-library/">VAPIX Library</a>.</p><p><br></p><p>VAPIX API parameter affected:<br><span style="font-style: italic;">call_overlay_upload.cgi<br>call_overlay_del.cgi<br>call_overlay_set.cgi<br>create_overlay.cgi<br>overlay_list.cgi<br>overlay_image_formats.cgi</span><br></p><p><br><span style="font-weight: bold;">Why is this change introduced?</span> It is obsolete and replaced by a different API.<br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.</p></li></ul><p><br></p><p><span style="font-weight: bold;">Other changes: </span></p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removal of the built in motion detection</span></span></p><p>In AXIS OS 11.2 the old built in motion detection, also known as VMD1, was removed.</p><p><span style="font-weight: bold;">Why is this change introduced?</span> It is obsolete, and keeping it might be a security threat. <br><span style="font-weight: bold;">How can it affect me?</span> If you have third party software using this application, it will not work correctly with AXIS OS 11.2 or higher.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removed installable decoder AAC</span></span></p><p>Since AXIS OS 11.0, the installable audio decoder for AAC has been removed and is no longer downloadable from the cameras web interface.</p></li><li><p><span style="font-weight: bold;"><span style="text-decoration: underline;">Removed installable decoder H.264</span></span></p><p>Since AXIS OS 11.0, the installable decoder for H.264 has been removed and is no longer downloadable from the cameras web interface.</p></li></ul></div></section><section toc-id="t10161722"><div class="section__title"><h2 id="next-axis-os-version" toc-id="t10161722" class="title-attention">Next AXIS OS version</h2></div> <div class="section__body"><p>Please note that this schedule is preliminary and that both time schedule and included features are subject to change as work progresses.</p><p>For the Developer News articles, visit the <a class="link" href="https://www.axis.com/developer-community/news">Developer Community</a>.</p><p><span style="font-weight: bold;">AXIS OS 12.4</span></p><p>Scheduled for: April 2025</p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;">Features for all products</span></p><li class="knowledge-list-item-skip knowledge-list-item-sublist"><ul class="knowledge-list knowledge-list-bullets"><li><p>Added support to set custom headers for HTTP-based video streaming cgi.</p></li></ul></li></li><li><p><span style="font-weight: bold;">Cybersecurity updates</span></p><li class="knowledge-list-item-skip knowledge-list-item-sublist"><ul class="knowledge-list knowledge-list-bullets"><li><p>Added support for Crypto-Policy setting to chose between standard OpenSSL cipher suite or FIPS 140-2 cipher suites. The Crypto-Policy setting can be adjusted from the Security tab in the web-interface or through VAPIX API.</p></li><li><p>Added support for OAuth 2.0 RFC6749 Client Credential Flow for token-based machine-to-machine communication that provides better overall security as traditional digest/basic authentication schemes.</p></li></ul></li></li><li><p><span style="font-weight: bold;">Product specific features and changes</span></p><li class="knowledge-list-item-skip knowledge-list-item-sublist"><ul class="knowledge-list knowledge-list-bullets"><li><p>Zipstream storage profiles for AV1 format now support B-frames, allowing for more efficient video compression. <br><span style="text-decoration: underline;">Applies to</span>: All products based on <a class="link" href="https://help.axis.com/axis-os-release-notes#artpec-9">AXIS ARTPEC-9</a></p></li><li><p>Hardware modifications have been made to proactively prepare for the new NDAA 23 regulations that will be required in 2028. You will find more information about NDDA Compliance on <a class="link" href="https://www.axis.com/en-us/solutions/government/compliance#ndaa-compliance">axis.com</a>. In AXIS OS knowledge base, you will find more about the <a class="link" href="https://help.axis.com/axis-os-knowledge-base#hardware-changes">hardware changes</a>. The hardware ID can be found in Plain config > Properties > System > Hardware ID.</p><li class="knowledge-list-item-skip knowledge-list-item-sublist"><ul class="knowledge-list knowledge-list-bullets"><li><p>Products with Hardware ID A1D and A1E only support active track 12.4.XX and later, as well as coming LTS 2024 11.11 version and LTS 2022 10.12 version, and later. <br><span style="text-decoration: underline;">Applies to</span>: <span class="keep">AXIS M7116</span> and <span class="keep">AXIS P7316</span></p></li></ul></li></li></ul></li></li></ul></div></section><section toc-id="t10171198"><div class="section__title"><h2 id="current-axis-os-version" toc-id="t10171198" class="title-attention">Current AXIS OS version</h2></div> <div class="section__body"><p><span style="font-weight: bold;">AXIS OS 12.3</span></p><p>Release date: February-March 2025</p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;">Features for all products</span></p><li class="knowledge-list-item-skip knowledge-list-item-sublist"><ul class="knowledge-list knowledge-list-bullets"><li><p>Added Time API to Device Configuration API, as beta.</p></li><li><p>Updated the Certificate, Firewall, SNMP, and LLDP APIs in the Device Configuration API to remove the beta designation, indicating they are now stable and ready for production use.</p></li><li><p>IPv6 support is now enabled by default, which includes IPv6 Link-Local Address, DHCPv6, and Router Advertisement capabilities.</p></li></ul></li></li><li><p><span style="font-weight: bold;">Cybersecurity updates</span></p><li class="knowledge-list-item-skip knowledge-list-item-sublist"><ul class="knowledge-list knowledge-list-bullets"><li><p>Updated cURL to version 8.11.0, addressing <a class="link" href="https://www.cve.org/CVERecord?id=CVE-2024-9681">CVE-2024-9681</a>.</p></li><li><p>Updated cURL to version 8.11.1 to increase overall cybersecurity level.</p></li></ul></li></li><li><p><span style="font-weight: bold;">Analytics updates</span></p><li class="knowledge-list-item-skip knowledge-list-item-sublist"><ul class="knowledge-list knowledge-list-bullets"><li><p>AXIS Object Analytics: <br>Added the ability to copy the scenario ID in the web interface.</p></li><li><p>AXIS Scene Metadata: <br>Reduced the frequency of sending empty frames from Analytics Scene Description. If no objects are detected in the scene, an empty frame is now sent every other second (instead of approximately 10 times per second). This change affects both the ONVIF producer 'Analytics Scene Description' and the message broker topic 'com.axis.analytics_scene_description.v0.beta'.<br>Applies to: All products with AXIS Scene Metadata support.</p></li></ul></li></li><li><p><span style="font-weight: bold;">Product specific features and changes</span></p><li class="knowledge-list-item-skip knowledge-list-item-sublist"><ul class="knowledge-list knowledge-list-bullets"><li><p>Hardware modifications have been made to proactively prepare for the new NDAA 23 regulations that will be required in 2028. You will find more information about NDDA Compliance on <a class="link" href="https://www.axis.com/en-us/solutions/government/compliance#ndaa-compliance">axis.com</a>. In AXIS OS knowledge base, you will find more about the <a class="link" href="https://help.axis.com/axis-os-knowledge-base#hardware-changes">hardware changes</a>. The hardware ID can be found in Plain config > Properties > System > Hardware ID.</p><li class="knowledge-list-item-skip knowledge-list-item-sublist"><ul class="knowledge-list knowledge-list-bullets"><li><p>Products with Hardware ID A16, A17 and A18 only support active track 12.3.XX and later, as well as coming LTS 2024 11.11 version and LTS 2022 10.12 version, and later. <br><span style="text-decoration: underline;">Applies to</span>: <span class="keep">AXIS M5074</span>, <span class="keep">AXIS M5075</span> and <span class="keep">AXIS M5075-G</span></p></li></ul></li></li><li><p>AXIS Image Health Analytics is added as pre-installed application. <br><span style="text-decoration: underline;">Applies to</span>: AXIS Q1686-DLE</p></li><li><p>Add unknown object filter which hides all tracks that are not classified as "human" or "vehicle"<br><span style="text-decoration: underline;">Applies to</span>: AXIS D2110-VE, AXIS D2210-VE, AXIS Q1656-DLE and AXIS Q1686-DLE</p></li></ul></li></li></ul></div></section><section toc-id="t10194525"><div class="section__title"><h2 id="open-source-library-support" toc-id="t10194525" class="title-attention">Open source library support</h2></div> <div class="section__body"><p>AXIS OS-based network products use a variety of open source libraries. Therefore, it is critical that changes to these libraries are reflected in AXIS OS. Libraries are updated in the AXIS OS Active and LTS tracks in conjunction with the release. If there are no software restrictions, they are also updated in the PSS track.</p><p>If an open source library becomes end-of-life (EOL) by the upstream community, Axis aims to replace the library in a timely manner or provide support in a different way depending on its use within the AXIS OS-based network product. An example is listed below.</p><p><span style="font-weight: bold;">OpenSSL</span> is used for cryptographic operations. The currently used OpenSSL 1.1.1 version is a long-term support (LTS) release which has reached its <a class="link" href="https://www.openssl.org/blog/blog/2023/03/28/1.1.1-EOL/">EOL during September 2023</a> as announced by the OpenSSL foundation.</p><ul class="knowledge-list knowledge-list-bullets"><li><p>From AXIS OS 11.6.89 and onwards, the newest OpenSSL 3.0 library (LTS) is supported in addition to the current OpenSSL 1.1.1, which will be deprecated but still usable.</p></li><li><p>Axis plans to remove OpenSSL 1.1.1 support in AXIS OS 12 after LTS 2024.</p></li><li><p>To support AXIS OS LTS tracks, Axis has a support contract agreement with the OpenSSL foundation for continued patching of OpenSSL 1.1.1.</p></li></ul><p><span style="text-decoration: underline;"><span style="font-weight: bold;">ACAP related information</span></span></p><p>Starting from ACAP SDK version 4.14, we're integrating the latest openSSL Version 3 into the Native ACAP SDK. <br>Please read more in the <a class="link" href="https://axiscommunications.github.io/acap-documentation/docs/release-notes/4.14.html">release notes</a> and explore API examples on <a class="link" href="https://github.com/AxisCommunications/acap-native-sdk-examples/tree/main/curl-openssl">GitHub</a> for details.</p><p><span style="font-weight: bold;">What needs to be done:</span></p><p>If any Axis-owned ACAP relies on the OpenSSL 1.1.1 runtime dependency provided by the platform, it requires refactoring and rebuilding with OpenSSL 3 libraries. We recommend utilizing the latest ACAP SDK (4.14) to ensure compatibility with the correct library version.</p></div></section><section toc-id="t10186723"><div class="section__title"><h2 id="software-bill-of-materials" toc-id="t10186723" class="title-attention">Software Bill of Materials</h2></div> <div class="section__body"><p>A Software Bill of Materials (SBOM) is an inventory of all components included in the software. It has become an increasingly important and common part of software development lifecycle and processes. It allows IT Operations and Security staff to determine which third-party or open-source software is packaged with your software. Having an SBOM is important when it comes to securing your IT systems and protecting user data. </p><p><span style="font-weight: bold;">Why do Axis publish an SBOM?</span></p><p>Axis works actively with the principles of openness and building trust through transparency, the SBOM is a valued addition to these principles. It provides our customers with the information necessary to know whether or not the products we have provided may be vulnerable to cyber attacks.</p><p><span style="font-weight: bold;">For which AXIS OS versions?</span></p><p>Axis will provide an SBOM for all AXIS OS releases on active track starting with release 11.2.</p><p><span style="font-weight: bold;">What is included?</span></p><p>The Axis SBOM contains information about Axis-Proprietary components and Opensource software used to assemble AXIS OS.</p><p><span style="font-weight: bold;">What is excluded and why?</span></p><p>Initially, due to current licensing and technical limitations we cannot provide information about third-party proprietary software and Axis-proprietary components with dependencies. In addition to this some of the packages in the software consist of pre-compiled bundles such as our web interface and ACAPS, which have not in their turn provided an SBOM. Over time our aim is to cover all the third-party components and as much of the Axis-proprietary components as legally possible.</p><p><span style="font-weight: bold;">Where can I find the SBOM?</span></p><p>The SBOM is located together with the AXIS OS version it is based on. AXIS OS can be found in the product support or at the <a class="link" href="https://www.axis.com/support/firmware">download page</a>.</p><p><span style="font-weight: bold;">What format and why?</span></p><p>The Axis SBOM is produced in accordance with the CycloneDX SBOM specification. This format seems to be the most usable in other systems and strives to be a minimalist format easy to work with. Advantages of this format can be found <a class="link" href="https://cyclonedx.org/about/guiding-principles">here</a>.</p><p><span style="font-weight: bold;">What is the difference between a SBOM and the Third party software licenses document?</span></p><p>The Third party software licenses document is meant to list all legal agreements and licenses with third parties related to any intellectual property that allows us to use, market and incorporate this into our products.</p><p><span style="font-weight: bold;">What about SBOM for other AXIS software?</span></p><p>This is a start, and we are looking into how SBOM is applicable to other software from Axis.</p><p><span style="font-weight: bold;">Where can I find more information about SBOM in general?</span> </p><p>The <a class="link" href="https://www.ntia.gov">National Telecommunications and Information Administration</a> provides more educational information about SBOM.</p><ul class="knowledge-list knowledge-list-bullets"><li><p><a class="link" href="https://www.ntia.gov/files/ntia/publications/framingsbom_20191112.pdf">Framing Software Component Transparency: Establishing a Common Software Bill of Material (SBOM)</a></p></li><li><p><a class="link" href="https://www.ntia.gov/files/ntia/publications/sbom_faq_-_20201116.pdf">Software Bill of Material FAQ</a></p></li></ul><p><span style="font-weight: bold;">How can I use the SBOM to analyze the software?</span></p><p>The Axis SBOM contains information about Axis-Proprietary and Opensource software used to assemble AXIS OS. The Axis SBOM can be used by third party vulnerability scanners to highlight known vulnerabilities in software packages. A vulnerability that applies to a certain module or feature in a software package needs to be loaded and used by the Axis device. Vulnerabilities in modules that are not loaded are not relevant but may still be flagged by the vulnerability scanner or SBOM information. For more information on how to work with the result of a security scanner see: <a class="link" href="https://help.axis.com/axis-os-vulnerability-scanner-guide">AXIS OS Vulnerability Scanner Guide</a>.</p></div></section><section toc-id="t10139395"><div class="section__title"><h2 id="axis-os-lifecycle" toc-id="t10139395" class="title-attention">AXIS OS lifecycle management</h2></div> <div class="section__body"><p>AXIS OS supplies three types of tracks: <span style="font-weight: bold;">active</span>, <span style="font-weight: bold;">long-term support (LTS)</span> and <span style="font-weight: bold;">product-specific support (PSS)</span> track. </p><p>In the active track, we consistently add new features while also improving cybersecurity. In LTS, we refrain from introducing new features, prioritizing to maintain cybersecurity and ensuring compatibility. PSS will receive updates less frequently compared to our other two tracks, but we remain committed to addressing bug corrections and upholding cybersecurity measures.</p><img alt="" height="468" src="/image/t10216382.png" width="676"><p></p><p>There's a <a class="link" href="https://youtu.be/sAyciMeHOMU?si=x6nUpwwFy7FjqNiH">YouTube video</a> that explains the AXIS OS lifecycle in more detail. It covers our different tracks, version management and upgrade recommendations.</p></div></section><section toc-id="t10139394"><div class="section__title"><h3 id="active-track" toc-id="t10139394">Active track</h3></div> <div class="section__body"><p>The most updated and feature progressive track of AXIS OS, that is suitable for customers who want access to the newest features and improvements. New products are launched on this track, which means the most immediate access to any new features and updates.</p><img alt="" height="467" src="/image/t10184574.png" width="1208"></div></section><section toc-id="t10139393"><div class="section__title"><h3 id="lts-track" toc-id="t10139393">Long-term support track</h3></div> <div class="section__body"><p>The focus of the long-term support (LTS) track is to keep the products well integrated with third-party equipment or software, and still get necessary bug fixes and cybersecurity updates. An LTS track has a fixed feature set and a new track is created every two years and maintained for 5 years. No new products or features are added to the LTS track.</p></div></section><section toc-id="t10203002"><div class="section__title"><h3 id="pss" toc-id="t10203002">Product-specific support</h3></div> <div class="section__body"><p>Product-specific support (PSS), is a rare track used when a product needs support after an LTS track has expired. The products on this track will still receive necessary bug fixes and cybersecurity updates. Each product is on its own track, the tracks are not connected with one another. Also, other non-Axis OS products have similar support tracks. </p><img alt="" height="1864" src="/image/t10205720.png" width="4023"></div></section><section toc-id="t10220344"><div class="section__title"><h3 id="suggested-track" toc-id="t10220344">Suggested track</h3></div> <div class="section__body"><p></p><p>Below is a list of system characteristics and goals to help you choose the right track.</p><dl class="dl-horizontal"><dt>Highest level of cybersecurity</dt><dd><span style="font-weight: bold;">AXIS OS active<br></span>AXIS OS active track provides security patches and the latest enhancements including security.</dd><dt>Need for specific new features</dt><dd><span style="font-weight: bold;">AXIS OS active</span><br>AXIS OS active track offers the latest features. In some areas, such as analytics, the gap between Active, LTS and newer products may be greater.</dd><dt>Satisfied with current features and cybersecurity level</dt><dd><span style="font-weight: bold;">AXIS OS LTS</span><br>LTS tracks has focus on compatibility and adding new cyber security patches. AXIS OS LTS track do not introduce new features or breaking changes.</dd><dt>Extensive internal verification process when accepting new software updates</dt><dd><span style="font-weight: bold;">AXIS OS LTS<br></span>Updates within the same AXIS OS LTS track shouldn’t require recertification. If validating new releases is costly or time-consuming, the AXIS OS LTS track is recommended.</dd><dt>Existing processes involve frequent updates of VMS and system components.</dt><dd><span style="font-weight: bold;">AXIS OS active or AXIS OS LTS<br></span>Both AXIS OS Active and LTS track may be used. Each new Axis release is validated with Milestone, Genetec and AXIS Camera Station. <br>Make sure your VMS is validated before upgrading.</dd><dt>Current processes lack frequent updates for VMS and system components</dt><dd><span style="font-weight: bold;">AXIS OS LTS<br></span>Verify with your VMS and ACAP provider which versions they test and recommend. AXIS OS LTS is the recommended choice for optimal compatibility.</dd></dl><p></p></div></section><section toc-id="t10218226"><div class="section__title"><h3 id="upgrade-path" toc-id="t10218226">Upgrade path</h3></div> <div class="section__body"><p><br>You can upgrade your devices using the web interface or various device management tools, such as AXIS Device Manager, AXIS Camera Station Pro, and AXIS Camera Station Edge. AXIS Device Management Extend simplifies the upgrade process by providing built-in backend upgrade paths. Read more about <a class="link" href="https://help.axis.com/axis-os-knowledge-base#how-to-upgrade">How to upgrade</a> in AXIS OS Knowledge base.</p><p>Here are some recommendations for how to upgrading:</p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;">Upgrading from an older active track to the latest active</span>: Upgrade to the latest version of the intermediate LTS.</p></li></ul><p><img alt="" class="inline" height="392" src="/image/t10218216.png" style="vertical-align:middle;" width="639"></p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;">Upgrading from the latest LTS track to the active track</span>: Start by upgrading to the latest version of your current LTS.</p></li></ul><p><img alt="" class="inline" height="292" src="/image/t10218214.png" style="vertical-align:middle;" width="521"></p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;">Upgrading from an older LTS to the next LTS version</span>: First, update to the latest version of your current LTS</p></li></ul><p><img alt="" class="inline" height="293" src="/image/t10218213.png" style="vertical-align:middle;" width="753"></p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;">Upgrading from an older LTS to two newer LTS versions</span>: Upgrade to the intermediate LTS version first.</p></li></ul><p><img alt="" class="inline" height="430" src="/image/t10218215.png" style="vertical-align:middle;" width="945"></p><p></p><p><span style="font-weight: bold;">Considerations</span></p><p>A new active track always means that something has changed. To move AXIS OS forward we deliberately introduce breaking changes to keep our software up-to-date due to cybersecurity and feature growth. When you upgrade to a newer track please keep in mind we may have introduced new features, changed the default settings, and performance enhancements can affect compatibility with your existing system. </p><p>Over time, multiple LTS tracks become available for a product. Each LTS track is designed to provide long-term consistency by focusing on bug fixes without introducing new features. However, it's a good idea to upgrade to the latest LTS track. </p><p>Therefore, product upgrades should be performed in a controlled and monitored manner to ensure that the version is performing as expected in your environment before proceeding. It is always recommended to have a group of devices that represent your inventory in a test environment and validate the upgrade before the actual installation. Grouping and and testing please read more here.</p><p><span style="font-weight: bold;">Stay current with AXIS OS upgrades</span></p><p>Maintaining a consistent upgrade strategy is essential for ensuring your Axis products benefit from ongoing enhancements. Axis Technical Services also advises upgrading to the latest version when addressing issues with an Axis product.</p><p><span style="font-weight: bold;">Selecting the right latest version</span></p><p>With multiple upgrade options available, it’s important to choose the appropriate "latest" version. Here’s some guidance: </p><ul class="knowledge-list knowledge-list-bullets"><li><p>For Long-term support (LTS), we recommend to chose the newest LTS track if available for you product. </p></li><li><p>On any track (Active or LTS), we recommend upgrading to the latest available version.</p></li><li class="knowledge-list-item-skip knowledge-list-item-paragraph">By following this approach, you’ll keep your Axis products up-to-date with optimal performance and cybersecurity.</li><li class="knowledge-list-item-skip knowledge-list-item-paragraph"></ul><p><span style="font-weight: bold;"></span></p><p><span style="font-weight: bold;">Additional Q&A</span></p><ul class="knowledge-list knowledge-list-bullets"><li><p><span style="font-weight: bold;">If my Axis product is running on the LTS 2022 (10.12) track, should I consider upgrading to the latest AXIS OS active track?</span><br>It depends on third-party dependencies and compatibility with the active track. Generally, we recommend remaining on the LTS 2022 (10.12) track and updating within that track as long as it's supported. If you need features only on the active track, upgrading might be worth considering.</p></li><li><p><span style="font-weight: bold;">I would like to run my Axis product on an LTS track, but there is currently no LTS track available?</span><br>If your product was released between two LTS tracks, it’s recommended to keep it updated on the active track until a new LTS track is available. New LTS tracks are introduced every two years.</p></li><li><p><span style="font-weight: bold;">If there are multiple LTS tracks available, which LTS track should I choose?</span><br>We recommend using the latest LTS track supported by your third-party software. This ensures compatibility, reduces the need to switch tracks, and provides access to the latest cybersecurity updates and features.</p></li><li><p><span style="font-weight: bold;">What should I do if my VMS states that it requires a specific version of the LTS track, such as version 9.80.3.2 on LTS 2020, but I cannot find it on axis.com?</span><br>If your VMS specifies a specific LTS version, it will also be compatible with subsequent releases within that track. VMS systems typically list one version because it was certified with it, but compatibility remains consistent within each LTS track. It’s generally safe to use other versions.</p></li><li><p><span style="font-weight: bold;">When upgrading from an old LTS to a new LTS, is it necessary to upgrade to the intermediate versions?</span><br>To preserve settings, we recommend upgrading in incremental steps. If resetting the device to factory defaults, however, intermediate versions are not necessary.</p></li></ul><p></p></div></section><section toc-id="t10220343"><div class="section__title"><h3 id="general-recommendations" toc-id="t10220343">General recommendations</h3></div> <div class="section__body"><p>Follow the below recommendations to optimize AXIS OS performance, ensure cybersecurity, and simplify updates and lifecycle management.</p><p><span style="font-weight: bold;">Always use the latest supported AXIS OS version:</span></p><ul class="knowledge-list knowledge-list-bullets"><li><p>Always run the latest version within your selected AXIS OS track.</p></li><li><p>Ensure that all models in your system are running the same AXIS OS version, if possible. </p></li><li><p>If you have products with different HWIDs for the same model, make sure you are still running the same version, see <a class="link" href="https://help.axis.com/axis-os-knowledge-base#hardware-changes">Hardware Changes</a> in the AXIS OS Knowledge Base.</p></li><li><p>If AXIS OS LTS track is preferred, choose the latest available LTS version for each product.</p></li><li><p>The LTS track provides robust cybersecurity measures and allows time to plan for upgrading to a newer LTS track when needed.</p></li></ul><p><span style="font-weight: bold;">Simplify software updates and lifecycle planning using device management tools:</span></p><ul class="knowledge-list knowledge-list-bullets"><li><p>E.g. <a class="link" href="https://www.axis.com/support/tools/axis-device-manager">AXIS Device Manager</a> and <a class="link" href="https://www.axis.com/products/axis-device-manager-extend">AXIS Device Manager Extend</a>.</p></li><li><p>Plan for device replacement before software reaches end-of-support.</p></li></ul><p><span style="font-weight: bold;">Stay up-to-date on cybersecurity recommendations:</span></p><ul class="knowledge-list knowledge-list-bullets"><li><p>Subscribe to <a class="link" href="https://www.axis.com/support/cybersecurity/security-notification-service">cybersecurity notifications</a> for the latest updates. </p></li><li><p>Apply recommendations from <a class="link" href="https://help.axis.com/axis-os-hardening-guide">AXIS OS hardening guide</a> to secure your devices. </p></li><li><p>Use network security scanners (e.g., Tenable, Rapid7) to identify potential vulnerabilities.</p></li></ul><p><span style="font-weight: bold;">Upgrading between AXIS OS LTS tracks:</span></p><ul class="knowledge-list knowledge-list-bullets"><li><p>If you are changing AXIS OS tracks (LTS or active), please read the <a class="anchor link" data-anchor="upgrade-path" href="#upgrade-path">Upgrade path</a>.</p></li><li><p>Read the<a class="link" href="https://help.axis.com/axis-os-release-notes"> release notes</a>, changes has been done between the different tracks. </p></li></ul><p><span style="font-weight: bold;">Verification of new releases:</span></p><ul class="knowledge-list knowledge-list-bullets"><li><p>When updating within the same AXIS OS LTS track additional certification or compatibility testing is usually not required.</p></li><li><p>For large systems using AXIS OS active track, it's recommended to pre-test new releases in a staging environment before deploying them to production. This ensures a smooth transition and minimizes potential disruptions.</p></li><li><p>To stay ahead of the curve, take advantage of <a class="link" href="https://www.axis.com/developer-community/axis-os-beta-releases">AXIS OS active track beta releases</a> to test upcoming features and enhancements in your staging environment prior to the official release.</p></li><li><p>Axis verifies all new AXIS OS releases against the latest versions of AXIS Camera Station, Genetec and Milestone. If you are using older VMS versions or VMS solutions from other vendors, we recommend pre-validating new AXIS OS active track releases to ensure compatibility. </p></li><li><p>Ensure that all components in the system supports the new version before changing LTS tracks or major versions on AXIS OS Active track.</p></li></ul><p></p></div></section><section toc-id="t10185211"><div class="section__title"><h3 id="downloading-axis-os" toc-id="t10185211">Downloading AXIS OS</h3></div> <div class="section__body"><p>Which AXIS OS tracks are available for an Axis edge device can be obtained when downloading AXIS OS from the <span class="keep"><a class="link" href="https://www.axis.com/support/firmware">download page</a>.</span><br></p><p>AXIS OS can also be found on the product support page for each product, where you can find all available supported versions and some older. Older unsupported versions will periodically be removed due to known bugs and cybersecurity vulnerabilities that are corrected in later releases. It is recommend to only AXIS OS versions that are supported.</p><img alt="" height="529" src="/image/t10210543.png" width="1200"><p><br></p><p>Please see below a list of common tags that indicate different AXIS OS tracks as seen in the picture above.</p><table class="knowledge-table table table-bordered"><tbody><tr class="knowledge-table-row"><td class="knowledge-table-cell"><span style="font-weight: bold;">Tag example</span></td><td class="knowledge-table-cell"><span style="font-weight: bold;">Explanation</span></td></tr><tr class="knowledge-table-row"><td class="knowledge-table-cell"><span class="keep">12.1.64 - AXIS OS active</span></td><td class="knowledge-table-cell"><p>AXIS OS active track providing new features, security and other improvements.</p></td></tr><tr class="knowledge-table-row"><td class="knowledge-table-cell"><span class="keep">11.11.124 - AXIS OS LTS 2024</span><br><span class="keep">10.12.262 - AXIS OS LTS 2022</span><br><span class="keep">9.80.66 - AXIS OS LTS 2020</span></td><td class="knowledge-table-cell"><p>AXIS OS long-term support track (LTS) providing security and maintain compatibility.</p></td></tr><tr class="knowledge-table-row"><td class="knowledge-table-cell"><span class="keep">8.40.59 - PSS</span><br><span class="keep">6.50.5.19 - PSS</span><br><span class="keep">5.51.4.7 </span></td><td class="knowledge-table-cell"><p>With and without PSS tag. Product-specific support (PSS) track.</p></td></tr></tbody></table></div></section><section toc-id="t10185297"><div class="section__title"><h3 id="axis-os-versioning" toc-id="t10185297">AXIS OS versioning</h3></div> <div class="section__body"><p>AXIS OS releases are denoted by a unique number combination. Older releases where named by the year and type of the release but since release 10.10 we changed the versioning. The differences and the significance of each number is explained in the figures below. </p><p>In some cases, you may also notice an additional number at the end. This version builds on the main AXIS OS release with additional features, such as AXIS Access Control products.</p><img alt="" height="336" src="/image/t10200176.png" width="471"><p></p><ul class="knowledge-list knowledge-list-bullets"><li><p>The major version is incremented after a new active track has been created. This happens every two years when the active track becomes an LTS track.</p></li><li><p>The minor version is indicating what feature set is included and updated with each feature release approximately 6 times per year.</p></li><li><p>The patch number is increased more often, it’s used for adding patches and bugfixes, and only final versions will be available to customers. This means that this number is only a number to mirror the external version with the internal version. </p></li></ul><p></p><p>Previous versioning .</p><img alt="" height="311" src="/image/t10184576.png" width="406"><p></p></div></section><section toc-id="t10186857"><div class="section__title"><h3 id="axis-os-maintenance" toc-id="t10186857">AXIS OS Support</h3></div> <div class="section__body"><p></p><p><span style="font-weight: bold;">When a product has an AXIS OS support date, what does that mean?</span></p><p>The product will be supported during this period with bug fixes as well as critical security updates, and with focus on compatibility and consistency.</p><p><span style="font-weight: bold;">What is required to get the full support period?</span></p><p>To benefit from the full support period of AXIS OS, the device must be upgraded to the latest active, LTS or PSS version. For more information on upgrade strategies, see <a class="anchor link" data-anchor="upgrade-path" href="#upgrade-path">Upgrade path</a>.</p><p><span style="font-weight: bold;">How long can I expect to get AXIS OS support for my product?</span></p><p>Axis generally provides 5 years of Axis OS support from the product's discontinuation date. This policy was introduced in 2016, ensuring that our customers receive extended support for their devices. To view the exact support date for your product, please visit the product's support page.</p><p><span style="font-weight: bold;">Why do some products display only the date for Hardware support and not AXIS OS support, or vice versa?</span></p><p>The dates displayed depend on investigated information and the product's lifecycle stage. For older products, no dates may be shown, while in other cases, two different dates might be displayed. If the product has a defined end-of-support date for hardware and AXIS OS, both dates will be shown.</p><p><span style="font-weight: bold;">What accounts for the diverse end-of-software support dates across different products?</span></p><p>Each product's end of software support date is determined based on its unique hardware characteristics, including system-on-chip (SoC) type, memory capacity, and market segment. </p><p><span style="font-weight: bold;">Why do some products lack an AXIS OS support date?</span></p><p>Some products are not included in the development of AXIS OS, and therefore some old products have no software support dates. However, dates will be available for more products in the Axis portfolio over time. For further questions, please contact <a class="link" href="https://www.axis.com/support/helpdesk">Axis Technical Support Helpdesk</a>.</p><p><span style="font-weight: bold;">What happens once the AXIS OS support has expired for a product?</span></p><p>No further updates, improvements or security patches will be released. There are limits to how long we can maintain software currency and implement changes to an older version. Modifying software that is limited by hardware resources becomes increasingly challenging and complicated over time. Eventually, we reach a stage where it is no longer possible to guarantee the cybersecurity of the product. This signals that it is time to replace the device.</p><p><span style="font-weight: bold;">Where can I find further information on the current forecast for AXIS OS, upcoming changes and which tracks are currently supported? </span></p><p>Please follow and monitor the <a class="anchor link" data-anchor="release-schedule" href="#release-schedule">Release schedule</a>.</p><p></p><p><span style="font-weight: bold;">Example of AXIS OS Support: </span><br>Throughout its product lifecycle, the AXIS Q1656-LE will continue to receive new features, increased cybersecurity, improvements and security updates until 2028. Between 2028 and the end of 2033, it will receive some improvements along with all security updates through LTS 2028, with a focus on compatibility.</p><img alt="" height="839" src="/image/t10187162.png" width="1891"></div></section></div></div> <div class="container scroll-to-top"><div class="row"><div class="text-right col col-12"><button type="button" class="v-btn v-btn--is-elevated v-btn--fab v-btn--has-bg v-btn--round theme--dark v-size--default" style="background-color:var(--color-yellow-04);border-color:var(--color-yellow-04);display:none;"><span class="v-btn__content"><span aria-hidden="true" class="v-icon notranslate theme--dark"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" role="img" aria-hidden="true" class="v-icon__svg"><path d="M15,20H9V12H4.16L12,4.16L19.84,12H15V20Z"></path></svg></span></span></button></div></div></div></div></div></div></div></main> <footer id="footer" class="v-footer v-sheet theme--light v-footer--padless"><div class="container container--fluid"><div class="row"><div class="pl-0 pr-0 col"><div class="axis-tracks-thin"><div class="axis-tracks__parallelogram"></div></div></div></div> <div class="row justify-center"><div class="col col-auto"><a>Cookie settings</a></div> <div class="col col-auto">-</div> <div class="col col-auto"><a href="https://www.axis.com/privacy/privacy-policy">Privacy policy</a></div> <div class="col col-auto">-</div> <div class="col col-auto"><a href="https://www.axis.com/legal">Legal</a></div> <div class="col col-auto">-</div> <div class="col col-auto"><a href="https://www.axis.com/support">Support pages</a></div></div> <div class="row ma-0"><div class="copyright-link text-center py-6 col"> ©2025 Axis Communications AB. All rights reserved. </div></div></div></footer> <div class="v-snack v-snack--bottom v-snack--has-background v-snack--right"><div class="v-snack__wrapper v-sheet theme--dark" style="display:none;"><div role="status" aria-live="polite" class="v-snack__content"> Link copied to clipboard </div><div class="v-snack__action "><button type="button" class="v-btn v-btn--text theme--dark v-size--default v-snack__btn"><span class="v-btn__content"> Close </span></button></div></div></div> <div class="v-snack v-snack--bottom v-snack--has-background v-snack--right"><div class="v-snack__wrapper v-sheet theme--dark" style="display:none;"><div role="status" aria-live="polite" class="v-snack__content"> Could not find null help </div><div class="v-snack__action "><button type="button" class="v-btn v-btn--text theme--dark v-size--default v-snack__btn"><span class="v-btn__content"> Close </span></button></div></div></div> <div class="v-snack v-snack--bottom v-snack--has-background v-snack--right"><div class="v-snack__wrapper v-sheet theme--dark" style="display:none;"><div role="status" aria-live="polite" class="v-snack__content"> Could not find element on page </div><div class="v-snack__action "><button type="button" class="v-btn v-btn--text theme--dark v-size--default v-snack__btn"><span class="v-btn__content"> Close </span></button></div></div></div></div></div></div></div><script>window.__NUXT__=(function(a,b,c,d,e,f,g,h,i,j,k,l){d.id=e;d.language=f;d.languages=[f];d.piaId=0;d.title=g;d.urlAlias="axis-os";d.date="2025-03-21T07:22:03.000000Z";d.sections=[{id:"t10207450",body:"\u003Cp\u003E\u003Cspan class=\"keep\"\u003E\u003Ca class=\"link\" href=\"https:\u002F\u002Fhelp.axis.com\u002Faxis-os-release-notes\"\u003EAXIS OS Release Notes\u003C\u002Fa\u003E\u003C\u002Fspan\u003E | \u003Cspan class=\"keep\"\u003E\u003Ca class=\"link\" href=\"https:\u002F\u002Fhelp.axis.com\u002Faxis-os-knowledge-base\"\u003EAXIS OS Knowledge base\u003C\u002Fa\u003E\u003C\u002Fspan\u003E | \u003Cspan class=\"keep\"\u003E\u003Ca class=\"link\" href=\"https:\u002F\u002Fyoutube.com\u002Fplaylist?list=PLds2O4jvLhI5tdifpixi91-flQrOn6S1h&si=vsS3etHWYN_QxwoN\"\u003EAXIS OS YouTube playlist \u003C\u002Fa\u003E\u003C\u002Fspan\u003E| \u003Cspan class=\"keep\"\u003E\u003Ca class=\"link\" href=\"https:\u002F\u002Fhelp.axis.com\u002Faxis-os-hardening-guide\"\u003EAXIS OS Hardening Guide\u003C\u002Fa\u003E\u003C\u002Fspan\u003E | \u003Cspan class=\"keep\"\u003E\u003Ca class=\"link\" href=\"https:\u002F\u002Fhelp.axis.com\u002Fsecurity-advisories\"\u003ESecurity Advisories\u003C\u002Fa\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E",urlAlias:"navigation"},{id:"t10220642",body:"\u003Cp\u003EAXIS OS is our operating system for edge devices. It’s used in more than 400 products with the broadest partner application reach in the security industry. It’s a Linux-based OS that’s built around openness, transparency and cybersecurity.\u003C\u002Fp\u003E\u003Cp\u003EWe have three support tracks: \u003Ca class=\"anchor link\" data-anchor=\"active-track\" href=\"#active-track\"\u003EActive track\u003C\u002Fa\u003E, \u003Ca class=\"anchor link\" data-anchor=\"lts-track\" href=\"#lts-track\"\u003ELong-term support track\u003C\u002Fa\u003E, and \u003Ca class=\"anchor link\" data-anchor=\"pss\" href=\"#pss\"\u003EProduct-specific support\u003C\u002Fa\u003E. \u003Cbr\u003ESee \u003Ca class=\"anchor link\" data-anchor=\"axis-os-lifecycle\" href=\"#axis-os-lifecycle\"\u003EAXIS OS lifecycle management\u003C\u002Fa\u003E for more details.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-style: italic;\"\u003E\u003Cspan style=\"font-weight: bold;\"\u003EAXIS OS support overview\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cimg alt=\"\" height=\"706\" src=\"\u002Fimage\u002Ft10208092.png\" width=\"2316\"\u003E\u003Cfigcaption\u003E\u003Csub\u003EThe active track releases a new version every 2–3 months where only the latest version is supported. The LTS tracks are created every two years and are supported and maintained for about 5 years.\u003C\u002Fsub\u003E\u003C\u002Ffigcaption\u003E",title:"About",urlAlias:"about-axis-os",toc:a},{id:"t10186724",body:"\u003Cp\u003EIn the schedule below you can find information about upcoming releases on the active track and the LTS tracks.\u003C\u002Fp\u003E\u003Ctable class=\"knowledge-table table table-bordered\"\u003E\u003Ctbody\u003E\u003Ctr class=\"knowledge-table-row\"\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan style=\"font-weight: bold;\"\u003EVersion\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan style=\"font-weight: bold;\"\u003ETrack\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan style=\"font-weight: bold;\"\u003EPreliminary release date\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan style=\"font-weight: bold;\"\u003EPlanned features and updates\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003C\u002Ftr\u003E\u003Ctr class=\"knowledge-table-row\"\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan class=\"keep\"\u003E12.4\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003EActive\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003EApril 2025\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EcURL version 8.12.0\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EAXIS CVE: CVE-2025-0325\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Ftd\u003E\u003C\u002Ftr\u003E\u003Ctr class=\"knowledge-table-row\"\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan class=\"keep\"\u003E11.11\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan class=\"keep\"\u003ELTS 2024\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003EMarch 2025\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EOpenSSL vesion 3.0.16 and 1.1.1zb\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EcURL version 8.12.0\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E AXIS CVE: CVE-2025-0324, CVE-2025-0361 and CVE-2024-47261\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Ftd\u003E\u003C\u002Ftr\u003E\u003Ctr class=\"knowledge-table-row\"\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan class=\"keep\"\u003E10.12\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan class=\"keep\"\u003ELTS 2022\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003EMarch\u002FApril 2025\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EOpenSSL vesion 1.1.1zb\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EcURL version 8.12.0\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E AXIS CVE: CVE-2024-47261\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Ftd\u003E\u003C\u002Ftr\u003E\u003Ctr class=\"knowledge-table-row\"\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan class=\"keep\"\u003E9.80\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan class=\"keep\"\u003ELTS 2020\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003EApril 2025\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EOpenSSL version 1.1.1zb\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EcURL version 8.12.0\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E AXIS CVE: CVE-2024-47261\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Ftd\u003E\u003C\u002Ftr\u003E\u003Ctr class=\"knowledge-table-row\"\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan class=\"keep\"\u003E8.40\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan class=\"keep\"\u003EProduct-specific support\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003EMay 2025\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EcURL version 8.12.0\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EOpenSSL version 1.1.1zb\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E AXIS CVE: CVE-2025-0325\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Ftd\u003E\u003C\u002Ftr\u003E\u003Ctr class=\"knowledge-table-row\"\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan class=\"keep\"\u003E6.50\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan class=\"keep\"\u003EProduct-specific support\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003EMarch 2025\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EcURL version 8.11.1\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E AXIS CVE: CVE-2024-47262\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Ftd\u003E\u003C\u002Ftr\u003E\u003C\u002Ftbody\u003E\u003C\u002Ftable\u003E\u003Cp\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EFor highlights and detailed release notes on AXIS OS releases, visit \u003Ca class=\"link\" href=\"https:\u002F\u002Fhelp.axis.com\u002Faxis-os-release-notes#axis-os-11\"\u003EAXIS OS Release Notes\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003ESubscribe to the \u003Ca class=\"link\" href=\"https:\u002F\u002Fyoutube.com\u002Fplaylist?list=PLds2O4jvLhI5tdifpixi91-flQrOn6S1h&si=vsS3etHWYN_QxwoN\"\u003EAXIS OS YouTube playlist\u003C\u002Fa\u003E to conveniently stay updated and informed.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EGo to to read more about scheduled and current AXIS OS releases.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EFor downloads, visit \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fsupport\u002Fdevice-software\"\u003EDownload device software\u003C\u002Fa\u003E page.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E To get the latest updates to your RSS feed, subscribe to the \u003Cimg alt=\"\" class=\"inline\" height=\"28\" src=\"\u002Fimage\u002Ft10146754.png\" style=\"vertical-align:middle;\" width=\"28\"\u003E\u003Ca class=\"link\" href=\"http:\u002F\u002Ffeeds.axis.com\u002Faxisfirmware\"\u003Eproduct firmware feed\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E",title:"Release schedule",urlAlias:"release-schedule",toc:a},{id:"t10194568",body:"\u003Cp\u003EAxis launches a new active track every two years, transitioning the previous active track into a long-term support (LTS) phase.\u003Cbr\u003E In September 2024, AXIS OS 11 entered the LTS 2024 phase, while the new active track, AXIS OS 12, was introduced. \u003C\u002Fp\u003E\u003Cp\u003EEach new active track focuses on delivering innovative features to advance AXIS OS and enhance its cybersecurity.\u003Cbr\u003EIn addition, pre-announced breaking changes are introduced at the start of the new track, communicated well in advance, with further changes during the lifecycle of the active track taking place but with limited impact.\u003C\u002Fp\u003E\u003Cimg alt=\"\" height=\"248\" src=\"\u002Fimage\u002Ft10198582.png\" width=\"801\"\u003E\u003Cp\u003E\u003Cbr\u003EA breaking change is an intentional modification which will break backwards compatibility. While Axis consistently strives to maintain backward compatibility, introducing breaking changes is sometimes necessary to:\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EImprove cybersecurity\u003C\u002Fspan\u003E: Axis may remove obsolete features or modify existing features to enhance security.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EUpdate functionality and improve usability\u003C\u002Fspan\u003E: Axis enhances existing functionality by implementing new default settings or introducing more advanced features to expand use cases.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003EIn both scenarios, Axis provides an alternative method for accomplishing the same tasks and communicates these changes in advance. Furthermore,\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"font-style: italic;\"\u003E the active track is the only place where these changes can be made, as maintaining compatibility is the primary focus of LTS tracks.\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003Cspan style=\"font-style: italic;\"\u003E\u003C\u002Fspan\u003E These changes are usually implemented after a new LTS track has been established, giving users sufficient time to adapt while maintaining security measures.\u003C\u002Fp\u003E\u003Cdiv class=\"warning\"\u003E\u003Cdiv class=\"note\"\u003ENote\u003C\u002Fdiv\u003E\u003Cdiv class=\"information\"\u003E\u003Cp class=\"warning-paragraph\"\u003E If you experience issues after upgrading to AXIS OS 12, utilize the rollback option to let the device revert back to its previous AXIS OS version. See guidelines \u003Ca class=\"link\" href=\"https:\u002F\u002Fhelp.axis.com\u002Faxis-os-knowledge-base#how-to-rollback\"\u003Ehere\u003C\u002Fa\u003E. We recommend that you keep at least one device running AXIS OS 12, generate a server report and contact Axis Technical Support for troubleshooting assistance or guidance.\u003C\u002Fp\u003E\u003C\u002Fdiv\u003E\u003C\u002Fdiv\u003E",title:"Breaking changes",urlAlias:"upcoming-breaking-changes",toc:a,sections:[{id:"t10204853",body:h,title:"Planned",urlAlias:"planned-breaking-changes",toc:a,sections:[{id:"t10201943",body:"\u003Cp\u003EChanges that apply to the first version of AXIS OS 13, coming in September 2026. Please note that the changes can be adjusted in future.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EACAP related changes:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ESigned ACAP applications\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EFrom AXIS OS 13.0, the option to allow unsigned applications is removed and only signed ACAP applications are allowed.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"334\" src=\"\u002Fimage\u002Ft10207644.png\" style=\"vertical-align:middle;\" width=\"665\"\u003E\u003C\u002Fp\u003E\u003Cp\u003EVAPIX API parameters that will be removed :\u003Cbr\u003E\u002Faxis-cgi\u002Fapplications\u002Fconfig.cgi?action=set&name=AllowUnsigned&value=true\u003Cbr\u003E\u002Faxis-cgi\u002Fapplications\u002Fconfig.cgi?action=set&name=AllowUnsigned&value=false\u003C\u002Fp\u003E\u003Cp\u003E Running unsigned ACAPs from any previous version of AXIS OS when upgrading to AXIS OS 13 will not be affected and the ACAP will continue to function normally. Only new ACAP installations in AXIS OS 13 are affected. \u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E To increase trust in ACAP applications and comply with international regulations and best practices for secure software delivery. \u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E New ACAPs to be installed in AXIS OS 13 must be signed, otherwise the ACAP installation will fail.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003ESecurity:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EPassword complexity enforcement\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe user is currently supported with a password strength indicator for selecting secure passwords for service accounts. However, the user might select insecure passwords anyway. It is planned to introduce a password complexity enforcement to enforce using secure-considered passwords when accessing an Axis device.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003EAfterward, it will not be possible to use insecure password combinations. It is expected that the password complexity enforcement will be standardized and will require a minimum password length of 14 characters including small and big letters, special signs and numbers, alternatively small and big letters with a password length of 64-characters. \u003Cbr\u003EMore information to come. The decision on when to introduce password complexity has not been made yet but will be communicated in time.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"400\" src=\"\u002Fimage\u002Ft10198465.png\" style=\"vertical-align:middle;\" width=\"439\"\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E To increase the cybersecurity level.\u003Cbr\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"609\" src=\"\u002Fimage\u002Ft10204638.png\" style=\"vertical-align:middle;\" width=\"2772\"\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E Will be updated shortly.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EHTTPS-only enforcement\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe current default behavior of Axis devices in factory defaulted state is that HTTP and HTTPS are both enabled allowing for a flexible choice on which protocol to use to connect to the Axis device. Axis, since many years, has given the recommendation to configure the Axis device to HTTPS-only during initial configuration according to the \u003Ca class=\"link\" href=\"https:\u002F\u002Fhelp.axis.com\u002Faxis-os-hardening-guide#https\"\u003E AXIS OS Hardening Guide\u003C\u002Fa\u003E. Please see the current default settings below.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"361\" src=\"\u002Fimage\u002Ft10198463.png\" style=\"vertical-align:middle;\" width=\"725\"\u003E\u003C\u002Fp\u003E\u003Cp\u003EThis default behavior is likely to change in order to increase overall default security and protect communication between the Axis device and the human user as well as applications. Axis has plans to change the default behavior so that HTTP communication will be disabled, and HTTPS-only communication is the only enabled protocol to be used in factory defaulted state.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"298\" src=\"\u002Fimage\u002Ft10198464.png\" style=\"vertical-align:middle;\" width=\"563\"\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E To increase the cybersecurity level.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using HTTP, it will not work correctly with AXIS OS 13 or higher.\u003C\u002Fp\u003E\u003Cp\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E",title:"Changes in AXIS OS 13",urlAlias:"changes-in-axis-os-13",toc:a},{id:"t10223152",body:"\u003Cp\u003EChanges that apply to the first version of AXIS OS 14, coming in September 2028. Please note that the changes can be adjusted in future.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EAPI changes:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoval of unofficial certificate management\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe unofficial and externally undocumented custom certificate management API with the VAPIX endpoints \u003Cspan style=\"font-style: italic;\"\u003E\u002Faxis-cgi\u002Fcertappmgmt.cgi\u003C\u002Fspan\u003E and \u003Cspan style=\"font-style: italic;\"\u003E\u002Faxis-cgi\u002Fcertmgmt.cgi\u003C\u002Fspan\u003E will be removed. For supported AXIS OS certificate management and enrollment APIs, please refer to the \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fvapix-library\u002Fsubjects\u002Ft10175981\u002Fsection\u002Ft10035974\u002Fdisplay\"\u003EVAPIX Library\u003C\u002Fa\u003E. \u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E Unofficial and undocumented APIs shall not be used due to the security risk. Thus, it is removed since there are other VAPIX APIs that can be used instead. \u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this API, it will not work correctly with AXIS OS 14 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E",title:"Changes in AXIS OS 14",urlAlias:"changes-in-axis-os-14",toc:a}]},{id:"t10204852",body:h,title:"Applied",urlAlias:"applied-breaking-changes",toc:a,sections:[{id:"t10214433",body:"\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EEdge Storage:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoval of vFAT\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe ability to format SD cards to the vFAT system file will be removed. However, they can still be used as before. A long time ago, SD cards were delivered with vFAT as the standard file system for cards up to 32GB. Since such SD cards are no longer used, the usefulness of vFAT is very limited.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E Axis has since start recommended Ext 4. vFat should never be used.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003EIf necessary, you will need to format the SD card outside the device.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"502\" src=\"\u002Fimage\u002Ft10207682.png\" style=\"vertical-align:middle;\" width=\"842\"\u003E\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003ENetwork & Discovery:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EDisabled UPnP discovery protocol\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EAxis devices currently have UPnP and Bonjour enabled in factory defaulted state for general device discovery. The Bonjour protocol allows for device detection within the local subnet where the device is located (example: 192.168.1.0\u002F24). The UPnP protocol allows device discovery across networks (example: 192.168.1.0\u002F24 and 192.168.2.0\u002F24) but only if multicast-routing is properly configured. Axis believes that the device detection within the local subnet is the main use case for a discovery protocol and therefore will disable UPnP in factory defaulted devices moving forward. This will also lower the attack surface of the device and increase the overall network security. The UPnP protocol remains available in Axis devices with the option for the user to enable it if needed.\u003C\u002Fp\u003E\u003Cp\u003EVAPIX API parameter: \u003Cspan style=\"font-style: italic;\"\u003Eroot.Network.UPnP.Enabled\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"292\" src=\"\u002Fimage\u002Ft10207647.png\" style=\"vertical-align:middle;\" width=\"851\"\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E To lower the attack surface of the device and increase the overall device security.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software only using UPnP for device discovery, it will not work correctly with AXIS OS 12.1 or higher and users need to enable UPnP first on the Axis device.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003ESecurity:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EBasic authentication for HTTPS connections\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EAxis devices perform digest authentication when serving both HTTP and HTTPS connections. Since HTTPS connections are preferred for increased security, Axis will change the default behavior so that basic authentication is used for HTTPS connections only by introducing a new authentication policy mode called \"Recommended\". The authentication policy for HTTP & the RTSP server will not change in this mode. More information about the authentication policy can be found in the \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fvapix-library\u002Fsubjects\u002Ft10175981\u002Fsection\u002Ft10007717\u002Fdisplay?section=t10007717-t10158867\"\u003EVAPIX Library\u003C\u002Fa\u003E. Using basic authentication in HTTPS connections is IT-industry standard and allows Axis devices to operate in a well-defined and common practice as well. Digest authentication will still be kept for serving for unencrypted HTTP connections. Using HTTPS only is the recommended operational mode for Axis devices.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E To follow the IT-industry standard.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you use digest authentication for HTTPS connection, it will not work correctly with AXIS OS 12.1 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E",title:"Changes in AXIS OS 12.1",urlAlias:"changes-in-axis-os-12-1",toc:a},{id:"t10201932",body:"\u003Cimg alt=\"\" height=\"465\" src=\"\u002Fimage\u002Ft10209761.png\" width=\"676\"\u003E\u003Cp\u003E\u003Cbr\u003ECheck out the \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=964zGkbpkDY\"\u003EAXIS OS 12 Technical Update - Breaking Changes\u003C\u002Fa\u003E video, to learn more about the upcoming changes.\u003C\u002Fp\u003E\u003Cp\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoval of the old web interface\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe old web interface, also called “\u003Ca class=\"link\" href=\"https:\u002F\u002Fhelp.axis.com\u002Fen-us\u002Faxis-os-knowledge-base#axis-os-web-version-b\"\u003EAXIS OS web version B\u003C\u002Fa\u003E”, will be removed.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E The old web interface is no longer needed since the \u003Ca class=\"link\" href=\"https:\u002F\u002Fhelp.axis.com\u002Fen-us\u002Faxis-os-knowledge-base#axis-os-web-version-c\"\u003Enew interface\u003C\u002Fa\u003E has all implemented features . It is removed to save memory space on the device and to simplify both usage and maintenance. Additionally, the old web interface used a number of outdated libraries and removing it will make the device more secure.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E The new web interface will be displayed after upgrade.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003ESecurity:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EDisabled HTTP Port 80 redirects\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EIn previous security penetration tests, Axis was advised to disable HTTP Port 80 redirects in order to enhance security and to prevent information leakage. Currently, Axis devices are configured for HTTPS-only, but the HTTP port 80 redirects are enabled to inform users\u002Fclients that communication is not permitted on port 80 and redirecting them automatically to port 443 instead. Axis will follow the general recommendation provided by third-party penetration test laboratories and will deactivate HTTP port 80 redirects when the device is set to HTTPS-only mode.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"408\" src=\"\u002Fimage\u002Ft10198469.png\" style=\"vertical-align:middle;\" width=\"1473\"\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003Cp\u003ETo test the possible impact, configure your Axis device for HTTPS only and configure a firewall rule in AXIS OS 11.9 as shown below, where the Axis device would effectively block communication on port 80 for a specific client trying to connect.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"443\" src=\"\u002Fimage\u002Ft10205440.png\" style=\"vertical-align:middle;\" width=\"1320\"\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"608\" src=\"\u002Fimage\u002Ft10205441.png\" style=\"vertical-align:middle;\" width=\"1320\"\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E To lower the attack surface of the device and increase the overall device security.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you access the Axis device via HTTP, it will not work correctly with AXIS OS 12.0 or higher. Please use HTTPS instead.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoved support for TLS 1.0\u002F1.1 HTTPS connections\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EAxis devices support modern encryption technology through TLS 1.2\u002F1.3, which is used by default for HTTPS connections. However, there is also an option to enable older, outdated and insecure TLS 1.0\u002F1.1 versions for backward compatibility with legacy systems that cannot support more secure HTTPS connections. Axis will completely remove TLS 1.0\u002F1.1 versions for HTTPS connections to increase overall security and prevent users from accidentally enabling these protocol versions.\u003C\u002Fp\u003E\u003Cp\u003EVAPIX API Parameter: \u003Cspan style=\"font-style: italic;\"\u003Eroot.HTTPS.AllowTLS1 \u003C\u002Fspan\u003Eand\u003Cspan style=\"font-style: italic;\"\u003E root.HTTPS.AllowTLS11\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"1032\" src=\"\u002Fimage\u002Ft10198467.png\" style=\"vertical-align:middle;\" width=\"2189\"\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E It is obsolete, and keeping it might be a security threat.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using TLS 1.0\u002F1.1 HTTPS connections, it will not work correctly with AXIS OS 12.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoved support for OpenSSL 1.1.1\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ESince AXIS OS 11.6 (August 2023), Axis devices support simultaneously version 1.1.1 and 3.0 of the cryptographic software backend OpenSSL. To allow for smooth transition, OpenSSL 1.1.1 will still be supported until LTS 2024 track is launched and in that track. With AXIS OS 12, OpenSSL 1.1.1 support will be removed. Patches and security updates of OpenSSL 1.1.1 will still be supported on active AXIS OS long-term support tracks as Axis has signed a support contract with the OpenSSL foundation to receive prolonged support. \u003C\u002Fp\u003E\u003Cp\u003E\u003C\u002Fp\u003E\u003Cp\u003ENote that upcoming changes may affect ACAPs. To ensure compatibility and security, it is recommended to use \u003Cspan class=\"keep\"\u003E\u003Ca class=\"link\" href=\"https:\u002F\u002Fgithub.com\u002FAxisCommunications\u002Facap-native-sdk-examples\u002Ftree\u002Fmain\u002Fcurl-openssl\"\u003EOpenSSL 3.X\u003C\u002Fa\u003E\u003C\u002Fspan\u003E, which is available in ACAP Native SDK 1.14 \u002F AXIS OS 11.10. Alternatively, ACAPs can \u003Ca class=\"link\" href=\"https:\u002F\u002Fgithub.com\u002FAxisCommunications\u002Facap-native-sdk-examples\u002Ftree\u002Fmain\u002Futility-libraries\u002Fopenssl_curl_example\"\u003Eembed a custom cryptographic library\u003C\u002Fa\u003E to meet their specific needs.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E It is obsolete as the active track runs a newer version.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using OpenSSL 1.1.1, it will not work correctly with AXIS OS 12.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003ENetwork & Discovery:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EIPv4 address changes\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ETo date, Axis devices have never been IPv4 compliant following the corresponding RFC framework. That resulted in the Axis device having a default IP-address which is 192.168.0.90\u002F24. This circumstance leads to network related issues that we want to resolve. For instance, if no DHCP server is available on the network, the default IP address of Axis devices currently is 192.168.0.90\u002F24 regardless of whether anyone on the same network segment already uses the same IP address. This may cause service interruptions for other devices if such IP address conflict occurs. At the same time, the link-local address (169.254.x.x\u002F16) is enabled by default regardless of whether it’s used, which is not in compliance with the RFC standard.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003Cp\u003EWith the above changes in place, there will be no default IP addresses of AXIS OS devices anymore. The Axis OS devices will use the IP addresses either from a DHCP server or statically configured address. The devices will only fall back to link-local addresses if there is an IP address conflict detected, or a DHCP server is unavailable in the network. More information regarding the IPv4 addressing change can be found \u003Ca class=\"link\" href=\"https:\u002F\u002Fhelp.axis.com\u002Faxis-os-knowledge-base#ipv4-compliant-mode\"\u003Ehere\u003C\u002Fa\u003E. \u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cli class=\"knowledge-list-item-skip knowledge-list-item-sublist\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003ETo be completely RFC IPv4 compliant.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EDisable link-local address when it is not used. \u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EBetter user experience for our customers when multiple factory-defaulted Axis devices are placed on the same network simultaneously.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EIncrease robustness and detect IP address conflicts.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E Affects during installation, AXIS devices will request IP adress from the network it attaches to etc DHCP.\u003Cbr\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Fli\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EDisabled WS-Discovery protocol\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EAxis devices currently have the WS-Discovery (WebService-Discovery) protocol enabled in factory defaulted state as additional option for ONVIF-related device discovery. However, the ONVIF interface is not enabled in factory defaulted state which makes the availability of the WS-Discovery protocol by default obsolete. Axis will adapt the default behavior and will disable the WS-discovery protocol in factory defaulted state. This means a user need to enable the WS-discovery protocol if desired. \u003C\u002Fp\u003E\u003Cp\u003EVAPIX API parameter: \u003Cspan style=\"font-style: italic;\"\u003EWebService.DiscoveryMode.Discoverable\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"292\" src=\"\u002Fimage\u002Ft10207647.png\" style=\"vertical-align:middle;\" width=\"851\"\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E To lower the network footprint and increase the cybersecurity level of an Axis device when ONVIF is not being used.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E You will not be able to discover the device until WS-Discovery has been enabled.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EPossibility to disable Basic Device Info VAPIX API\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003Cbr\u003EThe \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fvapix-library\u002Fsubjects\u002Ft10175981\u002Fsection\u002Ft10132180\u002Fdisplay\"\u003EBasic Device Information\u003C\u002Fa\u003E VAPIX API allows to retrieve general information about the Axis product with no authentication. This is useful for device discovery and profiling during network and application onboarding. Axis will implement an additional VAPIX parameter that will allow the user to disable the basic device information API if needed. The ability for the user to disable this VAPIX API may be considered a behavioral change if unknown.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E Provide the ability to reduce the attack surface and information leakage of the device, increasing the overall security resilience of the network.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this API after onboarding, it will not work correctly with AXIS OS 12.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoval of releaseinfo.cgi\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003Cbr\u003EThe \u003Cspan style=\"font-style: italic;\"\u003Eaxis-release\u002Freleaseinfo.cgi\u003C\u002Fspan\u003E VAPIX API has been removed. It is recommended to use the Basic Device Information VAPIX API instead, see more info in the \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fvapix-library\u002F\"\u003EVAPIX Library\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003Cp\u003E Example output of \u003Cspan style=\"font-style: italic;\"\u003Eaxis-release\u002Freleaseinfo.cgi\u003C\u002Fspan\u003E:\u003C\u002Fp\u003E\u003Cp\u003E\u003Ccode class=\"text-code-example\"\u003Epart=6975649029\u003C\u002Fcode\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Ccode class=\"text-code-example\"\u003Eversion:11.2.53\u003C\u002Fcode\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E It is obsolete and replaced by a different API.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoval of getBrand.cgi\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003Cbr\u003EThe previously deprecated VAPIX API \u003Cspan style=\"font-style: italic;\"\u003Eaxis-cgi\u002Fprod_brand_info\u002Fgetbrand.cgi\u003C\u002Fspan\u003E has been removed. It is recommended to use the Basic Device Information VAPIX API instead, see more info in the \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fvapix-library\u002F\"\u003EVAPIX Library\u003C\u002Fa\u003E. Please find below an example output of the information that was possible to receive through getBrand.cgi, all the information is still available and covered in the referenced Basic Device Information VAPIX API.\u003C\u002Fp\u003E\u003Cp\u003E Example output of \u003Cspan style=\"font-style: italic;\"\u003EgetBrand.cgi\u003C\u002Fspan\u003E:\u003C\u002Fp\u003E\u003Cp\u003E\u003Ccode class=\"text-code-example\"\u003EBrand.Brand=AXIS\u003C\u002Fcode\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Ccode class=\"text-code-example\"\u003EBrand.ProdFullName=AXIS P3265-LV Dome Camera\u003C\u002Fcode\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Ccode class=\"text-code-example\"\u003EBrand.ProdNbr=P3265-LV\u003C\u002Fcode\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Ccode class=\"text-code-example\"\u003EBrand.ProdShortName=AXIS P3265-LV\u003C\u002Fcode\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Ccode class=\"text-code-example\"\u003EBrand.ProdType=Dome Camera\u003C\u002Fcode\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Ccode class=\"text-code-example\"\u003EBrand.ProdVariant=\u003C\u002Fcode\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Ccode class=\"text-code-example\"\u003EBrand.WebURL=http:\u002F\u002Fwww.axis.com\u003C\u002Fcode\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E It is obsolete and replaced by a different API.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoval of network filter API\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe current IP-filtering VAPIX API will be replaced by a more feature-rich firewall application that can be configured through JSON REST API. The new firewall service will be available in AXIS OS 11.8 (January 2024) and can be used from there on. \u003Cbr\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"276\" src=\"\u002Fimage\u002Ft10207646.png\" style=\"vertical-align:middle;\" width=\"747\"\u003E\u003Cbr\u003EThe legacy network filter API with the following below parameters will be removed in AXIS OS 12:\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-style: italic;\"\u003ENetwork.Filter.Enabled\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-style: italic;\"\u003ENetwork.Filter.Input.AcceptAddresses\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-style: italic;\"\u003ENetwork.Filter.Input.Policy\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-style: italic;\"\u003ENetwork.Filter.Log.Enabled\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E It is obsolete and replaced by the new host-based firewall.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EEdge Storage:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoved support for SMB 1.0 and 2.0\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe Server Message Block Protocol (SMB) is widely used for mounting network shares when storing recordings. While secure versions of the SMB protocol are supported and available in Axis devices (2.1, 3.0, 3.02 and 3.1.1), the insecure versions (1.0 and 2.0) are still available to use but disabled in factory defaulted state. Axis will remove version 1.0 and 2.0 completely to increase the overall security and to prevent users from enabling these protocol versions by mistake.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"445\" src=\"\u002Fimage\u002Ft10198468.png\" style=\"vertical-align:middle;\" width=\"491\"\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E It is obsolete, and keeping it might be a security threat.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have a storage connection requiring these versions, they will not work anymore.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EACAP application related changes:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cdiv class=\"warning\"\u003E\u003Cdiv class=\"notice\"\u003ENOTICE\u003C\u002Fdiv\u003E\u003Cdiv class=\"information\"\u003E\u003Cp class=\"warning-paragraph\"\u003EBefore upgrading to AXIS OS 12.0 or higher, note that certain applications require updates. See the respective documentation for more information.\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cspan style=\"font-weight: bold;\"\u003EAXIS Perimeter Defender 3.6.0 required. \u003C\u002Fspan\u003EVersions 3.5.1 and earlier are not compatible with AXIS OS 12.0 or higher. Follow these \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fdam\u002Fpublic\u002F0d\u002F2c\u002F0a\u002Fhow-to-upgrade-to-axis-os-12-with-axis-perimeter-defenderpdf-en-US-452254.pdf\"\u003Einstructions\u003C\u002Fa\u003E to perform the upgrade correctly.\u003C\u002Fli\u003E\u003Cli\u003E\u003Cspan style=\"font-weight: bold;\"\u003EAXIS License Plate Verifier 2.12.8 required.\u003C\u002Fspan\u003E Versions 2.8.4 or earlier are not compatible with AXIS 12 or higher. Follow these \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fdam\u002Fpublic\u002F10\u002F59\u002F21\u002Fhow-to-upgrade-to-axis-os-12-with-axis-license-plate-verifierpdf-en-US-452259.pdf\"\u003Einstructions\u003C\u002Fa\u003E to perform the upgrade correctly.\u003C\u002Fli\u003E\u003Cli\u003E\u003Cspan style=\"font-weight: bold;\"\u003EAXIS People Counter 5.0.5 required. \u003C\u002Fspan\u003EVersions 4.6.108 and earlier are not compatible with AXIS OS 12 or higher. Follow these \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fdam\u002Fpublic\u002Fbf\u002Fff\u002F6c\u002Fhow-to-upgrade-to-axis-os-12-with-axis-people-counterpdf-en-US-452253.pdf\"\u003Einstructions\u003C\u002Fa\u003E to perform the upgrade correctly.\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Fdiv\u003E\u003C\u002Fdiv\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoval of root-privileges\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ERoot-privileged access to Axis products and ACAP applications has been removed indefinitely without the possibility to enable it. The previously available parameter in AXIS OS 11 to enable root privileges has been removed. This change applies to the factory default settings as well as when upgrading to AXIS OS 12 from any previous version of AXIS OS. \u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003EThis change increases ACAP confidentiality by better protecting their data and secrets, preventing information leakage and increasing AXIS OS system integrity. Please read the \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fdeveloper-community\u002Fnews\u002Faxis-os-root-acap-signing\"\u003Efull guide\u003C\u002Fa\u003E for more information.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E To increase the security on the device. \u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E \u003Cbr\u003EACAPs that do not use root-privileges are not affected. \u003Cbr\u003EACAPs with root privileges, will not work with AXIS OS 12.0 or higher. Check the installed ACAP applications carefully! Make sure they are working properly. If possible, select the LTS 2024 track.\u003Cbr\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EPossible scenarios where failures could be expected are:\u003C\u002Fspan\u003E\u003Cbr\u003EThe ACAP cannot run because it tries to use the previously available root user with root privileges.\u003Cbr\u003EThe post-install script may be using root-privileges, which prevents the ACAP from being installed or run. \u003Cbr\u003EThe pre-uninstall script may be using root-privileges, which may prevent ACAP data from being cleaned up at installation.\u003Cbr\u003EThe ACAP tries to access file system resources or functionality that is locked behind root-privileges.\u003Cbr\u003EThe ACAP applications that include or need access to security-sensitive functionality will not work anymore. For example, VPN-capable solutions based on Tailscale, ZeroTier, IPsec, OpenVPN and WireGuard that may have been deployed as an ACAP previously, will not work in AXIS OS 12. Axis is looking into how and if a VPN-client can be embedded into the AXIS OS operating system natively.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ESigned ACAP applications\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003Cbr\u003E From AXIS OS 12.0, the option to allow unsigned apps will be disabled in factory defaulted state. To upload unsigned ACAPs, users must enable this option. This only applies to factory-defaulted products running AXIS OS 12 or higher.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"334\" src=\"\u002Fimage\u002Ft10207644.png\" style=\"vertical-align:middle;\" width=\"665\"\u003E\u003C\u002Fp\u003E\u003Cp\u003EVAPIX API parameters:\u003Cbr\u003E\u003Cspan style=\"font-style: italic;\"\u003E \u002Faxis-cgi\u002Fapplications\u002Fconfig.cgi?action=set&name=AllowUnsigned&value=true\u003Cbr\u003E \u002Faxis-cgi\u002Fapplications\u002Fconfig.cgi?action=set&name=AllowUnsigned&value=false \u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003ERunning unsigned ACAPs from any previous version of AXIS OS when upgrading to AXIS OS 12 will have no impact and the ACAP will continue to function normally. For more information and a timeline, see \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fdeveloper-community\u002Fnews\u002Faxis-os-root-acap-signing\"\u003EAdditional security in AXIS OS and ACAP applications.\u003C\u002Fa\u003E\u003Cbr\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E To lower the attack surface of the device and increase the overall device security.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E For factory default devices, you will need to enable Allow unsigned apps.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EACAP installation behaviour\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe ACAP installation is now aborted if the post-install script exit on EX_NOPERM (77). Previously, the ACAP is installed nevertheless and warnings were printed in the log files. Uninstall will happen regardless of pre-uninstall script error and will write the error code to the log.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E To increase the ACAPS reliability on the market.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E ACAP vendors are informed and should compile a new ACAP version without errors if affected.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoval of Basic analytics ACAP applications\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EDue to updates to our framework, it is not possible to support some older types of ACAP applications and they will therefore be removed. \u003Cbr\u003EThis applies to Axis Basic Enter-Exit, Axis Basic Object Counter and Axis Basic Object Removed\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E Due to architectural changes.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you are using any of these ACAPs, do not upgrade until the system has a verified replacer.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoval of libcapture library\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe libcapture library for ACAPs is obsolete and will be removed. It is recommended to use the Video capture API instead. For more information, visit the \u003Ca class=\"link\" href=\"https:\u002F\u002Faxiscommunications.github.io\u002Facap-documentation\u002Fdocs\u002Fapi\u002Fnative-sdk-api.html#video-capture-api-vdo\"\u003EACAP SDK Documentation\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E It is obsolete, and keeping it might be a security threat.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have an ACAP using this library, it will not work correctly with AXIS OS 12.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoval of vaconfig.cgi\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe ACAP applications managed by the vaconfig.cgi API is no longer supported, this configuration and management API is therefore obsolete and will be removed.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E It is obsolete, and keeping it might be a security threat. \u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have an ACAP using this library, it will not work correctly with AXIS OS 12.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoval of ACAP Computer Vision SDK support\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe ability to enable ACAP Computer Vision SDK support will be removed for the listed products because they only have 1 GB of memory. \u003Cbr\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EApplies to\u003C\u002Fspan\u003E: AXIS D2210–VE, AXIS M3215-LVE, AXIS M3216-LVE, AXIS M5526-E, AXIS P1465-LE, AXIS P1465-LE-3, AXIS P3265-LV\u002F-LVE\u002F-V and AXIS P3265-LVE-3\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E Running the Computer Vision SDK on the product will consume too much memory and may render the product inoperable.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have an ACAP using the Computer Vision SDK, it will not work correctly with AXIS OS 12.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EFile execution on edge storage\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EIn AXIS OS 12, to allow ACAPs to execute files or binaries from edge storage (such as an SD card or network share), the user must explicitly configure the Axis device. This can be achieved by setting up the Extra Mount Options in Plain Config, as described below.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"622\" src=\"\u002Fimage\u002Ft10213399.png\" style=\"vertical-align:middle;\" width=\"1018\"\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003EAs a result of this change, in the factory default state of AXIS OS 12, file execution from edge storage is disabled and must be explicitly configured.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E To increase the security on the device.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E ACAPs requiring file execution on edge storage may not function properly if the device is not configured accordingly.\u003Cbr\u003E\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E API changes:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERate Control changes for RTSP\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003Cbr\u003EAs the VAPIX Rate Control API has evolved over the years, the relationship between some of the URL options and \u003Cspan style=\"font-style: italic;\"\u003Eparam.cgi\u003C\u002Fspan\u003E parameters has become complicated. This will be simplified in upcoming versions of Axis OS. This was communicated earlier \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fdeveloper-community\u002Fnews\u002Frate-control-api\"\u003Ehere\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E To simplify the Rate control API.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E The new API is supported by the product when Properties.Image.RateControl.Version is 2.0 and higher. videobitrate and Image.I#.RateControl.TargetBitrate are deprecated from now No changes are made when it comes to Average Bitrate (ABR).\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemove Legacy Overlays\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe possibility to create overlays via the parameter CGI will be completely deprecated. This was communicated earlier \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fdeveloper-community\u002Fnews\u002Flegacy-overlays\"\u003Ehere\u003C\u002Fa\u003E. An example of the old overlay is provided below.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"802\" src=\"\u002Fimage\u002Ft10198460.png\" style=\"vertical-align:middle;\" width=\"1430\"\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E Overlays have their own API, dynamicoverlay CGI, with direct access to the overlay system. There for should this old way be deprecated.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EAdded path restrictions for dynamicoverlay.cgi\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fvapix-library\u002Fsubjects\u002Ft10175981\u002Fsection\u002Ft10007638\u002Fdisplay?section=t10007638-t10119641\"\u003EDynamic Overlay\u003C\u002Fa\u003E VAPIX API that allows to configure the path to the overlay image to display has been limited to \u002Fetc\u002Foverlays\u002F. It is not possible anymore to alter the path through VAPIX API.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E Supporting to alter the path trough API is not best practice and keeping it might be a security threat.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EChanges in dynamicoverlay.cgi\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EOptional values, “source” and “sensor” will be removed from the \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fvapix-library\u002Fsubjects\u002Ft10175981\u002Fsection\u002Ft10007638\u002Fdisplay?section=t10007638-t10119641\"\u003EDynamic Overlay\u003C\u002Fa\u003Ein AXIS OS 12.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E The options are obsolete and no longer used and should therefore be removed to follow best practice.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ENew version of privacymask.cgi. \u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EUnused functionality or parameters have been removed, while those utilized in the previous version have been preserved.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003EThe following will be removed in privacymask.cgi:\u003Cbr\u003E\u003Cspan style=\"font-style: italic;\"\u003Epreview_on \u003Cbr\u003Epreview_off\u003Cbr\u003Equery list \u003Cbr\u003Equery position\u003Cbr\u003Eptpolygon \u003Cbr\u003Eimagerotation \u003Cbr\u003Eimageresolution\u003Cbr\u003Ezoomlowlimit \u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003EThe following will be removed in param.cgi:\u003Cbr\u003E\u003Cspan style=\"font-style: italic;\"\u003Eparameter Image.I[source].Overlay.MaskWindows.PtPolygon\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E Supporting capabilities that are not used is not best practice and keeping them might be a security threat. \u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoval of \"ClassCandidate\" from Analytics Scene description for ONVIF\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EIn the analytics scene description, both \"tt:ClassDescriptor\u002Ftt:ClassCandidate\" and \"tt:ClassDescriptor\u002Ftt:Type\" are used today for backward comparability, but they say the same information. ONVIF recommends the use of \"tt:ClassDescriptor\u002Ftt:Type\", see \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.onvif.org\u002Fver10\u002Fschema\u002Fmetadatastream.xsd\"\u003Emetadatastream.xsd\u003C\u002Fa\u003E—\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EAXIS OS 11.11 and lower\u003C\u002Fspan\u003E\u003Cbr\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"470\" src=\"\u002Fimage\u002Ft10208091.png\" style=\"vertical-align:middle;\" width=\"644\"\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EAXIS OS 12.0 and higher\u003C\u002Fspan\u003E\u003Cbr\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"398\" src=\"\u002Fimage\u002Ft10208090.png\" style=\"vertical-align:middle;\" width=\"648\"\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E Axis should be in compliant with ONVIF. \u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EUpdating terminology from “Vehical” to “Vehicle” for ONVIF\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EDue to an error in the ONVIF Metadata Spec, “Vehicle” has been incorrectly represented as “Vehical”, in the Analytics Scene description. As of AXIS OS 12, the correct term “vehicle” will be used instead.\u003Cbr\u003ESee code example at \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fdeveloper-community\u002Fnews\u002Fmetadata-stream-os-12\"\u003EChanges in the analytics metadata stream in AXIS OS 12.0\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E Axis should be in compliant with ONVIF. \u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EUpdating terminology from “Bicycle” to “Bike” in VehicleType for ONVIF\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ECurrently in the Analytics Scene description, the term “Bicycle” is used to describe both a bicycle and a motorcycle within the context of “VehicleType”. As of AXIS OS 12.0, “Bike” will be used instead of “Bicycle” to describe both bicycles and motorcycles according to the ONVIF Standard, and it will be represented as an “ObjectType”. \u003Cbr\u003ESee code example at \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fdeveloper-community\u002Fnews\u002Fmetadata-stream-os-12\"\u003EChanges in the analytics metadata stream in AXIS OS 12.0\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E Axis should be in compliant with ONVIF. \u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoval of the lightcontrol web service API\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe lightcontrol web service API (implemented in ws\u002Fwsd\u002Fimpl\u002Fali) has been deprecated for many years and is replaced by the lightcontrol-cgi JSON API. Information about this change has been sent out previously to partners.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E It is obsolete, and keeping it might be a security threat. \u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EProduct specific:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemove support for AXIS T6101\u002FT6112\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ESupport for AXIS T6101 and AXIS T6112 will be removed. Read more about compatible products on \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fproducts\u002Faxis-t6101-audio-and-io-interface\u002Fsupport#compatible-products\"\u003Eaxis.com\u003C\u002Fa\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E AXIS T6101 and AXIS T6112 are discontinued.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E AXIS T6101 and AXIS T6112 does not work with Axis devices running AXIS OS 12.0 or higher. Please use AXIS OS LTS 2024 instead.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E",title:"Changes in AXIS OS 12.0",urlAlias:"changes-in-axis-os-12",toc:a},{id:"t10201933",body:"\u003Cp\u003EPlease note that some breaking was done AXIS OS 11, but with limited impact. \u003C\u002Fp\u003E\u003Cp\u003EThe changed default behavior in AXIS OS 11 will affect the product after a\u003Cspan style=\"font-weight: bold;\"\u003E factory reset\u003C\u002Fspan\u003E, as well as new products launched with that specific version, but will not affect an upgrade, i.e. if you upgrade AXIS OS without a factory reset, your products will not change their behavior.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003ESecurity:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemove access via FTP protocol\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ESince AXIS OS 11.1, we have removed the possibility to access the device via the FTP protocol, to increase overall minimum cybersecurity level. \u003Cbr\u003EFor troubleshooting purposes it is recommended to use secure SSH access. Note that upload from the device to an FTP server is still possible. For more information, visit SSH access in the AXIS OS Knowledge base.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E To increase overall security.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this feature, it will not work correctly with AXIS OS 11.1 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoved support for proxy SOCKS version 4 and 5\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ESince AXIS OS 11.0, support for proxy SOCKS version 4 and 5 has been removed.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E It is obsolete, and keeping it might be a security threat. \u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this feature, it will not work correctly with AXIS OS 11.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ENo dedicated root user in factory defaulted state\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ESince AXIS OS 11.5, no dedicated root user is pre-configured in factory defaulted state. To ease \u003Cspan class=\"keep\"\u003EO3C-related\u003C\u002Fspan\u003E integrations and to allow time to adapt, Axis made a modification that currently creates this root user for O3C onboarding\u002Fintegration. From LTS 2024, O3C integrations shall not rely on the previously available admin user named “root”. If a separate (admin) user is deemed necessary for some purpose, this user shall be specifically created during the initial onboarding\u002Fintegration.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E To lower the attack surface of the device and increase the overall device security.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using root as hardcoded username, it will not work correctly with AXIS OS 11.5 or higher unless you create a user root.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERoot-privilege is disabled in factory defaulted state\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ERoot-privileged access is disabled by default in Axis products and ACAP applications to increase ACAP confidentiality by better protecting their data and secrets, to prevent information leakage and to increase AXIS OS system integrity by removing system-wide root-privileged access for users and applications. In AXIS OS 11, this can still be enabled by parameter if required, see screenshots below for reference:\u003C\u002Fp\u003E\u003Cp\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"320\" src=\"\u002Fimage\u002Ft10207645.png\" style=\"vertical-align:middle;\" width=\"658\"\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"213\" src=\"\u002Fimage\u002Ft10207661.png\" style=\"vertical-align:middle;\" width=\"647\"\u003E\u003C\u002Fp\u003E\u003Cp\u003EPlease read the \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fdeveloper-community\u002Fnews\u002Faxis-os-root-acap-signing\"\u003Efull guide\u003C\u002Fa\u003E for more information. The changes in AXIS OS 11 are summarized below.\u003Cbr\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E To increase the security on the device.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E Affected ACAPs has been communicated about this and should create a new version if they are affected regarding this change.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli class=\"knowledge-list-item-skip knowledge-list-item-table\"\u003E\u003Ctable class=\"knowledge-table table table-bordered\"\u003E\u003Ctbody\u003E\u003Ctr class=\"knowledge-table-row\"\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan style=\"font-weight: bold;\"\u003EAXIS OS\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan style=\"font-weight: bold;\"\u003ETimeline\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan style=\"font-weight: bold;\"\u003EChanges\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003C\u002Ftr\u003E\u003Ctr class=\"knowledge-table-row\"\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E11.5\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003EJune 2023\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EVAPIX\u002FWeb Access: The user “root” is an ordinary administrator. \u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EACAP Privileges: Root privileges can be disabled.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Ftd\u003E\u003C\u002Ftr\u003E\u003Ctr class=\"knowledge-table-row\"\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E11.6\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003ESeptember 2023\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003ESSH Access: Root user access can be disabled.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Ftd\u003E\u003C\u002Ftr\u003E\u003Ctr class=\"knowledge-table-row\"\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E11.8\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E January 2024\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003ESSH Access: Root user access is disabled by default but can be enabled. \u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EACAP Privileges: Root privileges is disabled by default but can be enabled.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Ftd\u003E\u003C\u002Ftr\u003E\u003Ctr class=\"knowledge-table-row\"\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E11.11\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003EJune 2024\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EAxis devices only accept installation of signed ACAP applications by default. Devices can be configured to accept unsigned applications\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Ftd\u003E\u003C\u002Ftr\u003E\u003Ctr class=\"knowledge-table-row\"\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E LTS 2024\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E H2 2024\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cp\u003ESupport: 2024-2029. Can be used as a stop-gap solution until an ACAP application is fully adapted.\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003ESSH Access: Root user access is disabled by default but can be enabled.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EACAP Privileges: Root privileges is disabled by default but can be enabled.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Ftd\u003E\u003C\u002Ftr\u003E\u003C\u002Ftbody\u003E\u003C\u002Ftable\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EVAPIX API changes:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EPTZ VAPIX API version 2\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ESince AXIS OS 11.0, there is a new version of the PTZ VAPIX API. For more information, visit the \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fvapix-library\"\u003EVAPIX library\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoval of date.cgi\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ESince AXIS OS 11.0, the date.cgi has been removed and replaced by time.cgi. For more information, visit the \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fvapix-library\"\u003EVAPIX library\u003C\u002Fa\u003El \u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E It is obsolete, and keeping it might be a security threat. \u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this API, it will not work correctly with AXIS OS 11.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ESupport removed for BMP format\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ESince AXIS OS 11.0, support to request an image in BMP file format has been removed. For more information, visit the \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fvapix-library\"\u003EVAPIX library\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E It is obsolete, and keeping it might be a security threat. \u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this feature, it will not work correctly with AXIS OS 11.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoved support of recording mediaclip through Mediaclip AP\u003C\u002Fspan\u003E\u003C\u002Fspan\u003EI\u003C\u002Fp\u003E\u003Cp\u003ESince AXIS OS 11.0, support to record a mediaclip using the Mediaclip API has been removed. For more information, visit the \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fvapix-library\"\u003EVAPIX library\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E It is obsolete, and keeping it might be a security threat. \u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this feature, it will not work correctly with AXIS OS 11.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EParameters in the root.PTZ parameter group changes\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ESince AXIS OS 11.0, changed access for a number of parameters in the root.PTZ parameter group. For more information, visit the \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fvapix-library\"\u003EVAPIX library\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E Due to architectural changes. \u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this, it will not work correctly with AXIS OS 11.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoval of edit.cgi\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ESince AXIS OS 11.1, the edit.cgi has been removed. For more information, visit the \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fvapix-library\"\u003EVAPIX library\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E It is obsolete, and keeping it might be a security threat. \u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this API, it will not work correctly with AXIS OS 11.1 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoval of libvidcap\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe libvidcap has been removed. Use Video capture API instead. For more information, visit the \u003Ca class=\"link\" href=\"https:\u002F\u002Fhelp.axis.com\u002Facap-3-developer-guide#video-capture-api\"\u003EACAP developer guide\u003C\u002Fa\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E It is obsolete, and keeping it might be a security threat. \u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this API, it will not work correctly with AXIS OS 11.1 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoval of overlay-cgi.\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe overlay-cgi has been removed in AXIS OS 11.10. It is recommended to use overlayimage-cgi instead, see more info in the \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fvapix-library\u002F\"\u003EVAPIX Library\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003Cp\u003EVAPIX API parameter affected:\u003Cbr\u003E\u003Cspan style=\"font-style: italic;\"\u003Ecall_overlay_upload.cgi\u003Cbr\u003Ecall_overlay_del.cgi\u003Cbr\u003Ecall_overlay_set.cgi\u003Cbr\u003Ecreate_overlay.cgi\u003Cbr\u003Eoverlay_list.cgi\u003Cbr\u003Eoverlay_image_formats.cgi\u003C\u002Fspan\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E It is obsolete and replaced by a different API.\u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this API, it will not work correctly with AXIS OS 12.0 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EOther changes: \u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoval of the built in motion detection\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EIn AXIS OS 11.2 the old built in motion detection, also known as VMD1, was removed.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy is this change introduced?\u003C\u002Fspan\u003E It is obsolete, and keeping it might be a security threat. \u003Cbr\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can it affect me?\u003C\u002Fspan\u003E If you have third party software using this application, it will not work correctly with AXIS OS 11.2 or higher.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoved installable decoder AAC\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ESince AXIS OS 11.0, the installable audio decoder for AAC has been removed and is no longer downloadable from the cameras web interface.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003Cspan style=\"text-decoration: underline;\"\u003ERemoved installable decoder H.264\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ESince AXIS OS 11.0, the installable decoder for H.264 has been removed and is no longer downloadable from the cameras web interface.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E",title:"Changes in AXIS OS 11",urlAlias:"changes-in-axis-os-11",toc:a}]}]},{id:"t10161722",body:"\u003Cp\u003EPlease note that this schedule is preliminary and that both time schedule and included features are subject to change as work progresses.\u003C\u002Fp\u003E\u003Cp\u003EFor the Developer News articles, visit the \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fdeveloper-community\u002Fnews\"\u003EDeveloper Community\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EAXIS OS 12.4\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EScheduled for: April 2025\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EFeatures for all products\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cli class=\"knowledge-list-item-skip knowledge-list-item-sublist\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EAdded support to set custom headers for HTTP-based video streaming cgi.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Fli\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003ECybersecurity updates\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cli class=\"knowledge-list-item-skip knowledge-list-item-sublist\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EAdded support for Crypto-Policy setting to chose between standard OpenSSL cipher suite or FIPS 140-2 cipher suites. The Crypto-Policy setting can be adjusted from the Security tab in the web-interface or through VAPIX API.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EAdded support for OAuth 2.0 RFC6749 Client Credential Flow for token-based machine-to-machine communication that provides better overall security as traditional digest\u002Fbasic authentication schemes.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Fli\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EProduct specific features and changes\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cli class=\"knowledge-list-item-skip knowledge-list-item-sublist\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EZipstream storage profiles for AV1 format now support B-frames, allowing for more efficient video compression. \u003Cbr\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EApplies to\u003C\u002Fspan\u003E: All products based on \u003Ca class=\"link\" href=\"https:\u002F\u002Fhelp.axis.com\u002Faxis-os-release-notes#artpec-9\"\u003EAXIS ARTPEC-9\u003C\u002Fa\u003E\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EHardware modifications have been made to proactively prepare for the new NDAA 23 regulations that will be required in 2028. You will find more information about NDDA Compliance on \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fen-us\u002Fsolutions\u002Fgovernment\u002Fcompliance#ndaa-compliance\"\u003Eaxis.com\u003C\u002Fa\u003E. In AXIS OS knowledge base, you will find more about the \u003Ca class=\"link\" href=\"https:\u002F\u002Fhelp.axis.com\u002Faxis-os-knowledge-base#hardware-changes\"\u003Ehardware changes\u003C\u002Fa\u003E. The hardware ID can be found in Plain config > Properties > System > Hardware ID.\u003C\u002Fp\u003E\u003Cli class=\"knowledge-list-item-skip knowledge-list-item-sublist\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EProducts with Hardware ID A1D and A1E only support active track 12.4.XX and later, as well as coming LTS 2024 11.11 version and LTS 2022 10.12 version, and later. \u003Cbr\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EApplies to\u003C\u002Fspan\u003E: \u003Cspan class=\"keep\"\u003EAXIS M7116\u003C\u002Fspan\u003E and \u003Cspan class=\"keep\"\u003EAXIS P7316\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Fli\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Fli\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E",title:"Next AXIS OS version",urlAlias:"next-axis-os-version",toc:a},{id:"t10171198",body:"\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EAXIS OS 12.3\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ERelease date: February-March 2025\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EFeatures for all products\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cli class=\"knowledge-list-item-skip knowledge-list-item-sublist\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EAdded Time API to Device Configuration API, as beta.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EUpdated the Certificate, Firewall, SNMP, and LLDP APIs in the Device Configuration API to remove the beta designation, indicating they are now stable and ready for production use.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EIPv6 support is now enabled by default, which includes IPv6 Link-Local Address, DHCPv6, and Router Advertisement capabilities.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Fli\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003ECybersecurity updates\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cli class=\"knowledge-list-item-skip knowledge-list-item-sublist\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EUpdated cURL to version 8.11.0, addressing \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.cve.org\u002FCVERecord?id=CVE-2024-9681\"\u003ECVE-2024-9681\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EUpdated cURL to version 8.11.1 to increase overall cybersecurity level.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Fli\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EAnalytics updates\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cli class=\"knowledge-list-item-skip knowledge-list-item-sublist\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EAXIS Object Analytics: \u003Cbr\u003EAdded the ability to copy the scenario ID in the web interface.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EAXIS Scene Metadata: \u003Cbr\u003EReduced the frequency of sending empty frames from Analytics Scene Description. If no objects are detected in the scene, an empty frame is now sent every other second (instead of approximately 10 times per second). This change affects both the ONVIF producer 'Analytics Scene Description' and the message broker topic 'com.axis.analytics_scene_description.v0.beta'.\u003Cbr\u003EApplies to: All products with AXIS Scene Metadata support.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Fli\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EProduct specific features and changes\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cli class=\"knowledge-list-item-skip knowledge-list-item-sublist\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EHardware modifications have been made to proactively prepare for the new NDAA 23 regulations that will be required in 2028. You will find more information about NDDA Compliance on \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fen-us\u002Fsolutions\u002Fgovernment\u002Fcompliance#ndaa-compliance\"\u003Eaxis.com\u003C\u002Fa\u003E. In AXIS OS knowledge base, you will find more about the \u003Ca class=\"link\" href=\"https:\u002F\u002Fhelp.axis.com\u002Faxis-os-knowledge-base#hardware-changes\"\u003Ehardware changes\u003C\u002Fa\u003E. The hardware ID can be found in Plain config > Properties > System > Hardware ID.\u003C\u002Fp\u003E\u003Cli class=\"knowledge-list-item-skip knowledge-list-item-sublist\"\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EProducts with Hardware ID A16, A17 and A18 only support active track 12.3.XX and later, as well as coming LTS 2024 11.11 version and LTS 2022 10.12 version, and later. \u003Cbr\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EApplies to\u003C\u002Fspan\u003E: \u003Cspan class=\"keep\"\u003EAXIS M5074\u003C\u002Fspan\u003E, \u003Cspan class=\"keep\"\u003EAXIS M5075\u003C\u002Fspan\u003E and \u003Cspan class=\"keep\"\u003EAXIS M5075-G\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Fli\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EAXIS Image Health Analytics is added as pre-installed application. \u003Cbr\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EApplies to\u003C\u002Fspan\u003E: AXIS Q1686-DLE\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EAdd unknown object filter which hides all tracks that are not classified as \"human\" or \"vehicle\"\u003Cbr\u003E\u003Cspan style=\"text-decoration: underline;\"\u003EApplies to\u003C\u002Fspan\u003E: AXIS D2110-VE, AXIS D2210-VE, AXIS Q1656-DLE and AXIS Q1686-DLE\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003C\u002Fli\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E",title:"Current AXIS OS version",urlAlias:"current-axis-os-version",toc:a},{id:"t10194525",body:"\u003Cp\u003EAXIS OS-based network products use a variety of open source libraries. Therefore, it is critical that changes to these libraries are reflected in AXIS OS. Libraries are updated in the AXIS OS Active and LTS tracks in conjunction with the release. If there are no software restrictions, they are also updated in the PSS track.\u003C\u002Fp\u003E\u003Cp\u003EIf an open source library becomes end-of-life (EOL) by the upstream community, Axis aims to replace the library in a timely manner or provide support in a different way depending on its use within the AXIS OS-based network product. An example is listed below.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EOpenSSL\u003C\u002Fspan\u003E is used for cryptographic operations. The currently used OpenSSL 1.1.1 version is a long-term support (LTS) release which has reached its \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.openssl.org\u002Fblog\u002Fblog\u002F2023\u002F03\u002F28\u002F1.1.1-EOL\u002F\"\u003EEOL during September 2023\u003C\u002Fa\u003E as announced by the OpenSSL foundation.\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EFrom AXIS OS 11.6.89 and onwards, the newest OpenSSL 3.0 library (LTS) is supported in addition to the current OpenSSL 1.1.1, which will be deprecated but still usable.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EAxis plans to remove OpenSSL 1.1.1 support in AXIS OS 12 after LTS 2024.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003ETo support AXIS OS LTS tracks, Axis has a support contract agreement with the OpenSSL foundation for continued patching of OpenSSL 1.1.1.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cspan style=\"text-decoration: underline;\"\u003E\u003Cspan style=\"font-weight: bold;\"\u003EACAP related information\u003C\u002Fspan\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EStarting from ACAP SDK version 4.14, we're integrating the latest openSSL Version 3 into the Native ACAP SDK. \u003Cbr\u003EPlease read more in the \u003Ca class=\"link\" href=\"https:\u002F\u002Faxiscommunications.github.io\u002Facap-documentation\u002Fdocs\u002Frelease-notes\u002F4.14.html\"\u003Erelease notes\u003C\u002Fa\u003E and explore API examples on \u003Ca class=\"link\" href=\"https:\u002F\u002Fgithub.com\u002FAxisCommunications\u002Facap-native-sdk-examples\u002Ftree\u002Fmain\u002Fcurl-openssl\"\u003EGitHub\u003C\u002Fa\u003E for details.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhat needs to be done:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EIf any Axis-owned ACAP relies on the OpenSSL 1.1.1 runtime dependency provided by the platform, it requires refactoring and rebuilding with OpenSSL 3 libraries. We recommend utilizing the latest ACAP SDK (4.14) to ensure compatibility with the correct library version.\u003C\u002Fp\u003E",title:"Open source library support",urlAlias:"open-source-library-support",toc:a},{id:"t10186723",body:"\u003Cp\u003EA Software Bill of Materials (SBOM) is an inventory of all components included in the software. It has become an increasingly important and common part of software development lifecycle and processes. It allows IT Operations and Security staff to determine which third-party or open-source software is packaged with your software. Having an SBOM is important when it comes to securing your IT systems and protecting user data. \u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy do Axis publish an SBOM?\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EAxis works actively with the principles of openness and building trust through transparency, the SBOM is a valued addition to these principles. It provides our customers with the information necessary to know whether or not the products we have provided may be vulnerable to cyber attacks.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EFor which AXIS OS versions?\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EAxis will provide an SBOM for all AXIS OS releases on active track starting with release 11.2.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhat is included?\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe Axis SBOM contains information about Axis-Proprietary components and Opensource software used to assemble AXIS OS.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhat is excluded and why?\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EInitially, due to current licensing and technical limitations we cannot provide information about third-party proprietary software and Axis-proprietary components with dependencies. In addition to this some of the packages in the software consist of pre-compiled bundles such as our web interface and ACAPS, which have not in their turn provided an SBOM. Over time our aim is to cover all the third-party components and as much of the Axis-proprietary components as legally possible.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhere can I find the SBOM?\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe SBOM is located together with the AXIS OS version it is based on. AXIS OS can be found in the product support or at the \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fsupport\u002Ffirmware\"\u003Edownload page\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhat format and why?\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe Axis SBOM is produced in accordance with the CycloneDX SBOM specification. This format seems to be the most usable in other systems and strives to be a minimalist format easy to work with. Advantages of this format can be found \u003Ca class=\"link\" href=\"https:\u002F\u002Fcyclonedx.org\u002Fabout\u002Fguiding-principles\"\u003Ehere\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhat is the difference between a SBOM and the Third party software licenses document?\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe Third party software licenses document is meant to list all legal agreements and licenses with third parties related to any intellectual property that allows us to use, market and incorporate this into our products.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhat about SBOM for other AXIS software?\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThis is a start, and we are looking into how SBOM is applicable to other software from Axis.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhere can I find more information about SBOM in general?\u003C\u002Fspan\u003E \u003C\u002Fp\u003E\u003Cp\u003EThe \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.ntia.gov\"\u003ENational Telecommunications and Information Administration\u003C\u002Fa\u003E provides more educational information about SBOM.\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.ntia.gov\u002Ffiles\u002Fntia\u002Fpublications\u002Fframingsbom_20191112.pdf\"\u003EFraming Software Component Transparency: Establishing a Common Software Bill of Material (SBOM)\u003C\u002Fa\u003E\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.ntia.gov\u002Ffiles\u002Fntia\u002Fpublications\u002Fsbom_faq_-_20201116.pdf\"\u003ESoftware Bill of Material FAQ\u003C\u002Fa\u003E\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow can I use the SBOM to analyze the software?\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe Axis SBOM contains information about Axis-Proprietary and Opensource software used to assemble AXIS OS. The Axis SBOM can be used by third party vulnerability scanners to highlight known vulnerabilities in software packages. A vulnerability that applies to a certain module or feature in a software package needs to be loaded and used by the Axis device. Vulnerabilities in modules that are not loaded are not relevant but may still be flagged by the vulnerability scanner or SBOM information. For more information on how to work with the result of a security scanner see: \u003Ca class=\"link\" href=\"https:\u002F\u002Fhelp.axis.com\u002Faxis-os-vulnerability-scanner-guide\"\u003EAXIS OS Vulnerability Scanner Guide\u003C\u002Fa\u003E.\u003C\u002Fp\u003E",title:"Software Bill of Materials",urlAlias:"software-bill-of-materials",toc:a},{id:"t10139395",body:"\u003Cp\u003EAXIS OS supplies three types of tracks: \u003Cspan style=\"font-weight: bold;\"\u003Eactive\u003C\u002Fspan\u003E, \u003Cspan style=\"font-weight: bold;\"\u003Elong-term support (LTS)\u003C\u002Fspan\u003E and \u003Cspan style=\"font-weight: bold;\"\u003Eproduct-specific support (PSS)\u003C\u002Fspan\u003E track. \u003C\u002Fp\u003E\u003Cp\u003EIn the active track, we consistently add new features while also improving cybersecurity. In LTS, we refrain from introducing new features, prioritizing to maintain cybersecurity and ensuring compatibility. PSS will receive updates less frequently compared to our other two tracks, but we remain committed to addressing bug corrections and upholding cybersecurity measures.\u003C\u002Fp\u003E\u003Cimg alt=\"\" height=\"468\" src=\"\u002Fimage\u002Ft10216382.png\" width=\"676\"\u003E\u003Cp\u003E\u003C\u002Fp\u003E\u003Cp\u003EThere's a \u003Ca class=\"link\" href=\"https:\u002F\u002Fyoutu.be\u002FsAyciMeHOMU?si=x6nUpwwFy7FjqNiH\"\u003EYouTube video\u003C\u002Fa\u003E that explains the AXIS OS lifecycle in more detail. It covers our different tracks, version management and upgrade recommendations.\u003C\u002Fp\u003E",title:"AXIS OS lifecycle management",urlAlias:"axis-os-lifecycle",toc:a,sections:[{id:"t10139394",body:"\u003Cp\u003EThe most updated and feature progressive track of AXIS OS, that is suitable for customers who want access to the newest features and improvements. New products are launched on this track, which means the most immediate access to any new features and updates.\u003C\u002Fp\u003E\u003Cimg alt=\"\" height=\"467\" src=\"\u002Fimage\u002Ft10184574.png\" width=\"1208\"\u003E",title:"Active track",urlAlias:"active-track",toc:a},{id:"t10139393",body:"\u003Cp\u003EThe focus of the long-term support (LTS) track is to keep the products well integrated with third-party equipment or software, and still get necessary bug fixes and cybersecurity updates. An LTS track has a fixed feature set and a new track is created every two years and maintained for 5 years. No new products or features are added to the LTS track.\u003C\u002Fp\u003E",title:"Long-term support track",urlAlias:"lts-track",toc:a},{id:"t10203002",body:"\u003Cp\u003EProduct-specific support (PSS), is a rare track used when a product needs support after an LTS track has expired. The products on this track will still receive necessary bug fixes and cybersecurity updates. Each product is on its own track, the tracks are not connected with one another. Also, other non-Axis OS products have similar support tracks. \u003C\u002Fp\u003E\u003Cimg alt=\"\" height=\"1864\" src=\"\u002Fimage\u002Ft10205720.png\" width=\"4023\"\u003E",title:"Product-specific support",urlAlias:"pss",toc:a},{id:"t10220344",body:"\u003Cp\u003E\u003C\u002Fp\u003E\u003Cp\u003EBelow is a list of system characteristics and goals to help you choose the right track.\u003C\u002Fp\u003E\u003Cdl class=\"dl-horizontal\"\u003E\u003Cdt\u003EHighest level of cybersecurity\u003C\u002Fdt\u003E\u003Cdd\u003E\u003Cspan style=\"font-weight: bold;\"\u003EAXIS OS active\u003Cbr\u003E\u003C\u002Fspan\u003EAXIS OS active track provides security patches and the latest enhancements including security.\u003C\u002Fdd\u003E\u003Cdt\u003ENeed for specific new features\u003C\u002Fdt\u003E\u003Cdd\u003E\u003Cspan style=\"font-weight: bold;\"\u003EAXIS OS active\u003C\u002Fspan\u003E\u003Cbr\u003EAXIS OS active track offers the latest features. In some areas, such as analytics, the gap between Active, LTS and newer products may be greater.\u003C\u002Fdd\u003E\u003Cdt\u003ESatisfied with current features and cybersecurity level\u003C\u002Fdt\u003E\u003Cdd\u003E\u003Cspan style=\"font-weight: bold;\"\u003EAXIS OS LTS\u003C\u002Fspan\u003E\u003Cbr\u003ELTS tracks has focus on compatibility and adding new cyber security patches. AXIS OS LTS track do not introduce new features or breaking changes.\u003C\u002Fdd\u003E\u003Cdt\u003EExtensive internal verification process when accepting new software updates\u003C\u002Fdt\u003E\u003Cdd\u003E\u003Cspan style=\"font-weight: bold;\"\u003EAXIS OS LTS\u003Cbr\u003E\u003C\u002Fspan\u003EUpdates within the same AXIS OS LTS track shouldn’t require recertification. If validating new releases is costly or time-consuming, the AXIS OS LTS track is recommended.\u003C\u002Fdd\u003E\u003Cdt\u003EExisting processes involve frequent updates of VMS and system components.\u003C\u002Fdt\u003E\u003Cdd\u003E\u003Cspan style=\"font-weight: bold;\"\u003EAXIS OS active or AXIS OS LTS\u003Cbr\u003E\u003C\u002Fspan\u003EBoth AXIS OS Active and LTS track may be used. Each new Axis release is validated with Milestone, Genetec and AXIS Camera Station. \u003Cbr\u003EMake sure your VMS is validated before upgrading.\u003C\u002Fdd\u003E\u003Cdt\u003ECurrent processes lack frequent updates for VMS and system components\u003C\u002Fdt\u003E\u003Cdd\u003E\u003Cspan style=\"font-weight: bold;\"\u003EAXIS OS LTS\u003Cbr\u003E\u003C\u002Fspan\u003EVerify with your VMS and ACAP provider which versions they test and recommend. AXIS OS LTS is the recommended choice for optimal compatibility.\u003C\u002Fdd\u003E\u003C\u002Fdl\u003E\u003Cp\u003E\u003C\u002Fp\u003E",title:"Suggested track",urlAlias:"suggested-track",toc:a},{id:"t10218226",body:"\u003Cp\u003E\u003Cbr\u003EYou can upgrade your devices using the web interface or various device management tools, such as AXIS Device Manager, AXIS Camera Station Pro, and AXIS Camera Station Edge. AXIS Device Management Extend simplifies the upgrade process by providing built-in backend upgrade paths. Read more about \u003Ca class=\"link\" href=\"https:\u002F\u002Fhelp.axis.com\u002Faxis-os-knowledge-base#how-to-upgrade\"\u003EHow to upgrade\u003C\u002Fa\u003E in AXIS OS Knowledge base.\u003C\u002Fp\u003E\u003Cp\u003EHere are some recommendations for how to upgrading:\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EUpgrading from an older active track to the latest active\u003C\u002Fspan\u003E: Upgrade to the latest version of the intermediate LTS.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"392\" src=\"\u002Fimage\u002Ft10218216.png\" style=\"vertical-align:middle;\" width=\"639\"\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EUpgrading from the latest LTS track to the active track\u003C\u002Fspan\u003E: Start by upgrading to the latest version of your current LTS.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"292\" src=\"\u002Fimage\u002Ft10218214.png\" style=\"vertical-align:middle;\" width=\"521\"\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EUpgrading from an older LTS to the next LTS version\u003C\u002Fspan\u003E: First, update to the latest version of your current LTS\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"293\" src=\"\u002Fimage\u002Ft10218213.png\" style=\"vertical-align:middle;\" width=\"753\"\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EUpgrading from an older LTS to two newer LTS versions\u003C\u002Fspan\u003E: Upgrade to the intermediate LTS version first.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cimg alt=\"\" class=\"inline\" height=\"430\" src=\"\u002Fimage\u002Ft10218215.png\" style=\"vertical-align:middle;\" width=\"945\"\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EConsiderations\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EA new active track always means that something has changed. To move AXIS OS forward we deliberately introduce breaking changes to keep our software up-to-date due to cybersecurity and feature growth. When you upgrade to a newer track please keep in mind we may have introduced new features, changed the default settings, and performance enhancements can affect compatibility with your existing system. \u003C\u002Fp\u003E\u003Cp\u003EOver time, multiple LTS tracks become available for a product. Each LTS track is designed to provide long-term consistency by focusing on bug fixes without introducing new features. However, it's a good idea to upgrade to the latest LTS track. \u003C\u002Fp\u003E\u003Cp\u003ETherefore, product upgrades should be performed in a controlled and monitored manner to ensure that the version is performing as expected in your environment before proceeding. It is always recommended to have a group of devices that represent your inventory in a test environment and validate the upgrade before the actual installation. Grouping and and testing please read more here.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EStay current with AXIS OS upgrades\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EMaintaining a consistent upgrade strategy is essential for ensuring your Axis products benefit from ongoing enhancements. Axis Technical Services also advises upgrading to the latest version when addressing issues with an Axis product.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003ESelecting the right latest version\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EWith multiple upgrade options available, it’s important to choose the appropriate \"latest\" version. Here’s some guidance: \u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EFor Long-term support (LTS), we recommend to chose the newest LTS track if available for you product. \u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EOn any track (Active or LTS), we recommend upgrading to the latest available version.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli class=\"knowledge-list-item-skip knowledge-list-item-paragraph\"\u003EBy following this approach, you’ll keep your Axis products up-to-date with optimal performance and cybersecurity.\u003C\u002Fli\u003E\u003Cli class=\"knowledge-list-item-skip knowledge-list-item-paragraph\"\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003E\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EAdditional Q&A\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EIf my Axis product is running on the LTS 2022 (10.12) track, should I consider upgrading to the latest AXIS OS active track?\u003C\u002Fspan\u003E\u003Cbr\u003EIt depends on third-party dependencies and compatibility with the active track. Generally, we recommend remaining on the LTS 2022 (10.12) track and updating within that track as long as it's supported. If you need features only on the active track, upgrading might be worth considering.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EI would like to run my Axis product on an LTS track, but there is currently no LTS track available?\u003C\u002Fspan\u003E\u003Cbr\u003EIf your product was released between two LTS tracks, it’s recommended to keep it updated on the active track until a new LTS track is available. New LTS tracks are introduced every two years.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EIf there are multiple LTS tracks available, which LTS track should I choose?\u003C\u002Fspan\u003E\u003Cbr\u003EWe recommend using the latest LTS track supported by your third-party software. This ensures compatibility, reduces the need to switch tracks, and provides access to the latest cybersecurity updates and features.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhat should I do if my VMS states that it requires a specific version of the LTS track, such as version 9.80.3.2 on LTS 2020, but I cannot find it on axis.com?\u003C\u002Fspan\u003E\u003Cbr\u003EIf your VMS specifies a specific LTS version, it will also be compatible with subsequent releases within that track. VMS systems typically list one version because it was certified with it, but compatibility remains consistent within each LTS track. It’s generally safe to use other versions.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhen upgrading from an old LTS to a new LTS, is it necessary to upgrade to the intermediate versions?\u003C\u002Fspan\u003E\u003Cbr\u003ETo preserve settings, we recommend upgrading in incremental steps. If resetting the device to factory defaults, however, intermediate versions are not necessary.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003C\u002Fp\u003E",title:"Upgrade path",urlAlias:"upgrade-path",toc:a},{id:"t10220343",body:"\u003Cp\u003EFollow the below recommendations to optimize AXIS OS performance, ensure cybersecurity, and simplify updates and lifecycle management.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EAlways use the latest supported AXIS OS version:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EAlways run the latest version within your selected AXIS OS track.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EEnsure that all models in your system are running the same AXIS OS version, if possible. \u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EIf you have products with different HWIDs for the same model, make sure you are still running the same version, see \u003Ca class=\"link\" href=\"https:\u002F\u002Fhelp.axis.com\u002Faxis-os-knowledge-base#hardware-changes\"\u003EHardware Changes\u003C\u002Fa\u003E in the AXIS OS Knowledge Base.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EIf AXIS OS LTS track is preferred, choose the latest available LTS version for each product.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EThe LTS track provides robust cybersecurity measures and allows time to plan for upgrading to a newer LTS track when needed.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003ESimplify software updates and lifecycle planning using device management tools:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EE.g. \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fsupport\u002Ftools\u002Faxis-device-manager\"\u003EAXIS Device Manager\u003C\u002Fa\u003E and \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fproducts\u002Faxis-device-manager-extend\"\u003EAXIS Device Manager Extend\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EPlan for device replacement before software reaches end-of-support.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EStay up-to-date on cybersecurity recommendations:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003ESubscribe to \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fsupport\u002Fcybersecurity\u002Fsecurity-notification-service\"\u003Ecybersecurity notifications\u003C\u002Fa\u003E for the latest updates. \u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EApply recommendations from \u003Ca class=\"link\" href=\"https:\u002F\u002Fhelp.axis.com\u002Faxis-os-hardening-guide\"\u003EAXIS OS hardening guide\u003C\u002Fa\u003E to secure your devices. \u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EUse network security scanners (e.g., Tenable, Rapid7) to identify potential vulnerabilities.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EUpgrading between AXIS OS LTS tracks:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EIf you are changing AXIS OS tracks (LTS or active), please read the \u003Ca class=\"anchor link\" data-anchor=\"upgrade-path\" href=\"#upgrade-path\"\u003EUpgrade path\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003ERead the\u003Ca class=\"link\" href=\"https:\u002F\u002Fhelp.axis.com\u002Faxis-os-release-notes\"\u003E release notes\u003C\u002Fa\u003E, changes has been done between the different tracks. \u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EVerification of new releases:\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EWhen updating within the same AXIS OS LTS track additional certification or compatibility testing is usually not required.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EFor large systems using AXIS OS active track, it's recommended to pre-test new releases in a staging environment before deploying them to production. This ensures a smooth transition and minimizes potential disruptions.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003ETo stay ahead of the curve, take advantage of \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fdeveloper-community\u002Faxis-os-beta-releases\"\u003EAXIS OS active track beta releases\u003C\u002Fa\u003E to test upcoming features and enhancements in your staging environment prior to the official release.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EAxis verifies all new AXIS OS releases against the latest versions of AXIS Camera Station, Genetec and Milestone. If you are using older VMS versions or VMS solutions from other vendors, we recommend pre-validating new AXIS OS active track releases to ensure compatibility. \u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EEnsure that all components in the system supports the new version before changing LTS tracks or major versions on AXIS OS Active track.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003C\u002Fp\u003E",title:"General recommendations",urlAlias:"general-recommendations",toc:a},{id:"t10185211",body:"\u003Cp\u003EWhich AXIS OS tracks are available for an Axis edge device can be obtained when downloading AXIS OS from the \u003Cspan class=\"keep\"\u003E\u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fsupport\u002Ffirmware\"\u003Edownload page\u003C\u002Fa\u003E.\u003C\u002Fspan\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003Cp\u003EAXIS OS can also be found on the product support page for each product, where you can find all available supported versions and some older. Older unsupported versions will periodically be removed due to known bugs and cybersecurity vulnerabilities that are corrected in later releases. It is recommend to only AXIS OS versions that are supported.\u003C\u002Fp\u003E\u003Cimg alt=\"\" height=\"529\" src=\"\u002Fimage\u002Ft10210543.png\" width=\"1200\"\u003E\u003Cp\u003E\u003Cbr\u003E\u003C\u002Fp\u003E\u003Cp\u003EPlease see below a list of common tags that indicate different AXIS OS tracks as seen in the picture above.\u003C\u002Fp\u003E\u003Ctable class=\"knowledge-table table table-bordered\"\u003E\u003Ctbody\u003E\u003Ctr class=\"knowledge-table-row\"\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan style=\"font-weight: bold;\"\u003ETag example\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan style=\"font-weight: bold;\"\u003EExplanation\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003C\u002Ftr\u003E\u003Ctr class=\"knowledge-table-row\"\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan class=\"keep\"\u003E12.1.64 - AXIS OS active\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cp\u003EAXIS OS active track providing new features, security and other improvements.\u003C\u002Fp\u003E\u003C\u002Ftd\u003E\u003C\u002Ftr\u003E\u003Ctr class=\"knowledge-table-row\"\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan class=\"keep\"\u003E11.11.124 - AXIS OS LTS 2024\u003C\u002Fspan\u003E\u003Cbr\u003E\u003Cspan class=\"keep\"\u003E10.12.262 - AXIS OS LTS 2022\u003C\u002Fspan\u003E\u003Cbr\u003E\u003Cspan class=\"keep\"\u003E9.80.66 - AXIS OS LTS 2020\u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cp\u003EAXIS OS long-term support track (LTS) providing security and maintain compatibility.\u003C\u002Fp\u003E\u003C\u002Ftd\u003E\u003C\u002Ftr\u003E\u003Ctr class=\"knowledge-table-row\"\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cspan class=\"keep\"\u003E8.40.59 - PSS\u003C\u002Fspan\u003E\u003Cbr\u003E\u003Cspan class=\"keep\"\u003E6.50.5.19 - PSS\u003C\u002Fspan\u003E\u003Cbr\u003E\u003Cspan class=\"keep\"\u003E5.51.4.7 \u003C\u002Fspan\u003E\u003C\u002Ftd\u003E\u003Ctd class=\"knowledge-table-cell\"\u003E\u003Cp\u003EWith and without PSS tag. Product-specific support (PSS) track.\u003C\u002Fp\u003E\u003C\u002Ftd\u003E\u003C\u002Ftr\u003E\u003C\u002Ftbody\u003E\u003C\u002Ftable\u003E",title:"Downloading AXIS OS",urlAlias:"downloading-axis-os",toc:a},{id:"t10185297",body:"\u003Cp\u003EAXIS OS releases are denoted by a unique number combination. Older releases where named by the year and type of the release but since release 10.10 we changed the versioning. The differences and the significance of each number is explained in the figures below. \u003C\u002Fp\u003E\u003Cp\u003EIn some cases, you may also notice an additional number at the end. This version builds on the main AXIS OS release with additional features, such as AXIS Access Control products.\u003C\u002Fp\u003E\u003Cimg alt=\"\" height=\"336\" src=\"\u002Fimage\u002Ft10200176.png\" width=\"471\"\u003E\u003Cp\u003E\u003C\u002Fp\u003E\u003Cul class=\"knowledge-list knowledge-list-bullets\"\u003E\u003Cli\u003E\u003Cp\u003EThe major version is incremented after a new active track has been created. This happens every two years when the active track becomes an LTS track.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EThe minor version is indicating what feature set is included and updated with each feature release approximately 6 times per year.\u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003Cli\u003E\u003Cp\u003EThe patch number is increased more often, it’s used for adding patches and bugfixes, and only final versions will be available to customers. This means that this number is only a number to mirror the external version with the internal version. \u003C\u002Fp\u003E\u003C\u002Fli\u003E\u003C\u002Ful\u003E\u003Cp\u003E\u003C\u002Fp\u003E\u003Cp\u003EPrevious versioning .\u003C\u002Fp\u003E\u003Cimg alt=\"\" height=\"311\" src=\"\u002Fimage\u002Ft10184576.png\" width=\"406\"\u003E\u003Cp\u003E\u003C\u002Fp\u003E",title:"AXIS OS versioning",urlAlias:"axis-os-versioning",toc:a},{id:"t10186857",body:"\u003Cp\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhen a product has an AXIS OS support date, what does that mean?\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe product will be supported during this period with bug fixes as well as critical security updates, and with focus on compatibility and consistency.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhat is required to get the full support period?\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ETo benefit from the full support period of AXIS OS, the device must be upgraded to the latest active, LTS or PSS version. For more information on upgrade strategies, see \u003Ca class=\"anchor link\" data-anchor=\"upgrade-path\" href=\"#upgrade-path\"\u003EUpgrade path\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EHow long can I expect to get AXIS OS support for my product?\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EAxis generally provides 5 years of Axis OS support from the product's discontinuation date. This policy was introduced in 2016, ensuring that our customers receive extended support for their devices. To view the exact support date for your product, please visit the product's support page.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy do some products display only the date for Hardware support and not AXIS OS support, or vice versa?\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EThe dates displayed depend on investigated information and the product's lifecycle stage. For older products, no dates may be shown, while in other cases, two different dates might be displayed. If the product has a defined end-of-support date for hardware and AXIS OS, both dates will be shown.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhat accounts for the diverse end-of-software support dates across different products?\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EEach product's end of software support date is determined based on its unique hardware characteristics, including system-on-chip (SoC) type, memory capacity, and market segment. \u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhy do some products lack an AXIS OS support date?\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ESome products are not included in the development of AXIS OS, and therefore some old products have no software support dates. However, dates will be available for more products in the Axis portfolio over time. For further questions, please contact \u003Ca class=\"link\" href=\"https:\u002F\u002Fwww.axis.com\u002Fsupport\u002Fhelpdesk\"\u003EAxis Technical Support Helpdesk\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhat happens once the AXIS OS support has expired for a product?\u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003ENo further updates, improvements or security patches will be released. There are limits to how long we can maintain software currency and implement changes to an older version. Modifying software that is limited by hardware resources becomes increasingly challenging and complicated over time. Eventually, we reach a stage where it is no longer possible to guarantee the cybersecurity of the product. This signals that it is time to replace the device.\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EWhere can I find further information on the current forecast for AXIS OS, upcoming changes and which tracks are currently supported? \u003C\u002Fspan\u003E\u003C\u002Fp\u003E\u003Cp\u003EPlease follow and monitor the \u003Ca class=\"anchor link\" data-anchor=\"release-schedule\" href=\"#release-schedule\"\u003ERelease schedule\u003C\u002Fa\u003E.\u003C\u002Fp\u003E\u003Cp\u003E\u003C\u002Fp\u003E\u003Cp\u003E\u003Cspan style=\"font-weight: bold;\"\u003EExample of AXIS OS Support: \u003C\u002Fspan\u003E\u003Cbr\u003EThroughout its product lifecycle, the AXIS Q1656-LE will continue to receive new features, increased cybersecurity, improvements and security updates until 2028. Between 2028 and the end of 2033, it will receive some improvements along with all security updates through LTS 2028, with a focus on compatibility.\u003C\u002Fp\u003E\u003Cimg alt=\"\" height=\"839\" src=\"\u002Fimage\u002Ft10187162.png\" width=\"1891\"\u003E",title:"AXIS OS Support",urlAlias:"axis-os-maintenance",toc:a}]}];d.images=["t10208092.png","t10146754.png",i,"t10198465.png","t10204638.png","t10198463.png","t10198464.png","t10207682.png",j,"t10209761.png","t10198469.png","t10205440.png","t10205441.png","t10198467.png",j,"t10207646.png","t10198468.png",i,"t10213399.png","t10198460.png","t10208091.png","t10208090.png","t10207645.png","t10207661.png","t10198582.png","t10184574.png","t10205720.png","t10218216.png","t10218214.png","t10218213.png","t10218215.png","t10210543.png","t10200176.png","t10184576.png","t10187162.png","t10216382.png"];d.pdf="release_notes_os_t10202650_2503.pdf";return {layout:"manual",data:[{hideComponents:b,hidePdf:b,manual:d,relativePath:b}],fetch:{},error:c,state:{copied:{isActive:b},leftDrawer:{isActive:b},mobileSearchDrawer:{isActive:b},redirectInfo:{requested:c,recieved:c},scrollWarning:{isActive:b},categories:{categories:[]},intersection:{current:{}},manual:{documentType:k,id:e,manual:d,sections:[],searchString:k,title:g,toc:[],imageConvert:b},manuals:{manuals:[]},i18n:{routeParams:{}}},serverRendered:a,routePath:"\u002Fen-us\u002Faxis-os",config:{DOWNLOAD:"\u002Fdownload",axios:{browserBaseURL:"https:\u002F\u002Fhelp.axis.com"},_app:{basePath:"\u002F",assetsPath:"\u002F_nuxt\u002F",cdnURL:c}},__i18n:{langs:{"en-us":{All:"All",Axis:"Axis",Close:"Close",CookieSettings:"Cookie settings",Copyright:"{copy}{year} Axis Communications AB. All rights reserved.",Document:"Document|Documents",Download:"Download",Search:l,Translation:"Translation|Translations",WhitePaper:"White Paper|White Papers",backTo:"Go to",categories:{Analytics:"Analytics",Application:"Application","Audio management software":"Audio management software","Audio system devices":"Audio system devices","Audio/visual alerters":"Audio\u002Fvisual alerters","AXIS Camera Station":"AXIS Camera Station","AXIS Camera Station 5":"AXIS Camera Station 5","AXIS Camera Station Pro":"AXIS Camera Station Pro","AXIS Companion IP cameras":"AXIS Companion","AXIS OS":"AXIS OS","Accessory / Speaker":"Accessory\u002FSpeaker","Box cameras":"Box cameras","Bullet cameras":"Bullet cameras",Cybersecurity:"Cybersecurity","Dome cameras":"Dome cameras","Explosion-protected cameras":"Explosion-protected cameras","Explosion-protected speakers":"Explosion-protected speakers","Fixed box cameras":"Fixed box cameras","Fixed bullet cameras":"Fixed bullet cameras","Fixed Dome Network Camera":"Fixed Dome Network Camera","Fixed dome cameras":"Fixed dome cameras","Find and compare":"Find and compare",Guidelines:"Guidelines","I/O devices":"I\u002FO devices","Install and manage":"Install and manage",Integration:"Integration","Integration guide":"Integration guides","Joysticks and keypads":"Joysticks and keypads",Microphones:"Microphones","Modular cameras":"Modular cameras","Network camera":"Network camera","Network door controllers":"Network door controllers","Network I/O relay modules":"Network I\u002FO relay modules","Network intercoms":"Network intercoms","Network speakers":"Network speakers","Network video recorders":"Network video recorders","Onboard cameras":"Onboard cameras",Other:"Other","Paging microphones":"Paging @:microphone","Panoramic cameras":"Panoramic cameras","Plan and design":"Plan and design",Power:"Power","PTZ cameras":"PTZ cameras",Readers:"Readers","Release notes":"Release notes",Radars:"Radars",Software:"Softwares",Solution:"Solutions","System device":"System devices",Switches:"Switches","Thermal cameras":"Thermal cameras",Troubleshooting:"Troubleshooting","Video decoders":"Video decoders","Video encoders":"Video encoders","Video management software":"Video management software",Wearables:"Wearables",Workstations:"Workstations"},category:"Category|Categories",chooseLanguage:"Choose language",copySuccess:"Link copied to clipboard",couldNotFindScroll:"Could not find element on page",documentation:"documentation",findAManual:"Find a manual",hint:"Contens of the document",languages:{Czech:"Czech",German:"German","English (American)":"English (American)",Spanish:"Spanish",French:"French",Italian:"Italian",Japanese:"Japanese",Korean:"Korean",Dutch:"Dutch",Polish:"Polish","Portuguese (Brazilian)":"Portuguese (Brazilian)",Portuguese:"Portuguese",Russian:"Russian (Russia)","Russian (Kazakhstan)":"Russian (Kazakhstan)",Swedish:"Swedish","Chinese (Simplified)":"Chinese (Simplified)","Chinese (Traditional)":"Chinese (Traditional)"},legal:"Legal",libraries:"Libraries",microphone:"microphone|microphones",noResultsFound:"No results found",notFound:"404, we could not find the manual you are looking for.",privicyPolicy:"Privacy policy",search:l,supportPages:"Support pages",technical:"technical",userManual:"User manual|User manuals",AllWhitePapers:"@:(All) @:(WhitePaper)",AxisDocumentation:"@:(Axis) @:(documentation)",DownloadPdf:"@:(Download) PDF",TechnicalDocumentation:"@:(technical) @:(documentation)",backToDocuments:"@:(backTo) @:(AxisDocumentation)"}}}}}(true,false,null,{},"T10202650","en-us","AXIS OS Portal","\u003Cp\u003E\u003C\u002Fp\u003E","t10207644.png","t10207647.png","","Search"));</script><script src="/_nuxt/56ecfb3.js" defer></script><script src="/_nuxt/a0410e8.js" defer></script><script src="/_nuxt/0f2f0fe.js" defer></script><script src="/_nuxt/15149e8.js" defer></script><script src="/_nuxt/d93abf5.js" defer></script><script src="/_nuxt/0daeb4c.js" defer></script><script src="/_nuxt/767dc84.js" defer></script> <div id="AxisCCDiv"></div> <script src="https://www.axis.com/themes/custom/axiscom/cookie_consent/axiscookieconsent.js"></script> </body> </html>