{"id":54348,"date":"2019-12-24T00:00:00","date_gmt":"2019-12-23T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/vvedenie-v-arhitekturu-bezopasnosti-5g-nfv-klyuchi-i-2-autentifikatsii"},"modified":"2020-02-18T14:02:21","modified_gmt":"2020-02-18T11:02:21","slug":"vvedenie-v-arhitekturu-bezopasnosti-5g-nfv-klyuchi-i-2-autentifikatsii","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/vvedenie-v-arhitekturu-bezopasnosti-5g-nfv-klyuchi-i-2-autentifikatsii","title":{"rendered":"Introducere \u00een arhitectura de securitate 5G: NFV, chei \u0219i 2 autentific\u0103ri","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/481446\/\"><img decoding=\"async\" alt=\"Introducere \u00een arhitectura de securitate 5G: NFV, chei \u0219i 2 autentific\u0103ri\" src=\"\/wp-content\/uploads\/2019\/12\/731a83ddc08dfb8303c1dafb6ef0ef73.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p>Este evident c\u0103 a aborda dezvoltarea unui nou standard de comunicare f\u0103r\u0103 a lua \u00een considerare mecanismele de asigurare a securit\u0103\u021bii este o activitate extraordinar de \u00eendoielnic\u0103 \u0219i lipsit\u0103 de utilitate.<\/p>\n<p><u>Arhitectura de securitate 5G<\/u> \u2014 un ansamblu de mecanisme \u0219i proceduri de securitate implementate \u00een <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/5G\">re\u021belele de genera\u021bie a cincea<\/a><\/noindex> \u0219i care acoper\u0103 toate componentele re\u021belei, de la nucleu p\u00e2n\u0103 la interfe\u021bele radio. <\/p>\n<p>Re\u021belele de genera\u021bie a cincea sunt, \u00een esen\u021b\u0103, o evolu\u021bie a <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/4G\">re\u021belelor de genera\u021bie a patra LTE.<\/a><\/noindex>Cele mai semnificative modific\u0103ri au fost aduse tehnologiilor de acces radio. Pentru re\u021belele de genera\u021bie a cincea a fost dezvoltat\u0103 o nou\u0103 <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Radio_access_technology\">RAT<\/a><\/noindex> (Tehnologie de Acces Radio) \u2014 <noindex><a rel=\"nofollow\" href=\"https:\/\/www.riverpublishers.com\/journal\/journal_articles\/RP_Journal_2245-800X_614.pdf\">5G New Radio.<\/a><\/noindex>\u00cen ceea ce prive\u0219te nucleul re\u021belei, acesta a suferit modific\u0103ri mai pu\u021bin semnificative. \u00cen acest context, arhitectura de securitate a re\u021belelor 5G a fost conceput\u0103 av\u00e2nd \u00een vedere reutilizarea tehnologiilor corespunz\u0103toare, acceptate \u00een standardul 4G LTE.<\/p>\n<p>Cu toate acestea, merit\u0103 men\u021bionat c\u0103 reinterpretarea unor amenin\u021b\u0103ri bine cunoscute, cum ar fi atacurile asupra interfe\u021belor radio \u0219i nivelului de semnalizare (<noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Signaling_(telecommunications)\">signalling<\/a><\/noindex> plane), atacurile DDoS, atacurile Man-In-The-Middle \u0219i altele, a determinat operatorii de telecomunica\u021bii s\u0103 dezvolte noi standarde \u0219i s\u0103 integreze mecanisme de securitate complet noi \u00een re\u021belele de genera\u021bie a cincea. <br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\n<img decoding=\"async\" alt=\"Introducere \u00een arhitectura de securitate 5G: NFV, chei \u0219i 2 autentific\u0103ri\" src=\"\/wp-content\/uploads\/2019\/12\/c934556e832cb4ba4e3053cf36f6170a.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h1>Premise<\/h1>\n<p>\n\u00cen 2015, Uniunea Interna\u021bional\u0103 a Telecomunica\u021biilor a elaborat primul plan global de dezvoltare a re\u021belelor de genera\u021bie a cincea, ceea ce a ridicat \u00een mod special problema dezvolt\u0103rii mecanismelor \u0219i procedurilor de securitate \u00een re\u021belele 5G. <\/p>\n<p>Noua tehnologie oferea viteze de transfer a datelor cu adev\u0103rat impresionante (peste 1 Gbit\/s), o \u00eent\u00e2rziere de mai pu\u021bin de 1 ms \u0219i capacitatea de a conecta simultan aproximativ 1 milion de dispozitive \u00eentr-un radius de 1 km\u00b2. Aceste cerin\u021be extrem de ridicate, impuse re\u021belelor de genera\u021bie a cincea, s-au reflectat \u0219i \u00een principiile lor de organizare.<\/p>\n<p>Principalul dintre ele a fost descentralizarea, care implica plasarea unui num\u0103r mare de baze de date locale \u0219i centre de procesare pe periferia re\u021belei. Aceasta permitea minimizarea \u00eent\u00e2rzierilor \u00een <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/%D0%9C%D0%B5%D0%B6%D0%BC%D0%B0%D1%88%D0%B8%D0%BD%D0%BD%D0%BE%D0%B5_%D0%B2%D0%B7%D0%B0%D0%B8%D0%BC%D0%BE%D0%B4%D0%B5%D0%B9%D1%81%D1%82%D0%B2%D0%B8%D0%B5\">M2M<\/a><\/noindex>-comunicare \u0219i desc\u0103rcarea nucleului re\u021belei datorit\u0103 \u00eentre\u021binerii unui num\u0103r imens de dispozitive IoT. Astfel, grani\u021ba re\u021belelor de nou\u0103 genera\u021bie s-a extins p\u00e2n\u0103 la sta\u021biile de baz\u0103, permi\u021b\u00e2nd crearea de centre locale de comunicare \u0219i oferirea de servicii cloud f\u0103r\u0103 riscul \u00eent\u00e2rzierilor critice sau al refuzului de servicii. Este firesc c\u0103 abordarea modificat\u0103 a organiza\u021biei re\u021belelor \u0219i a serviciilor pentru clien\u021bi a atras aten\u021bia infractorilor, deoarece le oferea noi oportunit\u0103\u021bi de atac at\u00e2t asupra informa\u021biilor confiden\u021biale ale utilizatorilor, c\u00e2t \u0219i asupra componentelor re\u021belei pentru a provoca refuzuri de servicii sau a captura resursele de calcul ale operatorului.<\/p>\n<h2>Principalele vulnerabilit\u0103\u021bi ale re\u021belelor de genera\u021bie 5<\/h2>\n<p><\/p>\n<h3>Suprafa\u021b\u0103 mare de atac<\/h3>\n<p>\n<b class=\"spoiler_title\">Afl\u0103 mai multe<\/b>C\u00e2nd au construit re\u021belele de telecomunica\u021bii de genera\u021bie 3 \u0219i 4, operatorii de telefonie au fost \u00een general limita\u021bi la colaborarea cu un singur sau mai mul\u021bi furnizori, care furnizau simultan un pachet complet de hardware \u0219i software. Adic\u0103, totul putea func\u021biona, ceea ce se nume\u0219te \u201edin cutie\u201d \u2014 era suficient s\u0103 instalezi \u0219i s\u0103 configurezi echipamentul achizi\u021bionat de la furnizor; \u00een acest caz, nu era necesar s\u0103 \u00eenlocuie\u0219ti sau s\u0103 completezi software-ul proprietar. Tendin\u021bele moderne contravin acestui \u201eapropiere clasic\u0103\u201d \u0219i sunt orientate spre virtualizarea re\u021belelor, o abordare multi-furnizor \u00een construc\u021bia lor \u0219i diversitatea software-ului. Tehnologii precum <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/%D0%9F%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D0%BD%D0%BE-%D0%BE%D0%BF%D1%80%D0%B5%D0%B4%D0%B5%D0%BB%D1%8F%D0%B5%D0%BC%D0%B0%D1%8F_%D1%81%D0%B5%D1%82%D1%8C\">SDN<\/a><\/noindex> (eng. Software Defined Network) \u0219i <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/%D0%92%D0%B8%D1%80%D1%82%D1%83%D0%B0%D0%BB%D0%B8%D0%B7%D0%B0%D1%86%D0%B8%D1%8F_%D1%81%D0%B5%D1%82%D0%B5%D0%B2%D1%8B%D1%85_%D1%84%D1%83%D0%BD%D0%BA%D1%86%D0%B8%D0%B9\">NFV<\/a><\/noindex> (eng. Network Functions Virtualization) devin din ce \u00een ce mai populare, ceea ce duce la includerea unui num\u0103r imens de software bazat pe coduri deschise \u00een procesele \u0219i func\u021biile de gestionare a re\u021belelor de telecomunica\u021bii. Aceasta le ofer\u0103 infractorilor oportunitatea de a studia mai bine re\u021beaua operatorului \u0219i de a identifica un num\u0103r mai mare de vulnerabilit\u0103\u021bi, ceea ce, la r\u00e2ndul s\u0103u, cre\u0219te suprafa\u021ba de atac a re\u021belelor de nou\u0103 genera\u021bie \u00een compara\u021bie cu cele actuale.<\/p>\n<h3>Un num\u0103r mare de dispozitive IoT<\/h3>\n<p>\n<b class=\"spoiler_title\">Afl\u0103 mai multe<\/b>P\u00e2n\u0103 \u00een 2021, aproximativ 57% dintre dispozitivele conectate la re\u021belele 5G vor fi dispozitive IoT. Aceasta \u00eenseamn\u0103 c\u0103 majoritatea gazdelor vor avea capacit\u0103\u021bi criptografice limitate (vezi punctul 2) \u0219i, prin urmare, vor fi vulnerabile la atacuri. Num\u0103rul mare de astfel de dispozitive va cre\u0219te riscul de r\u0103sp\u00e2ndire a botnet-urilor \u0219i va oferi posibilitatea de a realiza atacuri DDoS \u0219i mai puternice \u0219i distribuite.<\/p>\n<h3>Capacit\u0103\u021bi criptografice limitate ale dispozitivelor IoT<\/h3>\n<p>\n<b class=\"spoiler_title\">Afl\u0103 mai multe<\/b>Dup\u0103 cum s-a men\u021bionat deja, re\u021belele de genera\u021bie 5 utilizeaz\u0103 activ dispozitivele periferice, care permit desc\u0103rcarea unei p\u0103r\u021bi din \u00eenc\u0103rc\u0103tura de pe nucleul re\u021belei, diminu\u00e2nd astfel laten\u021ba. Acest lucru este esen\u021bial pentru servicii importante, cum ar fi gestionarea vehiculelor autonome \u0219i sistemul de alert\u0103 de urgen\u021b\u0103 <noindex><a rel=\"nofollow\" href=\"https:\/\/www.etsi.org\/deliver\/etsi_ts\/123100_123199\/123167\/12.00.00_60\/ts_123167v120000p.pdf\">IMS<\/a><\/noindex> \u0219i altele, pentru care asigurarea unei laten\u021be minime este critic\u0103, deoarece vie\u021bile oamenilor depind de acest lucru. Av\u00e2nd \u00een vedere conectarea unui num\u0103r mare de dispozitive IoT, care, datorit\u0103 dimensiunilor lor mici \u0219i consumului de energie redus, dispun de resurse de calcul foarte limitate, re\u021belele 5G devin vulnerabile la atacuri menite s\u0103 preia controlul \u0219i s\u0103 manipuleze astfel de dispozitive. De exemplu, sunt posibile scenarii de infectare a dispozitivelor IoT, care fac parte din sistemul \u201e<noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Building_automation\">cas\u0103 inteligent\u0103<\/a><\/noindex>\u201d, cu tipuri de malware, precum <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/%D0%92%D0%B8%D1%80%D1%83%D1%81-%D0%B2%D1%8B%D0%BC%D0%BE%D0%B3%D0%B0%D1%82%D0%B5%D0%BB%D1%8C\">ransomware \u0219i programe de tip ransomware<\/a><\/noindex>. De asemenea, sunt posibile scenarii de preluare a controlului vehiculelor autonome, care primesc comenzi \u0219i informa\u021bii de orientare prin intermediul \u201ecloud-ului\u201d. Formularea acestei vulnerabilit\u0103\u021bi este cauzat\u0103 de descentralizarea re\u021belelor de nou\u0103 genera\u021bie, dar punctul urm\u0103tor va eviden\u021bia problema descentraliz\u0103rii mai clar.<\/p>\n<h3>Descentralizare \u0219i extinderea frontierelor re\u021belei<\/h3>\n<p>\n<b class=\"spoiler_title\">Afl\u0103 mai multe<\/b>Dispozitivele periferice care joac\u0103 rolul de nuclee locale ale re\u021belei realizeaz\u0103 rutarea traficului utilizatorilor, procesarea cererilor, precum \u0219i cache local \u0219i stocarea datelor utilizatorilor. Astfel, limitele re\u021belelor de genera\u021bie 5 se extind, pe l\u00e2ng\u0103 nucleu, c\u0103tre periferie, inclusiv c\u0103tre bazele de date locale \u0219i interfe\u021bele radio 5G-NR (\u00een englez\u0103 5G New Radio). Aceasta creeaz\u0103 posibilit\u0103\u021bi pentru atacuri asupra resurselor de calcul ale dispozitivelor locale, care prin defini\u021bie sunt mai pu\u021bin protejate dec\u00e2t nodurile centrale ale re\u021belei, cu scopul de a provoca o \u00eentrerupere a serviciului. Acest lucru risc\u0103 s\u0103 dezactiveze accesul la internet \u00een \u00eentregi regiuni, s\u0103 afecteze func\u021bionarea corect\u0103 a dispozitivelor IoT (de exemplu, \u00een sistemul \u201ecas\u0103 inteligent\u0103\u201d), precum \u0219i s\u0103 fac\u0103 inaccesibil serviciul de alert\u0103 de urgen\u021b\u0103 IMS.<\/p>\n<p><img decoding=\"async\" alt=\"Introducere \u00een arhitectura de securitate 5G: NFV, chei \u0219i 2 autentific\u0103ri\" src=\"\/wp-content\/uploads\/2019\/12\/9b468364652e5077606e997d203ef398.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nCu toate acestea, \u00een prezent ETSI \u0219i 3GPP au publicat deja mai mult de 10 standarde care abordeaz\u0103 diferite aspecte ale securit\u0103\u021bii re\u021belelor 5G. Majoritatea mecanismelor descrise acolo sunt destinate protec\u021biei \u00eempotriva vulnerabilit\u0103\u021bilor (inclusiv cele men\u021bionate mai sus). Unul dintre principale este standardul <noindex><a rel=\"nofollow\" href=\"https:\/\/www.etsi.org\/deliver\/etsi_ts\/133500_133599\/133501\/15.06.00_60\/ts_133501v150600p.pdf\">TS 23.501 versiunea 15.6.0<\/a><\/noindex>, care descrie arhitectura de securitate a re\u021belelor de genera\u021bie 5.<\/p>\n<h1>Arhitectura 5G<\/h1>\n<p>\n<img decoding=\"async\" alt=\"Introducere \u00een arhitectura de securitate 5G: NFV, chei \u0219i 2 autentific\u0103ri\" src=\"\/wp-content\/uploads\/2019\/12\/3d1b8c350acf85f5fa77e0f3414771cb.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nPentru \u00eenceput, s\u0103 ne concentr\u0103m asupra principiilor cheie ale arhitecturii re\u021belelor 5G, care ne vor permite ulterior s\u0103 dezv\u0103luim pe deplin semnifica\u021bia \u0219i responsabilit\u0103\u021bile fiec\u0103rui modul software \u0219i fiec\u0103rei func\u021bii de securitate 5G.<\/p>\n<ul>\n<li>Separarea nodurilor de re\u021bea \u00een elemente care sprijin\u0103 func\u021bionarea protocoalelor <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/cbs\/blog\/301000\/\">planului utilizatorului<\/a><\/noindex> (de la englez\u0103 UP \u2014 User Plane) \u0219i elemente care sprijin\u0103 func\u021bionarea protocoalelor <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/cbs\/blog\/301000\/\">planului de control<\/a><\/noindex> (de la englez\u0103 CP \u2014 Control Plane), ceea ce cre\u0219te flexibilitatea \u00een ceea ce prive\u0219te scalarea \u0219i desf\u0103\u0219urarea re\u021belei, adic\u0103 este posibil\u0103 amplasarea centralizat\u0103 sau descentralizat\u0103 a unor componente individuale ale nodurilor de re\u021bea.<\/li>\n<li>Suport pentru mecanismul <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/5G_network_slicing\">network slicing<\/a><\/noindex>, baz\u00e2ndu-se pe serviciile furnizate grupurilor specifice de utilizatori finali.<\/li>\n<li>Implementarea elementelor de re\u021bea sub form\u0103 de <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/%D0%92%D0%B8%D1%80%D1%82%D1%83%D0%B0%D0%BB%D0%B8%D0%B7%D0%B0%D1%86%D0%B8%D1%8F_%D1%81%D0%B5%D1%82%D0%B5%D0%B2%D1%8B%D1%85_%D1%84%D1%83%D0%BD%D0%BA%D1%86%D0%B8%D0%B9\">func\u021bii virtuale de re\u021bea<\/a><\/noindex>.<\/li>\n<li>Suport pentru acces simultan la servicii centralizate \u0219i locale, adic\u0103 implementarea conceptelor de calcul \u00een cloud (de la englez\u0103 <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Fog_computing\">fog computing<\/a><\/noindex>) \u0219i calcul de margine (de la englez\u0103 <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Edge_computing\">edge computing<\/a><\/noindex>).<\/li>\n<li>Implementarea <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/%D0%9A%D0%BE%D0%BD%D0%B2%D0%B5%D1%80%D0%B3%D0%B5%D0%BD%D1%86%D0%B8%D1%8F_(%D1%82%D0%B5%D0%BB%D0%B5%D0%BA%D0%BE%D0%BC%D0%BC%D1%83%D0%BD%D0%B8%D0%BA%D0%B0%D1%86%D0%B8%D0%B8)\">Arhitectur\u0103<\/a><\/noindex> convergent\u0103, care combin\u0103 diferite tipuri de re\u021bele de acces \u2014 3GPP 5G New Radio \u0219i <noindex><a rel=\"nofollow\" href=\"https:\/\/www.etsi.org\/deliver\/etsi_ts\/124500_124599\/124502\/15.00.00_60\/ts_124502v150000p.pdf\">non-3GPP<\/a><\/noindex> (Wi-Fi etc.) \u2014 cu un nucleu de re\u021bea unic.<\/li>\n<li>Suport pentru algoritmi \u0219i proceduri de autentificare unificate, indiferent de tipul re\u021belei de acces.<\/li>\n<li>Suport pentru func\u021bii de re\u021bea f\u0103r\u0103 stare (de la englez\u0103: stateless), \u00een care resursa de calcul este separat\u0103 de stocarea resurselor.<\/li>\n<li>Suport pentru roaming cu rutare a traficului at\u00e2t prin re\u021beaua de origine (de la englez\u0103: home-routed roaming), c\u00e2t \u0219i cu 'atterizare' local\u0103 (de la englez\u0103: local breakout) \u00een re\u021beaua gazd\u0103.<\/li>\n<li>Interac\u021biunea \u00eentre func\u021biile de re\u021bea este prezentat\u0103 \u00een dou\u0103 moduri: <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/%D0%A1%D0%B5%D1%80%D0%B2%D0%B8%D1%81-%D0%BE%D1%80%D0%B8%D0%B5%D0%BD%D1%82%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%BD%D0%B0%D1%8F_%D0%B0%D1%80%D1%85%D0%B8%D1%82%D0%B5%D0%BA%D1%82%D1%83%D1%80%D0%B0\">orientat\u0103 pe servicii<\/a><\/noindex> \u0219i <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/%D0%98%D0%BD%D1%82%D0%B5%D1%80%D1%84%D0%B5%D0%B9%D1%81\">prin interfe\u021be<\/a><\/noindex>.<\/li>\n<\/ul>\n<p>\n<b>Conceptul de securitate al re\u021belelor 5G include<\/b>:<\/p>\n<ul>\n<li>Autentificarea utilizatorului din partea re\u021belei.<\/li>\n<li>Autentificarea re\u021belei din partea utilizatorului.<\/li>\n<li>Negocierea cheilor criptografice \u00eentre re\u021bea \u0219i echipamentele utilizatorului.<\/li>\n<li>Criptarea \u0219i controlul integrit\u0103\u021bii traficului de semnal.<\/li>\n<li>Criptarea \u0219i controlul integrit\u0103\u021bii traficului utilizatorului.<\/li>\n<li>Protec\u021bia identificatorului utilizatorului.<\/li>\n<li>Protec\u021bia interfe\u021belor \u00eentre diferitele elemente ale re\u021belei conform concep\u021biei de domeniu de securitate al re\u021belei.<\/li>\n<li>Izolarea diferitelor straturi ale mecanismului <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/5G_network_slicing\">network slicing<\/a><\/noindex> \u0219i determinarea unor niveluri de securitate proprii pentru fiecare strat.<\/li>\n<li>Autentificarea utilizatorului \u0219i protec\u021bia traficului la nivelul serviciilor finale (IMS, IoT \u0219i altele).<\/li>\n<\/ul>\n<p><\/p>\n<h2>Modulele software de baz\u0103 \u0219i func\u021biile de securitate ale re\u021belei 5G<\/h2>\n<p>\n<img decoding=\"async\" alt=\"Introducere \u00een arhitectura de securitate 5G: NFV, chei \u0219i 2 autentific\u0103ri\" src=\"\/wp-content\/uploads\/2019\/12\/223109a13286d858d29263d076888b09.jpg\" style=\"display:block;margin: 0 auto;\" \/> <b>AMF<\/b> (de la englez\u0103: Access &amp; Mobility Management Function \u2014 func\u021bia de gestionare a accesului \u0219i mobilit\u0103\u021bii) \u2014 asigur\u0103:<\/p>\n<ul>\n<li>Organizarea interfe\u021belor planului de control.<\/li>\n<li>Organizarea schimbului de trafic de semnal <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Radio_Resource_Control\">RRC<\/a><\/noindex>, criptarea \u0219i protec\u021bia integrit\u0103\u021bii datelor sale.<\/li>\n<li>Organizarea schimbului de trafic de semnal <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Non-access_stratum\">NAS<\/a><\/noindex>, criptarea \u0219i protec\u021bia integrit\u0103\u021bii datelor sale.<\/li>\n<li>Gestionarea \u00eenregistr\u0103rii echipamentului utilizatorului \u00een re\u021bea \u0219i controlul st\u0103rilor posibile de \u00eenregistrare.<\/li>\n<li>Gestionarea conexiunii echipamentului utilizatorului cu re\u021beaua \u0219i controlul st\u0103rilor posibile.<\/li>\n<li>Gestionarea disponibilit\u0103\u021bii echipamentului utilizatorului \u00een re\u021bea \u00een starea CM-IDLE.<\/li>\n<li>Gestionarea mobilit\u0103\u021bii echipamentului utilizatorului \u00een re\u021bea \u00een starea CM-CONNECTED.<\/li>\n<li>Transmiterea mesajelor scurte \u00eentre echipamentul utilizatorului \u0219i SMF.<\/li>\n<li>Gestionarea serviciilor de geolocalizare.<\/li>\n<li>Alocarea identificatorului fluxului <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/System_Architecture_Evolution\">EPS<\/a><\/noindex> pentru interac\u021biunea cu EPS.<\/li>\n<\/ul>\n<p>\n<b>SMF<\/b> (de la englez\u0103: Session Management Function \u2014 func\u021bia de gestionare a sesiunilor) \u2014 asigur\u0103:<\/p>\n<ul>\n<li>Gestionarea sesiunilor de conectare, adic\u0103 crearea, modificarea \u0219i eliberarea sesiunilor, inclusiv suportul pentru tunelarea \u00eentre re\u021beaua de acces \u0219i UPF.<\/li>\n<li>Distribu\u021bia \u0219i gestionarea adreselor IP ale echipamentului utilizatorului.<\/li>\n<li>Selectarea gateway-ului UPF utilizat.<\/li>\n<li>Organizarea interac\u021biunii cu PCF.<\/li>\n<li>Gestionarea aplic\u0103rii politicilor. <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/QoS\">QoS<\/a><\/noindex>.<\/li>\n<li>Configurarea dinamic\u0103 a echipamentului utilizatorului prin protocoale DHCPv4 \u0219i DHCPv6.<\/li>\n<li>Controlul colect\u0103rii datelor de tarifare \u0219i organizarea interac\u021biunii cu sistemul de facturare.<\/li>\n<li>Continuitatea serviciilor (din englez\u0103: <noindex><a rel=\"nofollow\" href=\"http:\/\/4g5gworld.com\/blog\/session-and-service-continuity-evolution-5g-networks\">SSC \u2014 Continuitatea Sesiunii \u0219i Serviciului<\/a><\/noindex>).<\/li>\n<li>Interac\u021biunea cu re\u021belele vizitatoare \u00een cadrul roamingului.<\/li>\n<\/ul>\n<p>\n<b>UPF<\/b> (englez\u0103: User Plane Function \u2014 Func\u021bia Planului Utilizator) \u2014 asigur\u0103:<\/p>\n<ul>\n<li>Interac\u021biunea cu re\u021bele externe de transfer de date, inclusiv cu internetul global.<\/li>\n<li>Ruteaz\u0103 pachetele utilizatorilor.<\/li>\n<li>Marcarea pachetelor conform politicilor QoS.<\/li>\n<li>Diagnosticul pachetelor utilizatorilor (de exemplu, detectarea aplica\u021biilor pe baza semn\u0103turilor).<\/li>\n<li>Furnizarea de rapoarte despre utilizarea traficului.<\/li>\n<li>UPF este, de asemenea, punctul de ancorare pentru suportul mobilit\u0103\u021bii at\u00e2t \u00een cadrul unei singure, c\u00e2t \u0219i \u00eentre diferite tehnologii de acces radio.<\/li>\n<\/ul>\n<p>\n<b>UDM<\/b> (englez\u0103: Unified Data Management \u2014 Gestionarea Unificat\u0103 a Datelor) \u2014 asigur\u0103:<\/p>\n<ul>\n<li>Gestionarea datelor profilurilor utilizatorilor, inclusiv stocarea \u0219i modificarea listei de servicii disponibile pentru utilizatori \u0219i parametrii corespunz\u0103tori.<\/li>\n<li>Gestionare <noindex><a rel=\"nofollow\" href=\"http:\/\/www.techplayon.com\/5g-identifiers-supi-and-suci\/\">SUPI<\/a><\/noindex><\/li>\n<li>Generarea datelor de acreditive de autentificare 3GPP. <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Authentication_and_Key_Agreement\">AKA<\/a><\/noindex>.<\/li>\n<li>Autorizarea accesului pe baza datelor profilului (de exemplu, restric\u021bia de roaming).<\/li>\n<li>Gestionarea \u00eenregistr\u0103rii utilizatorului, adic\u0103 stocarea AMF-ului care deserve\u0219te.<\/li>\n<li>Suportul pentru continuitatea serviciului \u0219i a sesiunii de conectare, adic\u0103 stocarea SMF-ului alocat pentru sesiunea de conectare curent\u0103.<\/li>\n<li>Gestionarea livr\u0103rii SMS-urilor.<\/li>\n<li>Mai multe UDM-uri diferite pot deservi un singur utilizator \u00een cadrul diferitelor tranzac\u021bii.<\/li>\n<\/ul>\n<p>\n<b>UDR<\/b> (englez\u0103: Unified Data Repository \u2014 Repozitoriu Unificat de Date) \u2014 asigur\u0103 stocarea diverselor date utilizator \u0219i este, de fapt, baza de date a tuturor abona\u021bilor re\u021belei. <\/p>\n<p><b>UDSF<\/b> (\u00een englez\u0103 Unstructured Data Storage Function \u2014 func\u021bia de stocare a datelor necorespunz\u0103toare) \u2014 asigur\u0103 p\u0103strarea contextelor curente ale utilizatorilor \u00eenregistrati de modulele AMF. Aceast\u0103 informa\u021bie poate fi \u00een general reprezentat\u0103 ca date cu o structur\u0103 nedefinit\u0103. Contexturile utilizatorilor pot fi utilizate pentru a asigura continuitatea \u0219i ne\u00eentreruperea sesiunilor abona\u021bilor at\u00e2t \u00een cazul unei deconect\u0103ri planificate din serviciu a unuia dintre AMF, c\u00e2t \u0219i \u00een cazul unei situa\u021bii de urgen\u021b\u0103. \u00cen ambele cazuri, AMF-ul de rezerv\u0103 va \u201eprelua\u201d serviciul, folosind contexturile salvate \u00een USDF.<\/p>\n<p>Combina\u021bia UDR \u0219i UDSF pe aceea\u0219i platform\u0103 fizic\u0103 este o implementare tipic\u0103 a acestor func\u021bii de re\u021bea.<\/p>\n<p><b>PCF<\/b> (\u00een englez\u0103 Policy Control Function \u2014 func\u021bia de control al politicilor) \u2014 formuleaz\u0103 \u0219i aloc\u0103 utilizatorilor diverse politici de serviciu, inclusiv parametrii QoS \u0219i regulile de tarifare. De exemplu, pentru transmiterea unui anumit tip de trafic, pot fi create dinamic canale virtuale cu caracteristici diferite. \u00cen acest proces, se pot lua \u00een considerare cerin\u021bele serviciului solicitat de abonat, nivelul de \u00eenc\u0103rcare al re\u021belei, volumul de trafic consumat etc.<\/p>\n<p><b>NEF<\/b> (\u00een englez\u0103 Network Exposure Function \u2014 func\u021bia de expunere a re\u021belei) \u2014 asigur\u0103:<\/p>\n<ul>\n<li>Organizarea interac\u021biunii sigure \u00eentre platformele externe \u0219i aplica\u021bii cu nucleul re\u021belei.<\/li>\n<li>Gestionarea parametrii QoS \u0219i regulilor de tarifare pentru utilizatori specifici.<\/li>\n<\/ul>\n<p>\n<b>SEAF<\/b> (\u00een englez\u0103 Security Anchor Function \u2014 func\u021bia ancor\u0103 de securitate) \u2014 \u00eempreun\u0103 cu AUSF asigur\u0103 autentificarea utilizatorilor \u00een momentul \u00eenregistr\u0103rii \u00een re\u021bea cu orice tehnologie de acces.<\/p>\n<p><b>AUSF<\/b> (\u00een englez\u0103 Authentication Server Function \u2014 func\u021bia de server de autentificare) \u2014 joac\u0103 rolul unui server de autentificare, primind \u0219i proces\u00e2nd cererile de la SEAF \u0219i redirec\u021bion\u00e2ndu-le c\u0103tre ARPF.<\/p>\n<p><b>ARPF<\/b> (\u00een englez\u0103 Authentication Credential Repository and Processing Function \u2014 func\u021bia de depozitare \u0219i procesare a acreditivelor de autentificare) \u2014 asigur\u0103 stocarea cheilor secrete personale (KI) \u0219i a parametrelor algoritmilor criptografici, precum \u0219i generarea vectorilor de autentificare conform algoritmilor 5G-AKA sau <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/EAP\">EAP<\/a><\/noindex>-AKA. Este situat \u00eentr-un centru de date protejat de influen\u021be fizice externe al operatorului de telecomunica\u021bii \u0219i, \u00een general, este integrat cu UDM.<\/p>\n<p><b>SCMF<\/b> (\u00een englez\u0103 Security Context Management Function \u2014 func\u021bia de gestionare a <noindex><a rel=\"nofollow\" href=\"https:\/\/it.wikireading.ru\/60129\">contextului de securitate<\/a><\/noindex>) \u2014 asigur\u0103 gestionarea ciclului de via\u021b\u0103 al contextului de securitate 5G.<\/p>\n<p><b>SPCF<\/b> (\u00een englez\u0103 Security Policy Control Function \u2014 func\u021bia de control al politicii de securitate) \u2014 asigur\u0103 alinierea \u0219i aplicarea politicilor de securitate pentru utilizatori specifici. Acestea iau \u00een considerare capacit\u0103\u021bile re\u021belei, capacit\u0103\u021bile echipamentului utilizatorului \u0219i cerin\u021bele specifice ale serviciului (de exemplu, nivelurile de protec\u021bie oferite de serviciul de comunica\u021bii critice \u0219i serviciul de acces wireless la internet pot diferi). Aplicarea politicilor de securitate include: selectarea AUSF, selectarea algoritmului de autentificare, alegerea algoritmilor de criptare a datelor \u0219i de control al integrit\u0103\u021bii, definirea lungimii \u0219i a ciclului de via\u021b\u0103 al cheilor.<\/p>\n<p><b>SIDF<\/b> (\u00een englez\u0103 Subscription Identifier De-concealing Function \u2014 func\u021bia de extragere a identificatorului utilizatorului) \u2014 asigur\u0103 extragerea identificatorului permanent al abonamentului utilizatorului (\u00een englez\u0103 SUPI) dintr-un identificator ascuns (\u00een englez\u0103. <noindex><a rel=\"nofollow\" href=\"http:\/\/www.techplayon.com\/5g-identifiers-supi-and-suci\/\">SUCI<\/a><\/noindex>), ob\u021binut \u00een cadrul cererii de procedur\u0103 de autentificare \u201eAuth Info Req\u201d.<\/p>\n<h2>Cerin\u021bele de baz\u0103 de securitate pentru re\u021belele de comunica\u021bii 5G<\/h2>\n<p>\n<b class=\"spoiler_title\">Afl\u0103 mai multe<\/b><b>Autentificarea utilizatorului<\/b>: Re\u021beaua 5G care ofer\u0103 servicii trebuie s\u0103 autentifice SUPI utilizatorului \u00een procesul 5G AKA \u00eentre utilizator \u0219i re\u021bea.<\/p>\n<p><b>Autentificarea re\u021belei care ofer\u0103 servicii<\/b>: Utilizatorul trebuie s\u0103 autentifice identificatorul re\u021belei 5G care ofer\u0103 servicii, iar autentificarea se asigur\u0103 prin utilizarea cu succes a cheilor ob\u021binute \u00een urma procedurii 5G AKA.<\/p>\n<p><b>Autorizarea utilizatorului<\/b>: Re\u021beaua care ofer\u0103 servicii trebuie s\u0103 autorizeze utilizatorul conform profilului utilizatorului ob\u021binut din re\u021beaua operatorului de domiciliu.<\/p>\n<p><b>Autorizarea re\u021belei care ofer\u0103 servicii de c\u0103tre re\u021beaua operatorului de domiciliu<\/b>: Utilizatorul trebuie s\u0103 primeasc\u0103 o confirmare c\u0103 este conectat la re\u021beaua care ofer\u0103 servicii, care este autorizat\u0103 de re\u021beaua operatorului de domiciliu pentru furnizarea serviciilor. Autorizarea este implicit\u0103 \u00een sensul c\u0103 este asigurat\u0103 prin finalizarea cu succes a procedurii 5G AKA.<\/p>\n<p><b>Autorizarea re\u021belei de acces de c\u0103tre re\u021beaua operatorului de domiciliu<\/b>: Utilizatorului trebuie s\u0103 i se ofere o confirmare c\u0103 este conectat la o re\u021bea de acces autorizat\u0103 de operatorul de re\u021bea pentru a furniza servicii. Autoriza\u021bia este implicit\u0103 \u00een sensul c\u0103 este asigurat\u0103 prin stabilirea cu succes a securit\u0103\u021bii re\u021belei de acces. Acest tip de autoriza\u021bie trebuie aplicat pentru orice tip de re\u021bea de acces.<\/p>\n<p><b>Servicii de urgen\u021b\u0103 neautentificate<\/b>: Pentru a respecta cerin\u021bele de reglementare \u00een anumite regiuni, re\u021belele 5G trebuie s\u0103 ofere posibilitatea de acces neautentificat pentru serviciile de urgen\u021b\u0103.<\/p>\n<p><b>Nucleul re\u021belei \u0219i re\u021beaua de acces radio<\/b>: Nucleul re\u021belei 5G \u0219i re\u021beaua de acces radio 5G trebuie s\u0103 sus\u021bin\u0103 utilizarea algoritmilor de criptare \u0219i integritate cu o lungime a cheii de 128 bi\u021bi pentru a asigura securitatea <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Access_stratum\">AS<\/a><\/noindex> \u0219i <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Non-access_stratum\">NAS<\/a><\/noindex>. Interfe\u021bele de re\u021bea trebuie s\u0103 sus\u021bin\u0103 chei de criptare de 256 bi\u021bi.<\/p>\n<h2>Cerin\u021be de baz\u0103 de securitate pentru echipamentele utilizatorului<\/h2>\n<p>\n<b class=\"spoiler_title\">Afl\u0103 mai multe<\/b><\/p>\n<ul>\n<li>Echipamentele utilizatorului trebuie s\u0103 sus\u021bin\u0103 criptarea, protec\u021bia integrit\u0103\u021bii \u0219i protec\u021bia \u00eempotriva atacurilor de reproducere a datelor utilizatorului transmise \u00eentre acestea \u0219i re\u021beaua de acces radio.<\/li>\n<li>Echipamentele utilizatorului trebuie s\u0103 activeze mecanismele de criptare \u0219i protec\u021bie a integrit\u0103\u021bii datelor conform instruc\u021biunilor primite de la re\u021beaua de acces radio.<\/li>\n<li>Echipamentele utilizatorului trebuie s\u0103 sus\u021bin\u0103 criptarea, protec\u021bia integrit\u0103\u021bii \u0219i protec\u021bia \u00eempotriva atacurilor de reproducere a traficului de semnale RRC \u0219i NAS.<\/li>\n<li>Echipamentele utilizatorului trebuie s\u0103 sus\u021bin\u0103 urm\u0103toarele algoritmi criptografici: NEA0, NIA0, 128-NEA1, 128-NIA1, 128-NEA2, 128-NIA2.<\/li>\n<li>Echipamentele utilizatorului pot sus\u021bine urm\u0103toarele algoritmi criptografici: 128-NEA3, 128-NIA3.<\/li>\n<li>Echipamentele utilizatorului trebuie s\u0103 sus\u021bin\u0103 urm\u0103toarele algoritmi criptografici: 128-EEA1, 128-EEA2, 128-EIA1, 128-EIA2, \u00een cazul \u00een care sus\u021bin conectarea la re\u021beaua de acces radio E-UTRA.<\/li>\n<li>Protec\u021bia confiden\u021bialit\u0103\u021bii datelor utilizatorului transmise \u00eentre echipamentele utilizatorului \u0219i re\u021beaua de acces radio este op\u021bional\u0103, dar trebuie asigurat\u0103 \u00een toate cazurile \u00een care este permis\u0103 de reglement\u0103rile legale.<\/li>\n<li>Protec\u021bia confiden\u021bialit\u0103\u021bii traficului de semnale RRC \u0219i NAS este op\u021bional\u0103.<\/li>\n<li>Cheia permanent\u0103 a utilizatorului trebuie s\u0103 fie protejat\u0103 \u0219i s\u0103 fie stocat\u0103 \u00een componente de echipament ale utilizatorului corespunz\u0103tor securizate.<\/li>\n<li>Identificatorul permanent al abonamentului nu trebuie transmis \u00een mod deschis prin re\u021beaua de acces radio, cu excep\u021bia informa\u021biilor necesare pentru rutare corect\u0103 (de exemplu, <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/Mobile_Country_Code\">MCC<\/a><\/noindex> \u0219i <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/MNC\">MNC<\/a><\/noindex>).<\/li>\n<li>Cheia public\u0103 a re\u021belei operatorului de baz\u0103, identificatorul acestei chei, identificatorul schemei de securitate \u0219i identificatorul de rutare trebuie s\u0103 fie stocate \u00een <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/USIM-%D0%BA%D0%B0%D1%80%D1%82%D0%B0\">USIM<\/a><\/noindex>.<\/li>\n<\/ul>\n<p>\nFiec\u0103rui algoritm de criptare \u00eei corespunde un num\u0103r binar:<\/p>\n<ul>\n<li>\u201e0000\u201d: NEA0 \u2014 Algoritmul de criptare Null<\/li>\n<li>\u201e0001\u201d: 128-NEA1 \u2014 128-bit <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/SNOW\">SNOW<\/a><\/noindex> algoritm bazat pe 3G<\/li>\n<li>\u201e0010\u201d 128-NEA2 \u2014 128-bit <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/Advanced_Encryption_Standard\">AES<\/a><\/noindex> algoritm bazat<\/li>\n<li>\u201e0011\u201d 128-NEA3 \u2014 128-bit <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Zuc_stream_cipher\">ZUC<\/a><\/noindex> algoritm bazat.<\/li>\n<\/ul>\n<p>\n<b class=\"spoiler_title\">Criptarea datelor utiliz\u00e2nd 128-NEA1 \u0219i 128-NEA2<\/b><img decoding=\"async\" alt=\"Introducere \u00een arhitectura de securitate 5G: NFV, chei \u0219i 2 autentific\u0103ri\" src=\"\/wp-content\/uploads\/2019\/12\/101481062364f5cc777df59b9a589e5b.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nP.S. Schema a fost \u00eemprumutat\u0103 din <noindex><a rel=\"nofollow\" href=\"https:\/\/www.etsi.org\/deliver\/etsi_ts\/133500_133599\/133501\/15.06.00_60\/ts_133501v150600p.pdf\">TS 133.501<\/a><\/noindex><\/p>\n<p><b class=\"spoiler_title\">Generarea de imituiri de c\u0103tre algoritmii 128-NIA1 \u0219i 128-NIA2 pentru asigurarea integrit\u0103\u021bii<\/b><img decoding=\"async\" alt=\"Introducere \u00een arhitectura de securitate 5G: NFV, chei \u0219i 2 autentific\u0103ri\" src=\"\/wp-content\/uploads\/2019\/12\/35271aaab9173837fcb859e71a31cc87.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nP.S. Schema a fost \u00eemprumutat\u0103 din <noindex><a rel=\"nofollow\" href=\"https:\/\/www.etsi.org\/deliver\/etsi_ts\/133500_133599\/133501\/15.06.00_60\/ts_133501v150600p.pdf\">TS 133.501<\/a><\/noindex><\/p>\n<p><\/p>\n<h2>Cerin\u021be de baz\u0103 de securitate pentru func\u021biile re\u021belei 5G<\/h2>\n<p>\n<b class=\"spoiler_title\">Afl\u0103 mai multe<\/b><\/p>\n<ul>\n<li>AMF trebuie s\u0103 suporte autentificarea primar\u0103 utiliz\u00e2nd SUCI.<\/li>\n<li>SEAF trebuie s\u0103 suporte autentificarea primar\u0103 utiliz\u00e2nd SUCI.<\/li>\n<li>UDM \u0219i ARPF trebuie s\u0103 stocheze cheia permanent\u0103 a utilizatorului \u0219i s\u0103 asigure protec\u021bia acesteia \u00eempotriva furtului.<\/li>\n<li>AUSF trebuie s\u0103 furnizeze SUPI re\u021belei locale doar \u00een cazul autentific\u0103rii primare reu\u0219ite utiliz\u00e2nd SUCI.<\/li>\n<li>NEF nu trebuie s\u0103 transmit\u0103 informa\u021bii ascunse despre nucleul re\u021belei \u00een afara domeniului de securitate al operatorului.<\/li>\n<\/ul>\n<h1>Proceduri de baz\u0103 de securitate<\/h1>\n<p><\/p>\n<h2>Domenii de \u00eencredere<\/h2>\n<p>\n\u00cen re\u021belele de genera\u021bia a 5-a, \u00eencrederea \u00een elementele re\u021belei scade pe m\u0103sur\u0103 ce acestea se \u00eendep\u0103rteaz\u0103 de nucleul re\u021belei. Aceast\u0103 concep\u021bie influen\u021beaz\u0103 solu\u021biile implementate \u00een arhitectura de securitate 5G. Prin urmare, se poate vorbi despre un model de \u00eencredere \u00een re\u021belele 5G care define\u0219te comportamentul mecanismelor de securitate a re\u021belei.<\/p>\n<p>Din partea utilizatorului, domeniul de \u00eencredere este constituit din UICC \u0219i USIM.<\/p>\n<p>Din partea re\u021belei, domeniul de \u00eencredere are o structur\u0103 mai complex\u0103.<\/p>\n<p><img decoding=\"async\" alt=\"Introducere \u00een arhitectura de securitate 5G: NFV, chei \u0219i 2 autentific\u0103ri\" src=\"\/wp-content\/uploads\/2019\/12\/de3f67c48e1f61afca7637417a2a735b.jpg\" style=\"display:block;margin: 0 auto;\" \/> Re\u021beaua de acces radio este \u00eemp\u0103r\u021bit\u0103 \u00een dou\u0103 componente \u2014 <b>DU<\/b> (de la Distributed Units \u2014 unit\u0103\u021bi distribuite ale re\u021belei) \u0219i <b>CU<\/b> (de la Central Units \u2014 unit\u0103\u021bi centrale ale re\u021belei). \u00cempreun\u0103, ele formeaz\u0103 <b>gNB<\/b> \u2014 interfa\u021ba radio a sta\u021biei de baz\u0103 a re\u021belei 5G. DU nu au acces direct la datele utilizatorului, deoarece pot fi desf\u0103\u0219urate \u00een segmente de infrastructur\u0103 nesecurizate. CU, pe de alt\u0103 parte, trebuie desf\u0103\u0219urate \u00een segmente protejate ale re\u021belei, deoarece sunt responsabile pentru terminarea traficului mecanismelor de securitate AS. \u00cen nucleul re\u021belei se afl\u0103 <b>AMF<\/b>, termin\u00e2nd traficul mecanismelor de securitate NAS. \u00cen specifica\u021bia actual\u0103 3GPP 5G Phase 1 este descris\u0103 combina\u021bia <b>AMF<\/b> cu func\u021bia de securitate <b>SEAF<\/b>, con\u021bin\u00e2nd cheia r\u0103d\u0103cin\u0103 (cunoscut\u0103 \u0219i sub numele de \u201echeia ancor\u0103\u201d) a re\u021belei care ofer\u0103 servicii. <b>AUSF<\/b> este responsabil\u0103 pentru stocarea cheii ob\u021binute dup\u0103 autentificarea reu\u0219it\u0103. Aceasta este necesar\u0103 pentru reutilizare \u00een cazurile de conectare simultan\u0103 a utilizatorului la mai multe re\u021bele de acces radio. <b>ARPF<\/b> stocheaz\u0103 informa\u021biile utilizatorilor \u0219i este echivalentul USIM pentru abona\u021bi. <b>UDR<\/b> \u0219i <b>UDM<\/b> stocheaz\u0103 informa\u021biile utilizatorului, pe care le utilizeaz\u0103 pentru a defini logica gener\u0103rii datelor de autentificare, identificatorilor utilizatorilor, asigurarea continuit\u0103\u021bii sesiunii etc.<\/p>\n<h2>Ierarhia cheilor \u0219i schemele lor de distribu\u021bie<\/h2>\n<p>\n\u00cen re\u021belele de a cincea genera\u021bie, spre deosebire de re\u021belele 4G-LTE, procesul de autentificare are dou\u0103 componente: autentificarea primar\u0103 \u0219i autentificarea secundar\u0103. Autentificarea primar\u0103 este obligatorie pentru toate dispozitivele utilizatorilor care se conecteaz\u0103 la re\u021bea. Autentificarea secundar\u0103 poate fi efectuat\u0103 la cererea re\u021belelor externe, dac\u0103 abona\u021bii se conecteaz\u0103 la acestea.<\/p>\n<p>Dup\u0103 finalizarea reu\u0219it\u0103 a autentific\u0103rii primare \u0219i generarea cheii comune K \u00eentre utilizator \u0219i re\u021bea, din cheia K se extrage KSEAF \u2014 o cheie special\u0103 ancor\u0103 (r\u0103d\u0103cin\u0103) a re\u021belei care ofer\u0103 servicii. Ulterior, din aceast\u0103 cheie se genereaz\u0103 cheile care asigur\u0103 confiden\u021bialitatea \u0219i integritatea datelor traficului de semnalizare RRC \u0219i NAS.<\/p>\n<p><b class=\"spoiler_title\">Schema cu explica\u021bii<\/b><img decoding=\"async\" alt=\"Introducere \u00een arhitectura de securitate 5G: NFV, chei \u0219i 2 autentific\u0103ri\" src=\"\/wp-content\/uploads\/2019\/12\/c10946db4ddebcb53f6fcfc585b7be23.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<b>Denumiri<\/b>:<br \/>\n<b>CK<\/b> (eng. Cipher Key)<br \/>\n<b>IK<\/b> (eng. Integrity Key) \u2014 cheia utilizat\u0103 \u00een mecanismele de protec\u021bie a integrit\u0103\u021bii datelor.<br \/>\n<b>CK\u2019<\/b> (eng. Cipher Key) \u2014 o alt\u0103 cheie criptografic\u0103, creat\u0103 din CK pentru mecanismul EAP-AKA.<br \/>\n<b>IK\u2019<\/b> (eng. Integrity Key) \u2014 o alt\u0103 cheie folosit\u0103 \u00een mecanismele de protec\u021bie a integrit\u0103\u021bii datelor pentru EAP-AKA.<br \/>\n<b>KAUSF<\/b> \u2014 creat\u0103 de func\u021bia ARPF \u0219i echipamentul utilizatorului din <b>CK<\/b> \u0219i <b>IK<\/b> \u00een timpul 5G AKA \u0219i EAP-AKA.<br \/>\n<b>KSEAF<\/b> \u2014 cheia ancor\u0103 ob\u021binut\u0103 de func\u021bia AUSF din cheia <b>KAMFAUSF<\/b>.<br \/>\n<b>KAMF<\/b> \u2014 cheia ob\u021binut\u0103 de func\u021bia SEAF din cheie <b>KSEAF<\/b>.<br \/>\n<b>KNASint<\/b>, <b>KNASenc<\/b> \u2014 cheile ob\u021binute de func\u021bia AMF din cheie <b>KAMF<\/b> pentru protejarea traficului semnal NAS.<br \/>\n<b>KRRCint<\/b>, <b>KRRCenc<\/b> \u2014 cheile ob\u021binute de func\u021bia AMF din cheie <b>KAMF<\/b> pentru protejarea traficului semnal RRC.<br \/>\n<b>KUPint<\/b>, <b>KUPenc<\/b> \u2014 cheile ob\u021binute de func\u021bia AMF din cheie <b>KAMF<\/b> pentru protejarea traficului semnal AS.<br \/>\n<b>NH<\/b> \u2014 cheia intermediar\u0103 ob\u021binut\u0103 de func\u021bia AMF din cheie <b>KAMF<\/b> pentru asigurarea securit\u0103\u021bii datelor \u00een timpul transferurilor.<br \/>\n<b>KgNB<\/b> \u2014 cheia ob\u021binut\u0103 de func\u021bia AMF din cheie <b>KAMF<\/b> pentru asigurarea securit\u0103\u021bii mecanismelor de mobilitate.<\/p>\n<p><b class=\"spoiler_title\">Schema gener\u0103rii SUCI din SUPI \u0219i invers<\/b><\/p>\n<h2>Schema ob\u021binerii SUPI \u0219i SUCI<\/h2>\n<p>\nGenerarea SUCI din SUPI \u0219i SUPI din SUCI:<br \/>\n<img decoding=\"async\" alt=\"Introducere \u00een arhitectura de securitate 5G: NFV, chei \u0219i 2 autentific\u0103ri\" src=\"\/wp-content\/uploads\/2019\/12\/ba2bdfbe1bded3f34edb7853a3758fbd.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h2>Autentificare<\/h2>\n<p><\/p>\n<h3>Autentificare ini\u021bial\u0103<\/h3>\n<p>\n\u00cen re\u021belele 5G, EAP-AKA \u0219i 5G AKA sunt mecanismele standard de autentificare ini\u021bial\u0103. S\u0103 descompunem mecanismul de autentificare ini\u021bial\u0103 \u00een dou\u0103 faze: prima r\u0103spunde de ini\u021bierea autentific\u0103rii \u0219i alegerea metodei de autentificare, a doua \u2014 de autentificarea reciproc\u0103 \u00eentre utilizator \u0219i re\u021bea.<\/p>\n<p><img decoding=\"async\" alt=\"Introducere \u00een arhitectura de securitate 5G: NFV, chei \u0219i 2 autentific\u0103ri\" src=\"\/wp-content\/uploads\/2019\/12\/87d17467440f027da9c5f8f521f2f800.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h4>Ini\u021biere<\/h4>\n<p>\nUtilizatorul trimite o cerere de \u00eenregistrare la SEAF, care con\u021bine un identificator ascuns al subscrierii utilizatorului SUCI.<\/p>\n<p>SEAF trimite c\u0103tre AUSF un mesaj cerere de autentificare (Nausf_UEAuthentication_Authenticate Request), con\u021bin\u00e2nd SNN (diminutive din englez\u0103 pentru Serving Network Name \u2014 numele re\u021belei de servire) \u0219i SUPI sau SUCI.<\/p>\n<p>AUSF verific\u0103 dac\u0103 SEAF, care solicit\u0103 autentificarea, are permisiunea de a folosi SNN-ul respectiv. Dac\u0103 re\u021beaua de servire nu este autorizat\u0103 s\u0103 utilizeze SNN-ul respectiv, AUSF r\u0103spunde cu un mesaj de eroare de autorizare \u201eRe\u021beaua de servire nu este autorizat\u0103\u201d (Nausf_UEAuthentication_Authenticate Response).<\/p>\n<p>Cererea de acreditive pentru autentificare de c\u0103tre AUSF la UDM, ARPF sau SIDF se face pe baza SUPI sau SUCI \u0219i SNN.<\/p>\n<p>Pe baza SUPI sau SUCI \u0219i a informa\u021biilor despre utilizator, UDM\/ARPF alege metoda de autentificare care va fi utilizat\u0103 ulterior \u0219i emite acreditivele utilizatorului.<\/p>\n<h4>Autentificare reciproc\u0103<\/h4>\n<p>\nLa utilizarea oric\u0103rei metode de autentificare, func\u021biile de re\u021bea UDM\/ARPF trebuie s\u0103 genereze un vector de autentificare (AV).<\/p>\n<p>EAP-AKA: UDM\/ARPF genereaz\u0103 mai \u00eent\u00e2i un vector de autentificare cu bitul de separare AMF = 1, dup\u0103 care genereaz\u0103 <b>CK\u2019<\/b> \u0219i <b>IK\u2019<\/b> din <b>CK<\/b>, <b>IK<\/b> \u0219i SNN \u0219i formeaz\u0103 un nou vector de autentificare AV (RAND, AUTN, XRES*, <b>CK\u2019<\/b>, <b>IK\u2019<\/b>), care este trimis la AUSF cu indica\u021bia de a-l folosi doar pentru EAP-AKA.<\/p>\n<p>5G AKA: UDM\/ARPF prime\u0219te cheia <b>KAUSF<\/b> din <b>CK<\/b>, <b>IK<\/b> \u0219i SNN, dup\u0103 care genereaz\u0103 5G HE AV (diminutive din englez\u0103 pentru 5G Home Environment Authentication Vector). Vectorul de autentificare 5G HE AV (RAND, AUTN, XRES, <b>KAUSF<\/b>) este trimis la AUSF cu specifica\u021bia de a fi utilizat doar pentru 5G AKA.<\/p>\n<p>Dup\u0103 aceasta, AUSF prime\u0219te cheia ancor\u0103 <b>KSEAF<\/b> din cheie <b>KAUSF<\/b> \u0219i trimite \u00een SEAF solicitarea \u00abChallenge\u00bb \u00een mesajul \u00abNausf_UEAuthentication_Authenticate Response\u00bb, care con\u021bine de asemenea RAND, AUTN \u0219i RES*. Ulterior, RAND \u0219i AUTN sunt transmise echipamentului utilizatorului printr-un mesaj de semnalizare NAS securizat. USIM-ul utilizatorului calculeaz\u0103 RES* din RAND \u0219i AUTN primite \u0219i \u00eel trimite \u00een SEAF. SEAF retransmite aceast\u0103 valoare c\u0103tre AUSF pentru verificare.<\/p>\n<p>AUSF compar\u0103 XRES* stocat cu RES* ob\u021binut de la utilizator. \u00cen caz de coresponden\u021b\u0103, AUSF \u0219i UDM din re\u021beaua de origine a operatorului sunt notificate despre autentificarea reu\u0219it\u0103, iar utilizatorul \u0219i SEAF genereaz\u0103 \u00een mod independent cheia <b>KAMF<\/b> din <b>KSEAF<\/b> \u0219i SUPI pentru comunica\u021bia ulterioar\u0103.<\/p>\n<h3>Autentificare secundar\u0103<\/h3>\n<p>\nStandardul 5G suport\u0103 o autentificare secundar\u0103 op\u021bional\u0103 bazat\u0103 pe EAP-AKA \u00eentre echipamentul utilizatorului \u0219i re\u021beaua extern\u0103 de transfer de date. \u00cen acest caz, SMF joac\u0103 rolul de autentificator EAP \u0219i se bazeaz\u0103 pe activitatea <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/AAA_(%D0%B8%D0%BD%D1%84%D0%BE%D1%80%D0%BC%D0%B0%D1%86%D0%B8%D0%BE%D0%BD%D0%BD%D0%B0%D1%8F_%D0%B1%D0%B5%D0%B7%D0%BE%D0%BF%D0%B0%D1%81%D0%BD%D0%BE%D1%81%D1%82%D1%8C)\">AAA<\/a><\/noindex>-serverului din re\u021beaua extern\u0103, care autentific\u0103 \u0219i autorizeaz\u0103 utilizatorul.<\/p>\n<p><img decoding=\"async\" alt=\"Introducere \u00een arhitectura de securitate 5G: NFV, chei \u0219i 2 autentific\u0103ri\" src=\"\/wp-content\/uploads\/2019\/12\/a42963ec26acea1397a4c7a9e4c2dc9f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<ul>\n<li>Se efectueaz\u0103 o autentificare primar\u0103 obligatorie a utilizatorului \u00een re\u021beaua de origine \u0219i se genereaz\u0103 un context de securitate NAS comun cu AMF.<\/li>\n<li>Utilizatorul trimite o solicitare AMF pentru stabilirea unei sesiuni.<\/li>\n<li>AMF trimite o solicitare pentru stabilirea unei sesiuni \u00een SMF indic\u00e2nd SUPI-ul utilizatorului.<\/li>\n<li>SMF verific\u0103 datele de autentificare ale utilizatorului \u00een UDM folosind SUPI-ul furnizat.<\/li>\n<li>SMF trimite un r\u0103spuns la solicitarea de la AMF.<\/li>\n<li>SMF ini\u021biaz\u0103 procedura de autentificare EAP cu scopul de a ob\u021bine permisiunea pentru stabilirea unei sesiuni de la serverul AAA din re\u021beaua extern\u0103. Pentru aceasta, SMF \u0219i utilizatorul schimb\u0103 mesaje pentru a ini\u021bia procedura.<\/li>\n<li>Utilizatorul \u0219i serverul AAA din re\u021beaua extern\u0103 \u00ee\u0219i schimb\u0103 \u00een continuare mesaje pentru a realiza autentificarea \u0219i autorizarea utilizatorului. \u00cen acest proces, utilizatorul trimite mesaje c\u0103tre SMF, care la r\u00e2ndul s\u0103u schimb\u0103 mesaje cu re\u021beaua extern\u0103 prin intermediul UPF.<\/li>\n<\/ul>\n<p><\/p>\n<h1>Concluzie<\/h1>\n<p>\nDe\u0219i arhitectura de securitate 5G se bazeaz\u0103 pe reutilizarea tehnologiilor existente, aceasta se confrunt\u0103 cu provoc\u0103ri complet noi. Un num\u0103r mare de dispozitive IoT, limite extinse ale re\u021belei \u0219i elemente de arhitectur\u0103 descentralizat\u0103 \u2013 acestea sunt doar c\u00e2teva dintre principiile cheie ale standardului 5G, care ofer\u0103 o mare oportunitate pentru infractorii cibernetici.<\/p>\n<p>Standardul principal pentru arhitectura de securitate 5G \u2013 <noindex><a rel=\"nofollow\" href=\"https:\/\/www.etsi.org\/deliver\/etsi_ts\/133500_133599\/133501\/15.06.00_60\/ts_133501v150600p.pdf\">TS 23.501 versiunea 15.6.0<\/a><\/noindex> \u2013 con\u021bine punctele cheie de func\u021bionare ale mecanismelor \u0219i procedurilor de securitate. \u00cen special, descrie rolul fiec\u0103rei VNF \u00een protejarea datelor utilizatorilor \u0219i a nodurilor re\u021belei, \u00een generarea cheilor criptografice \u0219i \u00een efectuarea procedurii de autentificare. \u00cens\u0103 chiar \u0219i acest standard nu ofer\u0103 r\u0103spunsuri la \u00eentreb\u0103rile presante de securitate cu care se confrunt\u0103 operatorii de telecomunica\u021bii, din ce \u00een ce mai des pe m\u0103sur\u0103 ce re\u021belele de nou\u0103 genera\u021bie se dezvolt\u0103 \u0219i sunt implementate.<\/p>\n<p>\u00cen acest context, ne dorim s\u0103 credem c\u0103 dificult\u0103\u021bile de operare \u0219i protejare a re\u021belelor de genera\u021bie 5 nu vor afecta utilizatorii obi\u0219nui\u021bi, care promiteau viteze \u0219i timp de r\u0103spuns precum cei care nu mai pot a\u0219tepta s\u0103 testeze toate caracteristicile promisiunii re\u021belelor de nou\u0103 genera\u021bie.<\/p>\n<h1>Linkuri utile<\/h1>\n<p>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/www.3gpp.org\/DynaReport\/33-series.htm\">Seria de specifica\u021bii 3GPP<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/www.etsi.org\/deliver\/etsi_ts\/133500_133599\/133501\/15.06.00_60\/ts_133501v150600p.pdf\">Arhitectura de securitate 5G<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/www.etsi.org\/deliver\/etsi_ts\/123500_123599\/123501\/15.02.00_60\/ts_123501v150200p.pdf\">Arhitectura sistemului 5G<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/5G\">Wiki 5G<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/itechinfo.ru\/content\/%D0%B0%D1%80%D1%85%D0%B8%D1%82%D0%B5%D0%BA%D1%82%D1%83%D1%80%D0%B0-%D1%81%D0%B5%D1%82%D0%B8-5g\">Note privind arhitectura 5G<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/www.riverpublishers.com\/journal\/journal_articles\/RP_Journal_2245-800X_619.pdf\">Prezentare general\u0103 a securit\u0103\u021bii 5G<\/a><\/noindex><br \/>\n<br \/>Sursa: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/481446\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041e\u0447\u0435\u0432\u0438\u0434\u043d\u043e, \u0431\u0440\u0430\u0442\u044c\u0441\u044f \u0437\u0430 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0443 \u043d\u043e\u0432\u043e\u0433\u043e \u0441\u0442\u0430\u043d\u0434\u0430\u0440\u0442\u0430 \u0441\u0432\u044f\u0437\u0438, \u043d\u0435 \u0434\u0443\u043c\u0430\u044f \u043e \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c\u0430\u0445 \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0435\u043d\u0438\u044f \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438, \u2014 \u0434\u0435\u043b\u043e \u043d\u0435\u043e\u0431\u044b\u0447\u0430\u0439\u043d\u043e \u0441\u043e\u043c\u043d\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0435 \u0438 \u0431\u0435\u0441\u043f\u043e\u043b\u0435\u0437\u043d\u043e\u0435. \u0410\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u0430 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 5G \u2014 \u0441\u043e\u0432\u043e\u043a\u0443\u043f\u043d\u043e\u0441\u0442\u044c \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c\u043e\u0432 \u0438 \u043f\u0440\u043e\u0446\u0435\u0434\u0443\u0440 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438, \u0440\u0435\u0430\u043b\u0438\u0437\u043e\u0432\u0430\u043d\u043d\u044b\u0445 \u0432 \u0441\u0435\u0442\u044f\u0445 5-\u0433\u043e \u043f\u043e\u043a\u043e\u043b\u0435\u043d\u0438\u044f \u0438 \u043e\u0445\u0432\u0430\u0442\u044b\u0432\u0430\u044e\u0449\u0438\u0445 \u0432\u0441\u0435 \u043a\u043e\u043c\u043f\u043e\u043d\u0435\u043d\u0442\u044b \u0441\u0435\u0442\u0438, \u043d\u0430\u0447\u0438\u043d\u0430\u044f \u043e\u0442 \u044f\u0434\u0440\u0430 \u0438 \u0437\u0430\u043a\u0430\u043d\u0447\u0438\u0432\u0430\u044f \u0440\u0430\u0434\u0438\u043e\u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441\u0430\u043c\u0438. \u0421\u0435\u0442\u0438 5-\u043e\u0433\u043e \u043f\u043e\u043a\u043e\u043b\u0435\u043d\u0438\u044f \u044f\u0432\u043b\u044f\u044e\u0442\u0441\u044f, \u043f\u043e \u0441\u0443\u0442\u0438 \u0441\u0432\u043e\u0435\u0439, \u044d\u0432\u043e\u043b\u044e\u0446\u0438\u0435\u0439 \u0441\u0435\u0442\u0435\u0439 4-\u043e\u0433\u043e \u043f\u043e\u043a\u043e\u043b\u0435\u043d\u0438\u044f [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-54348","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2.1 - aioseo.com -->\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/vvedenie-v-arhitekturu-bezopasnosti-5g-nfv-klyuchi-i-2-autentifikatsii\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u0432 \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u0443 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 5G: NFV, \u043a\u043b\u044e\u0447\u0438 \u0438 2 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 | ProHoster\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/vvedenie-v-arhitekturu-bezopasnosti-5g-nfv-klyuchi-i-2-autentifikatsii\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-12-23T21:00:00+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-02-18T11:02:21+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Introducere \u00een arhitectura de securitate 5G: NFV, chei \u0219i 2 autentific\u0103ri | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/vvedenie-v-arhitekturu-bezopasnosti-5g-nfv-klyuchi-i-2-autentifikatsii","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u0432 \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u0443 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 5G: NFV, \u043a\u043b\u044e\u0447\u0438 \u0438 2 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 | ProHoster","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/vvedenie-v-arhitekturu-bezopasnosti-5g-nfv-klyuchi-i-2-autentifikatsii","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-12-23T21:00:00+00:00","article:modified_time":"2020-02-18T11:02:21+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"54348","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-24 11:00:25","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 20:07:25","updated":"2026-01-24 11:00:25","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/54348","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=54348"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/54348\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=54348"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=54348"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=54348"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}