{"id":31068,"date":"2019-10-31T21:39:16","date_gmt":"2019-10-31T18:39:16","guid":{"rendered":"https:\/\/prohoster.info\/blog\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-pervaya-uderzhanie\/"},"modified":"2019-10-31T21:39:16","modified_gmt":"2019-10-31T18:39:16","slug":"kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-pervaya-uderzhanie","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-pervaya-uderzhanie","title":{"rendered":"Cum s\u0103 preiei controlul asupra infrastructurii de re\u021bea. Capitolul \u00eent\u00e2i. Men\u021binerea","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><i>Acest articol este primul dintr-o serie intitulat\u0103 \u201eCum s\u0103-\u021bi controlezi infrastructura de re\u021bea\u201d. Con\u021binutul tuturor articolelor din serie \u0219i linkurile pot fi g\u0103site <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/447008\/\">aici<\/a><\/noindex><\/i>.<\/p>\n<p>Accept c\u0103 exist\u0103 suficiente companii unde o simpl\u0103 re\u021bea timp de o or\u0103 sau chiar o zi nu este critic\u0103. Din p\u0103cate sau din fericire, nu am avut ocazia s\u0103 lucrez \u00een astfel de locuri. Totu\u0219i, re\u021belele sunt diferite, cerin\u021bele sunt diferite, abord\u0103rile sunt diferite \u0219i totu\u0219i, \u00eentr-un fel sau altul, lista de mai jos va fi \u00een multe cazuri de fapt, un \u201emust-do\u201d.<\/p>\n<p>A\u0219adar, condi\u021biile ini\u021biale. <\/p>\n<p>E\u0219ti la un nou loc de munc\u0103 sau ai fost promovat sau ai decis s\u0103 prive\u0219ti diferit \u00eendatoririle tale. Re\u021beaua companiei este responsabilitatea ta. Pentru tine, aceasta este \u00eentr-o mare m\u0103sur\u0103 o provocare \u0219i o noutate, ceea ce justific\u0103 \u00eentr-o oarecare m\u0103sur\u0103 tonul mentorului al acestui articol :). Dar, sper c\u0103 articolul poate fi de asemenea util pentru orice inginer de re\u021bea.<\/p>\n<p>Primul t\u0103u obiectiv strategic este s\u0103 \u00eenve\u021bi s\u0103 faci fa\u021b\u0103 entropiei \u0219i s\u0103 men\u021bii nivelul serviciului oferit. <\/p>\n<p>Multe dintre sarcinile descrise mai jos pot fi rezolvate prin diverse mijloace. \u00cen mod inten\u021bionat nu abordez tema implement\u0103rii tehnice, deoarece, \u00een principiu, adesea nu conteaz\u0103 cum ai rezolvat o anumit\u0103 problem\u0103, ci conteaz\u0103 cum folose\u0219ti acea solu\u021bie \u0219i dac\u0103 o folose\u0219ti de fapt. De exemplu, nu este prea util sistemul t\u0103u de monitorizare bine construit profesional, dac\u0103 nu te ui\u021bi acolo \u0219i nu reac\u021bionezi la alerte.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h2>Echipament<\/h2>\n<p>\nMai \u00eent\u00e2i trebuie s\u0103 \u00een\u021belegi unde sunt cele mai mari riscuri.<\/p>\n<p>Din nou, poate fi diferit. Accept c\u0103 undeva, de exemplu, ar putea fi probleme de securitate, iar \u00een alt\u0103 parte ar putea fi probleme legate de continuitatea serviciului, iar \u00een alt\u0103 parte, poate fi altceva. De ce nu?<\/p>\n<p>S\u0103 presupunem, pentru certitudine, c\u0103 este vorba despre continuitatea serviciului (a\u0219a a fost \u00een toate companiile \u00een care am lucrat).<\/p>\n<p>Atunci trebuie s\u0103 \u00eencepi cu echipamentul. Iat\u0103 lista de subiecte la care trebuie s\u0103 acorzi aten\u021bie:<\/p>\n<ul>\n<li>clasificarea echipamentului \u00een func\u021bie de gradul de criticitate<\/li>\n<li>rezervarea echipamentului critic<\/li>\n<li>asisten\u021b\u0103, licen\u021be<\/li>\n<\/ul>\n<p>\nTrebuie s\u0103 lua\u021bi \u00een considerare posibilele variante de defec\u021biuni, mai ales cu echipamentele aflate \u00een v\u00e2rful clasific\u0103rii dumneavoastr\u0103 de criticitate. De obicei, se neglijeaz\u0103 probabilitatea de probleme duble; altfel, solu\u021bia \u0219i suportul pot deveni nemeritat de scumpe, dar \u00een cazul elementelor cu adev\u0103rat critice ale re\u021belei, a c\u0103ror defec\u021biune poate afecta semnificativ afacerea, trebuie s\u0103 lua\u021bi \u00een considerare \u0219i acest aspect.<\/p>\n<blockquote><p><b>Exemplu<\/b><\/p>\n<p>S\u0103 presupunem c\u0103 vorbim despre switch-ul principal din data center. <\/p>\n<p>Av\u00e2nd \u00een vedere c\u0103 ne-am \u00een\u021beles c\u0103 continuitatea serviciului este cel mai important criteriu, este logic s\u0103 asigura\u021bi o rezervare \u201efierbinte\u201d (redundancy) a acestui echipament. Dar asta nu este tot. Trebuie s\u0103 determina\u021bi \u0219i c\u00e2t timp, \u00een cazul defec\u021biunii primului switch, este acceptabil pentru dumneavoastr\u0103 s\u0103 func\u021biona\u021bi cu un singur switch r\u0103mas, av\u00e2nd \u00een vedere riscul ca \u0219i acesta s\u0103 se defecteze.<\/p>\n<p><b>Important! Nu trebuie s\u0103 lua\u021bi aceast\u0103 decizie singuri. Trebuie s\u0103 descrie\u021bi riscurile, solu\u021biile posibile \u0219i costurile conducerii sau managementului companiei. Deciziile trebuie s\u0103 le ia ei.<\/b><\/p>\n<p>Astfel, dac\u0103 s-a decis c\u0103, av\u00e2nd \u00een vedere o probabilitate mic\u0103 de defec\u021biune dubl\u0103, func\u021bionarea timp de 4 ore pe un singur switch este acceptabil\u0103, pute\u021bi opta pur \u0219i simplu pentru un suport corespunz\u0103tor (\u00een care echipamentul va fi \u00eenlocuit \u00een termen de 4 ore). <\/p>\n<p>Dar exist\u0103 riscul s\u0103 nu ajung\u0103. Din p\u0103cate, am fost odat\u0103 \u00een aceast\u0103 situa\u021bie. \u00cen loc de patru ore, echipamentul a venit dup\u0103 o s\u0103pt\u0103m\u00e2n\u0103!!!<\/p>\n<p>De aceea, acest risc trebuie discutat \u0219i, poate, ar fi mai bine s\u0103 cump\u0103ra\u021bi un alt switch (al treilea) \u0219i s\u0103-l p\u0103stra\u021bi \u00een standby (\u201erezervare rece\u201d) sau s\u0103-l utiliza\u021bi \u00een scopuri de laborator.<\/p><\/blockquote>\n<p>\n<b>Important! Crea\u021bi o list\u0103 cu toate suporturile pe care le ave\u021bi, \u00eempreun\u0103 cu datele de expirare, \u0219i ad\u0103uga\u021bi-le \u00een calendar, astfel \u00eenc\u00e2t cu cel pu\u021bin o lun\u0103 \u00eenainte s\u0103 primi\u021bi un e-mail care s\u0103 v\u0103 reaminteasc\u0103 c\u0103 trebuie s\u0103 \u00eencepe\u021bi s\u0103 v\u0103 face\u021bi griji cu privire la re\u00eennoirea suportului.<\/b><\/p>\n<p>Nu vi se va ierta dac\u0103 uita\u021bi s\u0103 re\u00eennoi\u021bi suportul \u0219i \u00een ziua urm\u0103toare dup\u0103 ce acesta a expirat, echipamentul dumneavoastr\u0103 se va defecta.<\/p>\n<h2>Lucr\u0103ri de urgen\u021b\u0103<\/h2>\n<p>\nIndiferent ce se \u00eent\u00e2mpl\u0103 \u00een re\u021beaua dumneavoastr\u0103, \u00een mod ideal, trebuie s\u0103 p\u0103stra\u021bi accesul la echipamentul dumneavoastr\u0103 de re\u021bea. <\/p>\n<p><b>Este important! Trebuie s\u0103 ave\u021bi acces la consol\u0103 pentru tot hardware-ul \u0219i acest acces nu trebuie s\u0103 depind\u0103 de func\u021bionalitatea re\u021belei de transmitere a datelor.<\/b><\/p>\n<p>De asemenea, trebuie s\u0103 anticipa\u021bi posibilele scenarii negative \u0219i s\u0103 documenta\u021bi ac\u021biunile necesare. Accesibilitatea acestui document este de asemenea critic\u0103, a\u0219a c\u0103 acesta trebuie s\u0103 fie nu doar disponibil pe o resurs\u0103 comun\u0103 pentru departament, ci \u0219i salvat local pe calculatoarele inginerilor.<\/p>\n<p>Este obligatoriu s\u0103 existe <\/p>\n<ul>\n<li>informa\u021bii necesare pentru a deschide o cerere de suport la furnizor sau integrator <\/li>\n<li>informa\u021bii despre cum s\u0103 accesa\u021bi orice echipament (consol\u0103, management)<\/li>\n<\/ul>\n<p>\nDe asemenea, poate con\u021bine orice alte informa\u021bii utile, cum ar fi descrierea procedurii de upgrade a diferitelor echipamente \u0219i comenzi de diagnosticare utile.<\/p>\n<h2>Parteneri<\/h2>\n<p>\nAcum trebuie s\u0103 evalua\u021bi riscurile asociate partenerilor. De obicei, sunt<\/p>\n<ul>\n<li>furnizorii de internet \u0219i punctele de schimb de trafic (IX)<\/li>\n<li>furnizorii de canale de comunica\u021bie <\/li>\n<\/ul>\n<p>\nCe \u00eentreb\u0103ri trebuie s\u0103 v\u0103 pune\u021bi? A\u0219a cum s-a \u00eent\u00e2mplat \u0219i cu echipamentele, trebuie s\u0103 lua\u021bi \u00een considerare diverse op\u021biuni ale situa\u021biilor de urgen\u021b\u0103. De exemplu, pentru furnizorii de internet, aceasta poate fi ceva de genul:<\/p>\n<ul>\n<li>ce se va \u00eent\u00e2mpla dac\u0103 furnizorul de internet X nu v\u0103 mai ofer\u0103 serviciul dintr-un anumit motiv? <\/li>\n<li>ave\u021bi suficiente l\u0103\u021bimi de band\u0103 de la ceilal\u021bi furnizori?<\/li>\n<li>c\u00e2t de bun\u0103 va r\u0103m\u00e2ne conectivitatea?<\/li>\n<li>c\u00e2t de independen\u021bi sunt furnizorii dumneavoastr\u0103 de internet \u0219i va provoca o avarie major\u0103 a unuia dintre ei probleme cu ceilal\u021bi?<\/li>\n<li>c\u00e2te intr\u0103ri optice exist\u0103 \u00een centrul dvs. de date? <\/li>\n<li>ce se va \u00eent\u00e2mpla dac\u0103 una dintre intr\u0103ri va fi complet distrus\u0103?<\/li>\n<\/ul>\n<p>\n\u00cen ceea ce prive\u0219te intr\u0103rile, \u00een experien\u021ba mea din dou\u0103 companii diferite, \u00een dou\u0103 loca\u021bii diferite, <a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/ro\/kompaniya\/data-centers\/\"   title=\"de \u00eencredere\" data-wpil-keyword-link=\"linked\"  data-wpil-monitor-id=\"4668\">de \u00eencredere<\/a> un excavator a distrus pu\u021burile \u0219i, doar dintr-o minune, fibra noastr\u0103 optic\u0103 a fost nelovit\u0103. Nu este un caz at\u00e2t de rar.<\/p>\n<p>\u0218i, desigur, trebuie s\u0103 nu doar s\u0103 pune\u021bi aceste \u00eentreb\u0103ri, ci, din nou, cu sprijinul conducerii, s\u0103 asigura\u021bi o solu\u021bie acceptabil\u0103 \u00een orice situa\u021bie. <\/p>\n<h2>Backup<\/h2>\n<p>\nUrm\u0103toarea prioritate poate fi backup-ul configura\u021biilor hardware-ului. \u00cen orice caz, acesta este un aspect foarte important. Nu voi enumera cazurile \u00een care pute\u021bi pierde configura\u021bia, mai bine face\u021bi backup regulat \u0219i nu g\u00e2ndi\u021bi la asta. \u00cen plus, backup-ul regulat poate fi foarte util \u00een controlul modific\u0103rilor.<\/p>\n<p><b>Important! Make backups daily. This is not such a large amount of data that you should skimp on it. In the morning, the on-duty engineer (or you) should receive a report from the system clearly indicating whether the backup was successful or not, and in the case of an unsuccessful backup, the problem should be resolved or a ticket should be created (see the processes of the network department). <\/b><\/p>\n<h2>Versiuni software<\/h2>\n<p>\nThe question of whether to upgrade the software of the equipment is not so straightforward. On one hand, old versions come with known bugs and vulnerabilities, but on the other hand, new software is not always a painless upgrade process, and new bugs and vulnerabilities can arise.<\/p>\n<p>Here, you need to find the optimal solution. A few obvious recommendations:<\/p>\n<ul>\n<li>only install stable versions<\/li>\n<li>you still shouldn\u2019t stick to very old versions of the software<\/li>\n<li>create a table with information on which software is installed where<\/li>\n<li>periodically read reports on vulnerabilities and bugs in software versions, and in case of critical issues, consider upgrading<\/li>\n<\/ul>\n<p>\nAt this stage, having console access to the equipment, support information, and a description of the upgrade procedure, you are basically ready for this step. The ideal situation is when you have lab equipment where you can test the entire procedure, but unfortunately, that is not often the case.<\/p>\n<p>In the case of critical equipment, you can contact the vendor support for assistance with the upgrade.<\/p>\n<h2>Sistem de ticketing<\/h2>\n<p>\nNow you can look around. You need to establish processes for interaction with other departments and within your own department. <\/p>\n<p>This may not be mandatory (for example, if your company is small), but I would highly recommend organizing work in such a way that all external and internal tasks go through the ticketing system.<\/p>\n<p>The ticketing system is essentially your interface for internal and external communications, and you should describe this interface with sufficient detail.<\/p>\n<p>Let's take an important and commonly encountered task of granting access as an example. I will outline an algorithm that worked excellently in one company.<\/p>\n<blockquote><p><b>Exemplu<\/b><\/p>\n<p>S\u0103 \u00eencepem prin a spune c\u0103 de multe ori clien\u021bii formuleaz\u0103 cerin\u021bele de acces \u00eentr-un limbaj neclar pentru inginerii de re\u021bea, adic\u0103, \u00een jargonul aplica\u021biei, de exemplu, \u201eofer\u0103-mi acces la 1C\u201d. <\/p>\n<p>De aceea, niciodat\u0103 nu am acceptat cereri direct de la astfel de utilizatori. <br \/>\nIar aceasta a fost prima cerin\u021b\u0103.<\/p>\n<ul>\n<li>Cererea de acces trebuie s\u0103 vin\u0103 din partea departamentelor tehnice (\u00een cazul nostru, de la inginerii Unix, Windows, sau helpdesk).<\/li>\n<\/ul>\n<p>\nA doua cerin\u021b\u0103 este c\u0103 <\/p>\n<ul>\n<li>acest acces trebuie s\u0103 fie protocolat (de c\u0103tre departamentul tehnic de la care am primit cererea) \u0219i ca parte a cererii primim un link c\u0103tre acest acces protocolat. <\/li>\n<\/ul>\n<p>\nForma acestei cereri trebuie s\u0103 fie clar\u0103 pentru noi, adic\u0103 <\/p>\n<ul>\n<li>cererea trebuie s\u0103 con\u021bin\u0103 informa\u021bii despre din ce subre\u021bea \u0219i \u00een ce subre\u021bea trebuie s\u0103 se deschid\u0103 accesul, precum \u0219i despre protocol \u0219i (\u00een caz de tcp\/udp) porturi.<\/li>\n<\/ul>\n<p>\nDe asemenea, trebuie s\u0103 fie specificat <\/p>\n<ul>\n<li>descrierea motivului pentru care acest acces este deschis.<\/li>\n<li>Provizoriu sau permanent (dac\u0103 este provizoriu, atunci p\u00e2n\u0103 la ce dat\u0103).<\/li>\n<\/ul>\n<p>\n\u0218i un punct foarte important este aprob\u0103rile<\/p>\n<ul>\n<li>de la \u0219eful departamentului care a ini\u021biat accesul (de exemplu, de la contabilitate).<\/li>\n<li>De la \u0219eful departamentului tehnic, de unde a venit aceast\u0103 cerere c\u0103tre departamentul de re\u021bea (de exemplu, helpdesk).<\/li>\n<\/ul>\n<p>\n\u00cen acest context, \u201eproprietarul\u201d acestui acces este considerat \u0219eful departamentului care a ini\u021biat accesul (contabilitatea \u00een exemplul nostru) \u0219i el este responsabil pentru men\u021binerea actualiz\u0103rii paginii cu accesuri protocolate pentru acest departament.\n<\/p><\/blockquote>\n<p><\/p>\n<h2>Logare<\/h2>\n<p>\nAceasta este o zon\u0103 \u00een care te po\u021bi \u00eeneca. Dar dac\u0103 dore\u0219ti s\u0103 implementezi o abordare proactiv\u0103, trebuie s\u0103 \u00eenve\u021bi s\u0103 gestionezi acest flux de date.<\/p>\n<blockquote><p>Iat\u0103 c\u00e2teva recomand\u0103ri practice:<\/p>\n<ul>\n<li>verificarea log-urilor trebuie s\u0103 fie zilnic\u0103.<\/li>\n<li>\u00cen cazul unei verific\u0103ri planificate (nu \u00een caz de situa\u021bie de urgen\u021b\u0103), po\u021bi s\u0103 te limitezi la nivelurile de severitate (severity) 0, 1, 2 \u0219i s\u0103 adaugi modele preferate din alte niveluri dac\u0103 crezi c\u0103 este necesar.<\/li>\n<li>Scrie un script care analizeaz\u0103 log-urile \u0219i ignor\u0103 acele log-uri a c\u0103ror modele le-ai ad\u0103ugat \u00een lista de ignoran\u021b\u0103.<\/li>\n<\/ul>\n<p>\nAceast\u0103 abordare va permite, \u00een timp, s\u0103 creezi o list\u0103 de ignoran\u021b\u0103 a log-urilor care nu te intereseaz\u0103, l\u0103s\u00e2nd doar acelea pe care le consideri cu adev\u0103rat importante.<br \/>\nLa noi a func\u021bionat excelent.<\/p><\/blockquote>\n<p><\/p>\n<h2>Monitorizare<\/h2>\n<p>\nNu este o raritate ca o companie s\u0103 nu aib\u0103 un sistem de monitorizare. Pute\u021bi, de exemplu, s\u0103 v\u0103 baza\u021bi pe log-uri, dar echipamentul poate pur \u0219i simplu s\u0103 \u00abmoar\u0103\u00bb, f\u0103r\u0103 s\u0103 reu\u0219easc\u0103 s\u0103 \u00abspun\u0103\u00bb nimic, sau un pachet UDP din protocolul syslog poate s\u0103 se piard\u0103 \u0219i s\u0103 nu ajung\u0103. \u00cen general, desigur, monitorizarea activ\u0103 este important\u0103 \u0219i necesar\u0103.<\/p>\n<blockquote><p>Dou\u0103 exemple foarte solicitate \u00een practica mea:<\/p>\n<ul>\n<li>monitorizarea \u00eenc\u0103rc\u0103rii canalelor de comunicare, a leg\u0103turilor critice (de exemplu, conexiunea la furnizorii de servicii). Aceasta permite s\u0103 observa\u021bi proactiv o poten\u021bial\u0103 problem\u0103 de degradare a serviciului din cauza pierderii de trafic \u0219i, prin urmare, s\u0103 o evita\u021bi.<\/li>\n<li>graficele, construite pe baza NetFlow. Acestea permit identificarea u\u0219oar\u0103 a anomaliilor \u00een trafic \u0219i sunt foarte utile pentru detectarea unor tipuri simple, dar semnificative de atacuri cibernetice.<\/li>\n<\/ul>\n<\/blockquote>\n<p>\n<b>Important! Configura\u021bi notific\u0103rile SMS pentru cele mai critice evenimente. Acest lucru se aplic\u0103 at\u00e2t monitoriz\u0103rii, c\u00e2t \u0219i log\u0103rii. Dac\u0103 nu ave\u021bi un schimb de gard\u0103, atunci mesajele SMS ar trebui s\u0103 ajung\u0103 \u0219i \u00een afara orelor de program. <\/b><\/p>\n<p>Planifica\u021bi procesul astfel \u00eenc\u00e2t s\u0103 nu trezi\u021bi to\u021bi inginerii. La noi, pentru aceasta, am avut un inginer de gard\u0103.<\/p>\n<h2>Controlul modific\u0103rilor<\/h2>\n<p>\nDin punctul meu de vedere, nu este neap\u0103rat s\u0103 controla\u021bi toate modific\u0103rile. Dar, \u00een orice caz, trebuie s\u0103 ave\u021bi posibilitatea, dac\u0103 este necesar, s\u0103 g\u0103si\u021bi u\u0219or cine \u0219i de ce a efectuat anumite modific\u0103ri \u00een re\u021bea. <\/p>\n<blockquote><p>C\u00e2teva sfaturi:<\/p>\n<ul>\n<li>utiliza\u021bi un sistem de tichet pentru o descriere detaliat\u0103 a ceea ce s-a f\u0103cut \u00een cadrul acestui tichet, de exemplu, copiind configura\u021bia aplicat\u0103 \u00een tichet.<\/li>\n<li>folosi\u021bi func\u021bionalit\u0103\u021bile comentariilor pe echipamentele de re\u021bea (de exemplu, commit comment pe Juniper). Pute\u021bi nota num\u0103rul tichetului.<\/li>\n<li>utiliza\u021bi diff-urile backup-urilor voastre de configura\u021bie.<\/li>\n<\/ul>\n<p>\nPute\u021bi introduce acest lucru ca un proces, revizuind zilnic toate tichetele pentru modific\u0103ri.<\/p><\/blockquote>\n<p><\/p>\n<h2>Procese<\/h2>\n<p>\nTrebuie s\u0103 formaliza\u021bi \u0219i s\u0103 descrie\u021bi procesele din echipa voastr\u0103. Dac\u0103 a\u021bi ajuns la acest punct, atunci \u00een echipa voastr\u0103 ar trebui s\u0103 func\u021bioneze deja cel pu\u021bin urm\u0103toarele procese:<\/p>\n<p>Procese zilnice:<\/p>\n<ul>\n<li>lucrul cu tichetele<\/li>\n<li>lucrul cu log-urile<\/li>\n<li>controlul modific\u0103rilor<\/li>\n<li>lista de verificare zilnic\u0103<\/li>\n<\/ul>\n<p>\nProcese anuale:<\/p>\n<ul>\n<li>re\u00eennoirea garan\u021biilor, licen\u021belor<\/li>\n<\/ul>\n<p>\nProcese asincrone:<\/p>\n<ul>\n<li>reac\u021bia la diferite situa\u021bii de urgen\u021b\u0103<\/li>\n<\/ul>\n<p><\/p>\n<h2>Concluzia primei p\u0103r\u021bi<\/h2>\n<p>\nA\u021bi observat c\u0103 p\u00e2n\u0103 acum nu discut\u0103m despre configurarea re\u021belei, design, protocoalele de re\u021bea, rutare sau securitate\u2026 Este ceva \u00een jur. Dar, de\u0219i acestea pot p\u0103rea plictisitoare, ele sunt elemente foarte importante ale activit\u0103\u021bii unei divizii de re\u021bea. <\/p>\n<p>P\u00e2n\u0103 acum, a\u0219a cum observa\u021bi, nu a\u021bi \u00eembun\u0103t\u0103\u021bit nimic \u00een re\u021beaua dumneavoastr\u0103. Dac\u0103 existau vulnerabilit\u0103\u021bi \u00een securitate, acestea au r\u0103mas neschimbate; dac\u0103 designul era slab, acesta a r\u0103mas. P\u00e2n\u0103 nu a\u021bi aplicat abilit\u0103\u021bile \u0219i cuno\u0219tin\u021bele de inginer de re\u021bea, pe care probabil le-a\u021bi acumulat cu mult timp, efort \u0219i, uneori, bani. Dar mai \u00eent\u00e2i trebuie s\u0103 construi\u021bi (sau s\u0103 \u00eent\u0103ri\u021bi) funda\u021bia, iar abia apoi s\u0103 v\u0103 ocupa\u021bi de construc\u021bie.<\/p>\n<p>Despre cum s\u0103 c\u0103uta\u021bi \u0219i s\u0103 remedia\u021bi erorile, \u0219i apoi s\u0103 \u00eembun\u0103t\u0103\u021bi\u021bi infrastructura dumneavoastr\u0103 \u2013 despre asta vorbesc urm\u0103toarele p\u0103r\u021bi.<\/p>\n<p>Desigur, nu este necesar s\u0103 face\u021bi totul \u00een ordine secven\u021bial\u0103. Timpul poate fi critic. Face\u021bi lucrurile \u00een paralel, dac\u0103 resursele permit.<\/p>\n<p>\u0218i un aspect important. Comunica\u021bi, \u00eentreba\u021bi, consulta\u021bi-v\u0103 cu echipa dumneavoastr\u0103. \u00cen cele din urm\u0103, ei sunt cei care trebuie s\u0103 \u00eentre\u021bin\u0103 \u0219i s\u0103 implementeze toate acestea.<br \/>\n<br \/>Sursa: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/433614\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u042d\u0442\u0430 \u0441\u0442\u0430\u0442\u044c\u044f \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043f\u0435\u0440\u0432\u043e\u0439 \u0432 \u0446\u0438\u043a\u043b\u0435 \u0441\u0442\u0430\u0442\u0435\u0439 \u00ab\u041a\u0430\u043a \u0432\u0437\u044f\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043f\u043e\u0434 \u0441\u0432\u043e\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c\u00bb. \u0421\u043e\u0434\u0435\u0440\u0436\u0430\u043d\u0438\u0435 \u0432\u0441\u0435\u0445 \u0441\u0442\u0430\u0442\u0435\u0439 \u0446\u0438\u043a\u043b\u0430 \u0438 \u0441\u0441\u044b\u043b\u043a\u0438 \u043c\u043e\u0436\u043d\u043e \u043d\u0430\u0439\u0442\u0438 \u0437\u0434\u0435\u0441\u044c. \u0412\u043f\u043e\u043b\u043d\u0435 \u0434\u043e\u043f\u0443\u0441\u043a\u0430\u044e, \u0447\u0442\u043e \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u0435\u0442 \u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e\u0435 \u043a\u043e\u043b\u0438\u0447\u0435\u0441\u0442\u0432\u043e \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0439, \u0433\u0434\u0435 \u043f\u0440\u043e\u0441\u0442\u043e\u0439 \u0441\u0435\u0442\u0438 \u0432 \u043e\u0434\u0438\u043d \u0447\u0430\u0441 \u0438\u043b\u0438 \u0434\u0430\u0436\u0435 \u043e\u0434\u0438\u043d \u0434\u0435\u043d\u044c \u043d\u0435 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043a\u0440\u0438\u0442\u0438\u0447\u043d\u044b\u043c. \u041c\u043d\u0435, \u043a \u0441\u043e\u0436\u0430\u043b\u0435\u043d\u0438\u044e \u0438\u043b\u0438 \u043a \u0441\u0447\u0430\u0441\u0442\u044c\u044e, \u043d\u0435 \u0434\u043e\u0432\u0435\u043b\u043e\u0441\u044c \u0440\u0430\u0431\u043e\u0442\u0430\u0442\u044c \u0432 \u0442\u0430\u043a\u0438\u0445 \u043c\u0435\u0441\u0442\u0430\u0445. [&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-31068","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=\"description\" content=\"\u042d\u0442\u0430 \u0441\u0442\u0430\u0442\u044c\u044f \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043f\u0435\u0440\u0432\u043e\u0439 \u0432 \u0446\u0438\u043a\u043b\u0435 \u0441\u0442\u0430\u0442\u0435\u0439 \u00ab\u041a\u0430\u043a \u0432\u0437\u044f\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043f\u043e\u0434 \u0441\u0432\u043e\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c\u00bb.\" \/>\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\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-pervaya-uderzhanie\" \/>\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\u041a\u0430\u043a \u0432\u0437\u044f\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043f\u043e\u0434 \u0441\u0432\u043e\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c. \u0413\u043b\u0430\u0432\u0430 \u043f\u0435\u0440\u0432\u0430\u044f. \u0423\u0434\u0435\u0440\u0436\u0430\u043d\u0438\u0435 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u042d\u0442\u0430 \u0441\u0442\u0430\u0442\u044c\u044f \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043f\u0435\u0440\u0432\u043e\u0439 \u0432 \u0446\u0438\u043a\u043b\u0435 \u0441\u0442\u0430\u0442\u0435\u0439 \u00ab\u041a\u0430\u043a \u0432\u0437\u044f\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043f\u043e\u0434 \u0441\u0432\u043e\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c\u00bb.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-pervaya-uderzhanie\" \/>\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-10-31T18:39:16+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:39:16+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\udd47Cum s\u0103 preiei controlul asupra infrastructurii de re\u021bea. Capitolul \u00eent\u00e2i. Men\u021binere | ProHoster","description":"Acest articol este primul dintr-o serie de articole intitulate \u201eCum s\u0103 preiei controlul asupra infrastructurii de re\u021bea\u201d.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-pervaya-uderzhanie","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\u041a\u0430\u043a \u0432\u0437\u044f\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043f\u043e\u0434 \u0441\u0432\u043e\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c. \u0413\u043b\u0430\u0432\u0430 \u043f\u0435\u0440\u0432\u0430\u044f. \u0423\u0434\u0435\u0440\u0436\u0430\u043d\u0438\u0435 | ProHoster","og:description":"\u042d\u0442\u0430 \u0441\u0442\u0430\u0442\u044c\u044f \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043f\u0435\u0440\u0432\u043e\u0439 \u0432 \u0446\u0438\u043a\u043b\u0435 \u0441\u0442\u0430\u0442\u0435\u0439 \u00ab\u041a\u0430\u043a \u0432\u0437\u044f\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043f\u043e\u0434 \u0441\u0432\u043e\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c\u00bb.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-pervaya-uderzhanie","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-10-31T18:39:16+00:00","article:modified_time":"2019-10-31T18:39:16+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"31068","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-21 04:23:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 03:24:13","updated":"2026-01-21 04:23:19","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\/31068","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=31068"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/31068\/revisions"}],"predecessor-version":[{"id":164546,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/31068\/revisions\/164546"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=31068"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=31068"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=31068"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}