HARDVERSKO - SOFTVERSKO REŠENJE
ISPUNJAVA ZAHTEVE ISO 27000 I ISO 27001
SUBLANDIA je sistem izrađen da odgovori na zahteve ISO 27000 i
ISO 27001
Podrazumeva hardversko - softversko rešenje namenjeno Subtitling industriji.
SUBLANDIA je sačinjena od softverskih rešenja podržanih sa 2 ili više serverskih sistema u zavisnosti od zahteva i potreba.
U trenutnoj verziji, SUBLANDIA koristi desktop verziju open source softvera. Web based onlajn softversko rešenje je u fazi izrade.
Nova verzija softvera za subtitling je 50% izrađena i uskoro će proći prvu fazu testiranja samog rada i stabilnosti.
Trenutna verzija softvera biće zamenjena novom bez prekida tokom rada korisnika.
Sistem za automatsku transkripciju SUBLANDIA ima u Standardnom i Optimalnom paketu.
Trenutni softver za subtitling ima ugrađenu opciju za automatsku transkripciju koja je onemogućena jer u mnogome smanjuje radne performanse samog sistema. U Optimalnom paketu, sistem za transkripciju je namenski dizajniran i odvojen od softvera za subtitling i prilagođen je za upotrebu unutar kompanije bez mogućnosti pristupa radnim materijalima trećih lica. Ovaj sistem olakšava rad prevodiocima, rasterećuje Radni sistem i obezbeđuje adekvatnu zaštitu podataka.
Ovaj sistem se uključuje u rad isključivo prilikom katastrofa, kada je funkcionisanje Radnog i Bekap sistema u potpunosti onemogućeno. Uključivanje sistema za oporavak od katastrofe vrši se u roku 24h od nastanka katastrofalnog događaja.
Bekap radnih materijala je moguć uz bilo koji SUBLANDIA paket. Podrazmeva bekap na hard diskove. Količina i karakteristike samih hard diskova se određuju u zavisnosti od potreba i zahteva.
TABELARNI PRIKAZ ODGOVORA SUBLANDIA SISTEMA
NA ZAHTEVE ISO 27000 I ISO 27001
3.5. Are external vulnerability scans conducted by an internal team on a monthly basis? |
![]() |
Uz instalaciju sistema, prvog meseca se testiranje podrazumeva. Za ostala mesečna testiranja - dogovor. |
3.6. Are internal vulnerability scans conducted on all networks monthly? |
![]() |
Uz instalaciju sistema, prvog meseca se testiranje podrazumeva. Za ostala mesečna testiranja - dogovor. |
4.4. Do you have policies and procedures for managing of user, administrator, and service accounts? |
![]() |
|
4.6. Do you manage remote access? | ![]() |
|
4.7. Do you manage access permissions and authorizations, incorporating the principles of least privilege and separation of duties? |
![]() |
|
4.8. Are users, devices, and other assets authenticated (e.g. single-factor, multi-factor)? |
![]() |
Multi-factor |
4.9. Do you restrict and control the use of privileged access rights? |
![]() |
|
4.10. Do you have a process to rename administrator user IDs and change the password of default accounts? |
![]() |
|
4.11. Does your password policy includes the minimum requirement of a secured password (e.g. minimum password length of 8 characters, alphanumeric, maximum password age, maximum logon attempts, password history, etc)? |
![]() |
|
4.12. Do you limit the use of generic system administrator accounts (e.g. root, administrator) to only special situations which require the use of these accounts? |
![]() |
|
4.13. Do you restrict users from being able to grant themselves access to information systems? |
![]() |
|
4.14. Do you log administrator and service account activities? |
![]() |
|
4.16. Do you perform periodic access review for dormant access accounts in the domain controller? |
![]() |
|
5.1. Do you protect data at-rest and in-transit? |
![]() |
|
5.2. Do you implement protections against data leaks? |
![]() |
|
5.3. Are the development and testing environment(s) separate from the production environment? |
![]() |
|
5.4. Do you implement e-mail content filtering? |
![]() |
|
5.4.1. Does it identify phishing e-mails and spam? |
![]() |
|
5.4.2. Does it block e-mails from blacklisted domains? |
![]() |
|
5.4.3. Does it restrict file sizes? | ![]() |
|
5.4.4. Do you implement content and network traffic filtering? |
![]() |
|
5.4.5. Does it filter unauthorized file sharing and storage hubs? |
![]() |
|
5.6. Do you have an e-mail encryption system, i.e. secure e-mail application or service to encrypt sensitive data in e-mails or attachments? |
![]() |
|
***** 5.7. Are computer drives encrypted with FileVault or Bitlocker? ***** |
![]() |
Sistem je enkriptovan sa nativnom ZFS enkripcijom pošto se radi o Linux OS... Bitlocker je za WinOS, FileVault je za MacOS!!! |
5.8. Do you block the optical media burners on all content/production workstations (with the exception of systems used for content transfer/ingest)? |
![]() |
Nema optičkih uređaja |
5.9. Do you block access to C: drive for storage on all content/production workstations (with the exception of systems used for content transfer/ingest)? |
![]() |
Ne postoji C: disk. |
6.2. Do you have a firewall protecting the perimeter of your facility’s IT infrastructure? |
![]() |
|
6.2.1. Can firewalls be managed remotely using a secure VPN / encrypted tunnel set up and are sessions logged and monitored? |
![]() |
|
6.2.2. Does your firewall conduct deep packet inspections and have the ability to keep up with upload and download traffic? |
![]() |
|
6.2.3. Are firewall rules reviewed periodically and at least every six months? |
![]() |
|
6.2.4. Are firewalls configured to deny all protocols by default and enable only specific permitted secure protocols to access the WAN and firewall? |
![]() |
|
6.2.5. Do you employ multi-factor authentication for remote access on firewall, IDS/IPS, web portal, collaboration tools, e-mail? |
![]() |
|
6.4. Do you use intrusion detection or prevention systems? |
![]() |
|
6.4.1. Please provide details of the intrusion detection or prevention system used. |
![]() |
Koristimo više sistema za monitoring paketa na mreži. Ovi sistemi pomažu u zaštiti servera od više vrsta napada. Analiziraju Log fajlove, prepoznaju obrasce zlonamernog ponašanja, prilikom detekcije blokiraju IP adrese napadača. Analiziraju mrežni saobraćaj u realnom vremenu, upravljaju se pravilima za prepoznavanje zlonamernih aktivnosti, beleže informacije o pretnjama i preuzimaju akcije. Prate promene u fajlovima i direktorijumima u sistemu, prate dozvole, vlasništva, veličine fajlova, generišu izveštaje o svim promenama. Pored toga, koristi se i antivirus sistem koji proverava svaki preuzet fajl. |
6.5. Do you have a patch management program to ensure that systems and network infrastructure devices (e.g., firewalls, switches, routers) are up-to-date on patches and maintenance releases? |
![]() |
|
6.6. Do you have hardening and configuration requirements in place for networking and computing equipment, including firewalls, routers, switches, servers, workstations, and mobile computing devices? |
![]() |
|
6.7. Do you use antivirus, antispam, or endpoint software? |
![]() |
|
6.7.1. Please describe the antivirus programs or systems in place. |
![]() |
Sistem koristi AV koji služi za detekciju raznih vrsta malvera, uključujući viruse, trojance i druge zlonamerne pretnje. Razvijen je kao alat za skeniranje i zaštitu sistema, posebno u okruženjima kao što su serveri za e-poštu i web serveri. AV dolazi sa nizom alata, uključujući: **Višenitni demon: Ovaj demon omogućava efikasno skeniranje i obradu više zahteva istovremeno. **Komandna linija: AV nudi komandnu liniju za skeniranje fajlova i direktorijuma, što ga čini pogodnim za administratore sistema. **Automatska ažuriranja: AV može automatski ažurirati svoju bazu podataka sa potpisima malvera, što omogućava brzo reagovanje na nove pretnje. AV skenira fajlove i direktorijume koristeći unapred definisane potpise malvera. Kada se otkrije zlonameran sadržaj, korisnik može biti obavešten ili može automatski preduzeti akciju (npr. obrisati ili izolovati zaraženi fajl). Ažuriranje baze podataka: AV redovno ažurira svoju bazu podataka sa potpisima malvera kako bi mogao da prepozna nove pretnje. Ovo se može raditi automatski ili ručno, u zavisnosti od konfiguracije. |
6.13. Do you conduct, maintain and test backups of information? |
![]() |
|
6.14. Do you block the USB / Firewire / Thunderbolt ports on all content/production workstations (with the exception of systems used for content transfer/ingest)? |
![]() |
|
8.4. Is the network monitored to detect potential cybersecurity events? |
![]() |
|
8.9. Do you review user's access rights at regular intervals? |
![]() |
|
8.10. Are detection processes tested? | ![]() |
|
8.11. Is event detection information communicated to appropriate parties? |
![]() |
|
8.16. Do you investigate notifications from detection systems? |
![]() |
|
8.17. Are forensics performed? | ![]() |
Unutar SUBLANDIA sistema da. Van sistema je nadležan MUP RS, Odeljenje za visokotehnološki kriminal |
8.19. Are processes established to receive, analyze and respond to vulnerabilities disclosed to the organization from internal and external sources (e.g internal testing, security bulletins, or security researchers)? |
![]() |
|
8.22. Do you update detection process, response and recovery strategies? |
![]() |
Detekcija Da. Ostalo je stvar organizacije firme. |
10.2. Do you maintain content transfer servers? |
![]() |
|
10.2.1. Are the content transfer servers set up with at least AES 256 bit encryption at rest and in transit? |
![]() |
|
10.2.2. Are the access to content transfer systems limited only to dedicated data I/O (content transfer) staff and access limited based on least privilege? |
![]() |
|
10.2.3. Do you have a process to remove content from content transfer servers/systems immediately after successful transmission or receipt? |
![]() |
|
10.3. Do your web portals employ HTTPS? | ![]() |
|
10.4. Do your web portals avoid the use of persistent cookies or cookies that store credentials in plaintext? |
![]() |
|
10.5. Do you segment and isolate the production/content network from the administrative and wireless networks? |
![]() |
|
10.9. Do you maintain detailed tracking of access to digital content and maintain logs for at least 12 months? |
![]() |
|
10.9.1. What log details are collected? | ![]() |
Beleže se: **Korisničke aktivnosti: Audit logovi beleže aktivnosti korisnika, uključujući prijave i odjave, kao i sve akcije koje korisnici preduzimaju unutar sistema. Ovo može uključivati kreiranje, izmenu ili brisanje podataka. **Promene u sistemu: Sve promene u konfiguraciji sistema, uključujući instalaciju ili deinstalaciju softvera, ažuriranja i promene u postavkama, takođe se beleže. Ovo pomaže u identifikaciji potencijalnih problema ili neovlašćenih promena. **Pristup podacima: Audit logovi prate ko je imao pristup određenim podacima, kada je pristup izvršen i koje su akcije preduzete sa tim podacima. Ovo je posebno važno za zaštitu osetljivih informacija. **Sistemskih događaja: Beleže se različiti sistemski događaji, kao što su greške, upozorenja i obaveštenja. Ovi podaci pomažu u dijagnostikovanju problema i unapređenju performansi sistema. **Network aktivnosti: U nekim slučajevima, audit logovi mogu beležiti mrežne aktivnosti, uključujući dolazne i odlazne veze, kao i pokušaje neovlašćenog pristupa. **Usklađenost i revizija: Audit logovi se koriste za proveru usklađenosti sa standardima i regulativama. Oni pružaju dokumentaciju koja može biti potrebna tokom revizija ili inspekcija. |
10.9.2. How often are the logs reviewed? |
![]() |
Po dogovoru. |
10.10. Do you remove local accounts on systems that handle content? |
![]() |
|
10.11. If local accounts are used, do you change the default user names and passwords? |
![]() |
|
10.23. Do you employ multi-factor authentication for remote access on Content Transfer system? |
![]() |
Ostali zahtevi ISO 27000 i ISO 27001
rešavaju se papirologijom unutar organizacije
TABELARNI PRIKAZ ODGOVORA SUBLANDIA SISTEMA
CONTENT SECURITY BEST PRACTICES
COMMON GUIDELINES
DS-1.0 Separate external network(s)/WAN(s) from the internal network(s) by using stateful inspection firewall(s) with Access Control Lists that prevent unauthorized access to any internal network and with the ability to keep up with upload and download traffic. | ![]() |
|
DS-1.1 Implement a process to review firewall Access Control Lists (ACLs) to confirm configuration settings are appropriate and required by the business every 6 months. | ![]() |
|
DS-1.2 Deny all incoming and outgoing network requests by default. Enable only explicitly defined incoming requests by specific protocol and destination. Enable only explicitly defined outgoing requests by specific protocol and source. | ![]() |
|
DS-1.2.1 Firewalls should be configured to actively alert security members of key security events | ![]() |
|
DS-1.3 Place externally accessible servers (e.g., web servers, remote access servers (e.g., VPN gateways, remote access brokers, etc.) within a DMZ VLAN or a public subnet DMZ within a VPC (Virtual Private Cloud) and not on an internal network. | ![]() |
|
DS-1.6 For onsite, and/or remote facilities, do not allow direct management of the firewall from any external interfaces (i.e., Internet or WAN facing). |
![]() |
|
DS-1.7 Store local backups of network infrastructure / SAN/NAS devices and servers on a server in a secure internal network. | ![]() |
|
DS-1.8 Perform on at least a monthly basis network vulnerability scans of all external IP ranges and hosts and remediate issues. If applicable, the scope of external scans should include any cloud deployments. | ![]() |
|
DS-1.9 Perform on at least an annual basis, penetration testing of all external IP ranges and hosts and remediate issues. | ![]() |
|
DS-1.10 Secure any point-to-point connections by using dedicated, private connections and / or encryption. | ![]() |
|
DS-1.11 Implement a synchronized time service protocol (e.g., Network Time Protocol) to ensure all systems have a common time reference. | ![]() |
|
DS-2.0 Prohibit production network and all systems that process or store digital content from directly accessing the internet, including email. If a business case requires internet access from the production network or from systems that process or store digital content, only approved methods are allowed in the implementation guidance section. |
![]() |
|
DS-2.1 Implement - corporate filtering software or appliances that block the following: • Potential phishing emails • Prohibited file attachments (e.g., Visual Basic scripts, executables, etc.) • File size restrictions limited to 30 MB • Known domains that are sources of malware or viruses |
![]() |
|
DS-2.2 Implement web filtering software or appliances that restrict access to websites known for peer-to-peer file sharing, viruses, hacking or other malicious sites for all corporate devices, regardless of location, and including remote/WFH locations. | ![]() |
|
DS-3.0 Isolate the content / production network from non-production networks (e.g., office network, DMZ, the internet etc.) by means of physical or logical network segmentation. | ![]() |
|
DS-3.2 Remote access into company networks should be restricted following a tiered approach, depending on the level of access required, and whether or not access will be to a content/production network. Access tiers will fall into the following general tiers: Tier 1: Access only to a corporate network or service that doesn’t store content (e.g., VPN to corporate VLAN for file share access, Webmail, Office365, etc.) Tier 2: Remote worker (WFH) access to a content production network via studio approved pixel streaming (e.g., PCoIP, RGS, Parsec, NICE DCV, etc.) to perform post-production, VFX work etc. Tier 3: Restricted VPN administrative access to a production network, to perform maintenance work or approved personnel requiring elevated access to perform their job responsibilities. |
![]() |
|
DS-3.6 Implement a network-based intrusion detection /prevention system (IDS / IPS) to protect the content / production network. Other Basic Border Gateway services (e.g., Gateway Anti-Virus, and URL Filtering) should also be enabled. | ![]() |
|
DS-3.9 Conduct internal network vulnerability scans and remediate any issues, at least quarterly | ![]() |
|
DS-3.10 Store local backups of local area network, SAN/NAS, devices, servers, and workstations on a server in a secure internal network. | ![]() |
|
DS-3.11 Domain Name System (DNS) Servers should be securely configured, and only trusted DNS Servers should be used for domain name resolution. | ![]() |
|
DS-4.0 Prohibit wireless networking and the use of wireless devices on the content / production network. | ![]() |
|
DS-5.0 Designate specific data I/O systems to be used for uploading / downloading content from / to external networks (Internet). | ![]() |
|
DS-5.0.1 Implement a multi-layered network architecture for ingesting content from external networks (Internet) into the production network, and moving content from the production network to external networks. | ![]() |
|
DS-5.1 Block input/output (I/O), mass storage, external storage, and mobile storage devices (e.g., USB, FireWire, Thunderbolt, SATA, SCSI, Bluetooth, NFC, MTP, PTP, etc.) and optical media burners (e.g., DVD, Blu-Ray, CD, etc.) on all systems that handle or store content, with the exception of systems used for content I/O. Refer to DS-4.0 for disconnecting wireless NICs. | ![]() |
|
DS-6.0 Install endpoint protection, and/or anti-virus and anti-malware software on all workstations, servers, and on any device that connects to production networks where content is stored (e.g., SAN/NAS etc.). This includes WFH and remote worker machines, along with VDI (virtual desktop infrastructure) used to access remote production networks. | ![]() |
|
DS-6.1 Update all anti-virus and anti-malware definitions daily, or more frequently on all workstations, servers, WFH/Remote worker machines, and virtual desktops and servers. | ![]() |
|
DS-6.2 Scan all content for viruses and malware prior to ingest onto the content / production network. | ![]() |
|
DS- 6.2.1 Local firewalls should be implemented on workstations, including WFH, and remote worker machines, to restrict unauthorized access to the workstation. |
![]() |
|
DS-6.3 Perform scans as follows: • Enable regular full system virus and malware scanning on all workstations • Enable full system virus and malware scans for servers and for systems connecting to a SAN/NAS |
![]() |
|
DS-6.4 Implement a process to regularly update systems (e.g., file transfer systems, operating systems, databases, applications, network devices, WFH/Remote worker machines) with patches/updates that remediate security vulnerabilities. |
![]() |
|
DS-6.5 Prohibit users from being Administrators on their own workstations, unless required for software (e.g., ProTools, Clipster and authoring software such as Blu-Print, Scenarist and Toshiba). Documentation from the software provider must explicitly state that administrative rights are required. | ![]() |
|
DS-6.8 Restrict software installation privileges to IT management. | ![]() |
|
DS-6.9 Implement security baselines and standards to configure corporate systems (e.g., laptops, workstations, servers, SAN/NAS, VDI (Virtual Desktop Infrastructure)) used at an onsite facility and for those used by WFH and remote workers. | ![]() |
|
DS-6.10 Unnecessary services and applications should be uninstalled from content transfer servers. | ![]() |
|
DS-7.0 Establish and implement an account management process for administrator, user, and service accounts for all information systems and applications that handle content. |
![]() |
|
DS-7.1 Maintain traceable evidence of the account management activities (e.g., approval emails, change request forms). | ![]() |
|
DS-7.5 Monitor and audit administrator and service account activities. | ![]() |
|
DS-7.6 Implement a process to review user access for all information systems that handle content and remove any user accounts that no longer require access quarterly. | ![]() |
|
DS-7.7 Restrict user access to content on a per-project basis. | ![]() |
|
DS-7.8 Disable or remove local accounts on systems that handle content where technically feasible. | ![]() |
|
DS-8.0 Enforce the use of unique usernames and passwords to access information systems. | ![]() |
|
DS-8.1 Enforce a strong password policy for gaining access to information systems. Password policy should include guidance for service accounts. Utilize MFA for all administrative accounts, any internet facing systems. MFA should be utilized by remote and WFH users when connecting to corporate and/or production systems. |
![]() |
|
DS-8.2 For remote access (e.g., VPN) to the networks, implement two-factor authentication (e.g., username / password and hard token) and monitor activity. | ![]() |
|
DS-8.2.1 Implement two-factor authentication (e.g., username / password and hard token / verification code text message) for access to web-based e-mail (Google, Microsoft, etc.) from desktops or mobile computing devices. | ![]() |
|
DS-8.3 Implement password-protected screensavers or screen-lock software for servers and workstations. | ![]() |
|
DS-8.4 Consider implementing additional authentication mechanisms to provide a layered authentication strategy for WAN and LAN / Internal Network access. | ![]() |
|
DS-9.0 Implement real-time logging and reporting systems to record and report security events; gather the following information at a minimum: • When (time stamp) • Where (source) • Who (username) • What (content) |
![]() |
|
DS-9.01 Implement logging mechanisms on all systems used for the following: • Key generation • Key management • Vendor certificate management |
![]() |
|
DS-9.2 Configure logging systems to send automatic notifications when security events are detected in order to facilitate active response to incidents. | ![]() |
|
DS-9.3 Investigate any unusual activity reported by the logging and reporting systems. | ![]() |
|
DS-9.4 Review all logs weekly, and review all critical and high daily. | ![]() |
|
DS-9.5 Enable logging of internal and external content movement and transfers and include the following information at a minimum: • Username • Timestamp • File name • Source IP address • Destination IP address • Event (e.g., download, view) |
![]() |
|
DS-9.6 Retain logs for at least one year. | ![]() |
|
DS-11.1 Encrypt content on hard drives or encrypt entire hard drives using a minimum of AES-256 encryption by either: • File-based encryption: (i.e., encrypting the content itself) • Drive-based encryption: (i.e., encrypting the hard drive) |
![]() |
|
DS-11.3 Implement and document key management policies and procedures: • Use of encryption protocols for the protection of sensitive content or data, regardless of its location (e.g., servers, databases, workstations, laptops, mobile devices, data in transit, email) • Approval and revocation of trusted devices • Generation, renewal, and revocation of content keys • Internal and external distribution of content keys • Bind encryption keys to identifiable owners • Segregate duties to separate key management from key usage • Key storage procedures • Key backup procedures |
![]() |
|
DS-11.4 Encrypt content at rest and in motion, including across virtual server instances, using a minimum of AES-256 encryption. | ![]() |
|
DS-11.5 Store secret and private keys (not public keys) used to encrypt data/content in one or more of the following forms at all times: • Encrypted with a key-encrypting key that is at least as strong as the data-encrypting key, and that is stored separately from the data-encrypting key • Within a secure cryptographic device (e.g., Host Security Module (HSM) or a Pin Transaction Security (PTS) point-of-interaction device) Has at least two full-length key components or key shares, in accordance with a security industry accepted method |
![]() |
|
DS-12.0 Implement a digital content management system to provide detailed tracking of digital content. | ![]() |
|
DS-12.1 Retain digital content movement transaction logs for one year. | ![]() |
|
DS-12.2 Review logs from digital content management system periodically and investigate anomalies. | ![]() |
|
DS-13.0 Use only client-approved transfer systems that utilize access controls, a minimum of AES-256 encryption for content at rest and for content in motion and use strong authentication for content transfer sessions. | ![]() |
|
DS-14.0 Implement and use dedicated systems for content transfers. | ![]() |
|
DS-14.1 Separate content transfer systems from administrative and production networks. | ![]() |
|
DS-14.2 Place content transfer systems in a Demilitarized Zone (DMZ) and not in the content / production network. Implement allow listing on content transfer servers to only allow transfers to and from authorized external transfer servers. | ![]() |
|
DS-14.3 Remove content from content transfer devices/systems immediately after successful transmission/receipt. | ![]() |
|
DS-14.4 Send automatic notifications to the production coordinator(s) upon outbound content transmission. | ![]() |
|
DS-15.0 Restrict access to web portals which are used for transferring content, streaming content and key distribution to authorized users. | ![]() |
|
DS-15.1 Assign unique credentials (e.g., username and password) to portal users and distribute credentials to clients securely. Authentication should be multi-factor authentication as described in DS-8.1 | ![]() |
|
DS-15.3 Place the web portal on a dedicated server in the DMZ and limit access to/from specific IPs and protocols. | ![]() |
|
DS-15.4 Prohibit the use of third-party production software/systems/services that are hosted on an internet web server or cloud provider unless approved by client in advance. | ![]() |
|
DS-15.5 Use HTTPS and enforce use of a strong cipher suite (e.g., TLS v1.3) for the internal/external web portal. Acquire an HTTPS public key certificate signed by a certificate authority trusted by a majority of web browsers. | ![]() |
|
DS-15.6 Do not use persistent cookies or cookies that store credentials in plaintext. | ![]() |
|
DS-15.7 Set access to content on internal or external portals to expire automatically at predefined intervals, where configurable. | ![]() |
|
DS-15.8 Perform at least annual penetration testing of web applications and remediate any validated issues, as per DS-1.9 | ![]() |
|
DS-15.11 Prohibit transmission of content using email (including webmail). | ![]() |
|
DS-15.12 Review access to the client web portal at least quarterly. | ![]() |
|
DS-15.13 Implement a process to review the facility's public informational website and other online industry resources for sensitive information that could be leveraged by an attacker (e.g., mentions of internal infrastructure and technologies, content transfer servers, IP addresses, photos of sensitive areas, current content being worked on, etc.) | ![]() |
Ostali zahtevi CONTENT SECURITY BEST PRACTICES
COMMON GUIDELINES
rešavaju se papirologijom unutar organizacije ili su nepotrebni u organizaciji rada
30 korisnika
30 korisnika
30 korisnika
CENA: €355 do €595 mesečno * cena je bez PDV-a
Cena zavisi od veličine rack ormana i brzine interneta.
U cene je računat internet brzine 300/300 Mbps i brzine 500/500Mbps mesečno.
Cene se odnose na zakup za period od minimum 12 meseci.