C4I System Security Architecture: A Perspective on Big Data Lifecycle in a Military Environment
Abstract
:1. Introduction
- Design a three-layered C4I system framework that can implement a big data system: The C4I system has all 6V’s characteristics of big data, and the layered framework confirmed the correlation between the big data lifecycle and the big data framework.
- Derivation of detailed four-layered security architecture for the military C4I big data system: We derived security requirements for the entire C4I big data system.
- Introduction of potential directions focusing on C4I big data systems’ security to guide security managers in the military: Security managers can estimate the security level of the entire system through the security architecture.
2. Understanding Big Data in Military Environment
2.1. Overview of C4I Systems from a Data Perspective and Its Security Concerns
2.2. 6V’s in the Big Military Data
- Volume: The huge amount of data (or datasets) stored and processed in a big data system [17]. Since the US military highlighted the Network Centric Warfare [22] concept in 1998, information sharing between elements of the battlefield has become more active, particularly the IoBT and surveillance assets that shoot Video/Image have exponentially increased the amount of data to be processed in a C4I system. For example, terabytes (1012) of data volume have become common to handle at the end-user level, and zettabytes (1021) of data volume is no longer an unfamiliar word for military data managers. Due to the increase in the volume of data on the battlefield, Defense Data Center requires sufficient storage space to store it and technology to manage it efficiently.
- Velocity: Velocity, in big data, concerns mainly two aspects: the speed of data growth and the rate of data flow [18]. The speed of data growth is closely related to the characteristics of data volume introduced above. The increases in the IoBT and the development of information assets on the battlefield accelerate the rise in battlefield data. The data flow rate means that real-time (or near-real-time) data transmission/reception and processing capabilities are required to implement Observe-Orient-Decide-Act (OODA) in a real-time military operation. Improved wire/wireless communication network infrastructure provides data transmission with minimal latency, and advanced computing technology enables data processing (or analysis) in real time.
- Variety: Military intelligence types include human intelligence (HUMINT), signal intelligence (SIGINT), measurement and signature intelligence (MASINT), geospatial intelligence (GEOINT), open-source intelligence (OSINT), etc. This information is collected from the human, the IoBT, sensors, unmanned aerial vehicles (UAVs), satellites, etc., operated on the battlefield, and the collected data are stored in the database as structured, unstructured, or semi-structured formats. As a result, C4I systems must be able to process different forms of data from different kinds of sources on the battlefield.
- Variability: This feature refers to change in a dataset, whether in the data flow rate, format, structure, and/or volume. For example, data volume implies the need to scale up or scale down virtualized resources to efficiently handle the additional processing load [19]. As a system architecture to handle the variability of data, the cloud can dynamically scale systems in virtual environments. It also applies relational databases and NoSQL DBs as data types change.
- Veracity: Just as input (data) must be accurate and reliable in I/O systems to achieve the desired results, data accuracy is one of the most important requirements in C4I big data systems. For example, as big data are used for decision-making, it is important to ensure that they can be trusted [23]. Inaccurate data such as repetition of meaningless data, noise, or typos may result in poor-quality output data. The system requires technology to eliminate inaccurate data. For instance, statistical methods, integrating/aggregating data with high precision technology, even machine learning algorithms, etc., are the technologies used to ensure data quality.
- Value: From a data point of view, both the input data collected in a C4I system and the output data generated after big data analysis should be of sufficient value. Therefore, by using a C4I system with big data, the commander must be able to make a decision and effectively support the activities of the combatants.
2.3. Five-Phase Big Data Lifecycle
- Collection: In practice, big data systems collect large volumes and diverse formats of data from several unique areas such as healthcare, economics/industry, smart cities, science, military, etc. Structured data are exemplified by consistently structured data and can be described efficiently in a relational model [19]. Structured data conform to a database model, which is largely characterized by the various fields to which data belong, such as name, address, age, etc., and by the data type for each field such as numeric, currency, alphabetic, name, date, and address [27]. Unstructured data refer to information that either does not have a predefined data model or are not organized in a predefined way. Photos, graphic images, video, text, voice records, streaming sensor data, and so forth can be categorized as unstructured data. Semi-structured data are a data type in which both the characteristics of structured and unstructured data are reflected. Word-processing documents, including metadata such as author name and created date, and photos uploaded to social network service (SNS) with tags are representative examples of semi-structured data.
- Storage: Big data systems are not simply satisfied with storing the raw data collected in the previous phase. In the storage step, the data preparation process (i.e., data aggregation and integration, data cleaning/cleansing, data partition, data indexing, etc.) must be included to store the large volumes and diverse formats of data appropriately. This phase briefly introduces two main technologies (i.e., distributed file system and MapReduce) to implement data storage. Distributed file systems are the most popular infrastructure that can store massive data sets in multiple distributed storage repositories [21,28]. MapReduce is a data-intensive programming model for processing large data sets in a cluster of distributed storage nodes [21,29]. Practically, Hadoop provides a framework for both Distributed File System and MapReduce.
- Analytics: This phase, big data analytics, generates useful knowledge by analyzing a large amount of previously collected and stored data. For example, Husamaldin et al. [20] suggested that big data analytics can be categorized into four aspects: descriptive analytics, diagnostic analytics, predictive analytics, and prescriptive analytics. To obtain meaningful information or knowledge, various techniques are used, such as statistical analysis, data aggregation, data clustering, machine learning, etc.
- Utilization: In each field to which big data technology is applied, the primary purpose of the utilization phase is to produce valuable information and knowledge through data analysis. For example, it is easier for the company to produce products desired by consumers in the commercial field by analyzing purchasing trends during Internet shopping. In addition, data collected for academic research can be quickly and accurately analyzed to provide valuable results. In the military domain, it provides evidence for commanders to make decisions and suggests the direction in which each combat element acts. Therefore, to effectively use big data, a visualization tool or a decision-making tool that accurately understands and expresses users’ needs is essential.
- Destruction: As requirements regarding the security and privacy of big data become stricter, it has become crucial to manage data according to regulations. Basically, privacy data should be destroyed without delay after exceeding the data retention period unless otherwise specified in other laws and regulations. In addition, data must be destroyed if they are no longer necessary for the intended purpose or if the data provider withdraws consent [26]. In the military field, the destruction of data based on security regulations is an essential element to ensure the safety of military operations and protect the C4I system.
3. C4I System Framework with Big Data in the Battlefield Environment
3.1. Layered Big Data System Framework from a System Perspective
- Infrastructure Layer: This layer refers to physical or virtualized resources required in the entire process of the big data lifecycle for data collection, storage, analysis, utilization, and destruction. The infrastructure consists of a server, storage, network devices, the IoT, sensors, Internet web services, and so on. Additionally, in recent years, cloud computing, which is featured by excellent scalability and use of information system resources, on-demand resource provisioning, and ease of parallel computing, has been in the spotlight as a big data infrastructure that guarantees the 6V’s.
- Data Layer: This layer stores and manages data in a big data system. To deal with the vast amounts and various forms of data in the data layer, it is necessary to have an appropriate system. For example, partitioning, indexing, and MapReduce technologies have been applied to distributed file systems to store vast amounts of data in multiple repositories and efficiently manage data. In addition, databases such as relational databases and NoSQL are required for various types of data.
- Big Data Platform Layer: The big data platform may be defined as middleware for implementing the big data function of the system [21]. The Hadoop ecosystem is a representative platform for implementing big data. For example, HDFS, MapReduce, YARN, etc., provide functions as unique modules for storing, processing, and managing data in big data systems; Cloudera, which is a commercial product that enhances security and management, is a representative of a Platform as a Service (PaaS).
- Application Layer: Depending on the field in which the big data system and processed data are used, appropriate analysis methods and visualization tools should be applied, which are covered by the application layer. In other words, algorithms for obtaining analysis results required by users or equipment and software that users can directly use are necessary in the application layer.
3.2. Three-Layered C4I System Framework in Terms of Battlefield Data Flow
- Data Generation Layer: This layer generates large volumes and diverse types of battlefield data and transmits those data to the next step, the data processing layer. The elements that generate combat data are operated in a wide variety of places, such as combat areas, military camp areas, and civil areas. Examples of combat data generators are intelligence assets, combat assets, combat support facilities, other commands, the Internet, etc. Combat data also consist of sensor data from various IoBTs, GPS signal, image/video, voice/radio signal, text/documents, etc. It contains almost all forms of data covered by a typical big data system.
- Data Processing Layer: This layer runs in the integrated data center, where major big data lifecycle phases are implemented to store and analyze the collected data. The data processing layer can be divided into infrastructure and platform (or Platform as a Service (PaaS)). Infrastructure means physical/virtual resources such as cloud computing, network devices, etc., and the big data system platform may be, e.g., Hadoop, Cloudera, etc.
- Data Usage Layer: This layer helps commanders make decisions by visualizing the data analyzed in the data processing layer as valuable information. Real-time combat information is directly available to the commander and staff who make situational judgments and decisions at headquarters and the combat/intelligence assets on the battlefield.
3.3. Proposed C4I Big Data System Framework
4. Security Architecture for the Military C4I Big Data System
4.1. Three-Layered C4I System Framework in Terms of Battlefield Data Flow
4.2. Security Threat and Requirements Related to C4I Big Data System Framework
4.2.1. Data Generation Layer
- End-Point Security: The end-point devices that generate data may be referred to as the IoBT, which are connected through a network. The IoBT basically needs anti-malware functionality to compensate for the vulnerability to ransomware infection. In addition, considering the operating environment of the battlefield, the availability of the device should be increased, and data could be erased urgently in preparation for dangerous situations.
- Authentication: There are two considerations for the authentication in the data generation layer: The first is user authentication in the device. The device can verify that the user accesses the device by applying multi-factor authentication such as username/password and biometric authentication. The second is access permission to the system. By checking whether the device is registered as part of the system, network access control (NAC) may be applied to verify unique identifiers such as IP and MAC addresses of the device.
- Data Encryption: Encryption is necessary to ensure data confidentiality, and two points of view must also be considered: when data are collected and stored on a device and when data are transmitted and received over a network.
- Privacy Issue: Privacy-preserving issues for collected big data are a vital part of security. If individual combatants’ personal information covered in a C4I system is collected, privacy issues must thoroughly be considered as well. For example, not only general personal information (e.g., the combatant’s name, class, and gender) but also location information and bio-signals must be sensitively managed. Therefore, the system must comply with the country’s privacy regulations such as the General Data Protection Regulation (GDPR) and California Consumer Privacy Act (CCPA).
- Wireless Network Security: Confidence, availability, and integrity must be guaranteed for wireless traffic communication on the battlefield. Confidentiality can be strengthened through the data encryption (in-transit or at-rest) presented above, but further supplementary measures are needed to prevent interruptions to availability caused by jamming attacks and any harm to integrity caused by traffic hijacking or injection attacks from the enemy. Therefore, to protect the wireless network in the data generation layer, it is necessary to have the ability to overcome traffic jamming attacks and to prove that traffic has not been affected during transmission/reception by verifying data traffic.
- Connection Point Security: In an isolated network, connection points with external networks are vulnerable factors that should be dealt with carefully. In particular, to transmit the data from the external network to the inside, the network for the connection point must be configured safely, and the format and safety of the data must be verified and transmitted.
4.2.2. Data Processing Layer
- 1.
- Infrastructure Represented by Cloud Computing
- 2.
- Platform as a Service (PaaS)—Hadoop, Cloudera
- Authentication: This is a fundamental security requirement for any information system, users must prove their identity, and the system necessarily verifies whether the C4I big data system could be organized into four categories: authentication, authorization, encryption, and security monitoring and audit.
- Authentication: This is a fundamental security requirement for any information system, users must prove their identity, and the system necessarily verifies whether the user has accessibility. Clarifying the identity of users accessing the system amid the threat of continuous network penetration by the enemy is a necessary security factor to ensure C4I big data system managers can operate the entire system stably. Authentication on the Hadoop platform uses many different access control technologies (i.e., Access Control Lists (ACLs), HDFS extended ACLs, and role-based access control (RBAC)) and applies the Kerberos mechanism. Kerberos is widely used as an authentication mechanism applicable to most Hadoop clusters such as HDFS, MapReduce, and YARN [47].
- Authorization: In a military C4I system, the range of access to data assigned to users varies widely depending on the hierarchical differences in the organization and the role of the staff. All activities within the Hadoop cluster, such as data access, use, view, and administrative modification, must be properly executed within the authority assigned to the user or administrator, and the authorization mechanism must be applied for this purpose. In Hadoop clusters such as HDFS, MapReduce, and YARN, access control is applied through POSIX-style permissions that grant permission to each file and directory. Subdivided ACLs are also applied, or Apache RANGER is used to manage authorization for each cluster [47].
- Encryption: Encryption is the last line of defense when a hacker obtains complete access to our data [51]. Sensitive data that need to be protected, whether stored in storage or in transit, must be encrypted so that its contents are not disclosed and must not be decrypted by unauthorized users. In military C4I systems, data encryption is a crucial security requirement that protects against confidentiality breaches due to enemy threats. Hadoop cluster guarantees encryption not only for data-at-rest but also for data-in-transit by applying transport layer security (TLS) and secure socket layer (SSL) [47].
- Security Monitoring and Auditing Log: The system security administrator should monitor the behavior of the Hadoop cluster and quickly recognize events that deviate from the set security criteria. Sometimes by leaving all actions generated in the Hadoop cluster, the stored log is analyzed to find the cause and effect of the problem. Ganglia and Nagios are open-source-based monitoring tools [48] that can also be applied to Hadoop, and the Cloudera manager also provides high-performance security monitoring capabilities for the big data platform [47].
4.2.3. Data Usage Layer
4.3. Proposed Security Architecture for Big Data Implemented in a Military C4I System
5. Evaluation and Discussion
6. Conclusions
Author Contributions
Funding
Institutional Review Board Statement
Informed Consent Statement
Data Availability Statement
Conflicts of Interest
References
- Laurila, J.K.; Gatica-Perez, D.; Aad, I.; Blom, J.; Bornet, O.; Do, T.M.T.; Dousse, O.; Eberle, J.; Miettinen, M. From big smartphone data to worldwide research: The Mobile Data Challenge. Pervasive Mob. Comput. 2013, 9, 752–771. [Google Scholar] [CrossRef] [Green Version]
- Anshari, M.; Lim, S.A. E-government with big data enabled through smartphone for public services: Possibilities and challenges. Int. J. Public Adm. 2017, 40, 1143–1158. [Google Scholar] [CrossRef]
- Hajjaji, Y.; Boulila, W.; IFarah, R.; Romdhani, I.; Hussain, A. Big data and IoT-based applications in smart environments: A systematic review. Comput. Sci. Rev. 2021, 39, 100318. [Google Scholar] [CrossRef]
- Marjani, M.; Nasaruddin, F.; Gani, A.; Karim, A.; Hashem, I.A.T.; Siddiqa, A.; Yaqoob, I. Big IoT data analytics: Architecture, opportunities, and open research challenges. IEEE Access 2017, 5, 5247–5261. [Google Scholar]
- Ergüzen, A.; Ünver, M. Developing a File System Structure to Solve Healthy Big Data Storage and Archiving Problems Using a Distributed File System. Appl. Sci. 2018, 8, 913. [Google Scholar] [CrossRef] [Green Version]
- Ali, W.; Shafique, M.U.; Majeed, M.A.; Raza, A. Comparison between SQL and NoSQL Databases and Their Relationship with Big Data Analytics. Asian J. Res. Comput. Sci. 2019, 4, 1–10. [Google Scholar] [CrossRef]
- Roh, Y.; Heo, G.; Whang, S.E. A Survey on Data Collection for Machine Learning: A Big Data—AI Integration Perspective. IEEE Trans. Knowl. Data Eng. 2021, 33, 1328–1347. [Google Scholar] [CrossRef] [Green Version]
- Ge, M.; Bangui, H.; Buhnova, B. Big data for internet of things: A survey. Future Gener. Comput. Syst. 2018, 87, 601–614. [Google Scholar] [CrossRef]
- Abouelmehdi, K.; Beni-Hssane, A.; Khaloufi, H.; Saadi, M. Big data security and privacy in healthcare: A Review. Procedia Comput. Sci. 2017, 113, 73–80. [Google Scholar] [CrossRef]
- Russell, S.; Abdelzaher, T. The internet of battlefield things: The next generation of command, control, communications and intelligence (C3I) decision-making. In Proceedings of the MILCOM 2018–2018 IEEE Military Communications Conference (MILCOM), Los Angeles, CA, USA, 29–31 October 2018. [Google Scholar]
- Wang, M.; Cao, S. A survey on C4ISR system architecture technique. Glob. J. Eng. Technol. Adv. 2020, 2, 54–66. [Google Scholar] [CrossRef]
- Ahmad, H.; Dharmadasa, I.; Ullah, F.; Babar, A. A Review on C3I Systems’ Security: Vulnerabilities, Attacks, and Countermeasures. arXiv 2021, arXiv:2104.11906. [Google Scholar]
- Agadakos, I.; Ciocarlie, G.F.; Copos, B.; George, J.; Leslie, N.; Michaelis, J. Security for Resilient IoBT Systems: Emerging Research Directions. In Proceedings of the IEEE INFOCOM 2019—IEEE Conference on Computer Communications Workshops (INFOCOM WKSHPS), Paris, France, 29 April–2 May 2019. [Google Scholar]
- Cho, S.; Hwang, S.; Shin, W.; Kim, N.; In, H.P. Design of Military Service Framework for Enabling Migration to Military SaaS Cloud Environment. Electronics 2021, 10, 572. [Google Scholar] [CrossRef]
- Gupta, R.; Sultania, K.; Singh, P.; Gupta, A. Security for wireless sensor networks in military operations. In Proceedings of the 2013 Fourth International Conference on Computing, Communications and Networking Technologies (ICCCNT), Tiruchengode, India, 4–6 July 2013; pp. 1–6. [Google Scholar] [CrossRef]
- De Mauro, A.; Greco, M.; Grimaldi, M. A formal definition of Big Data based on its essential features. Libr. Rev. 2016, 65, 122–135. [Google Scholar] [CrossRef]
- Laney, D. 3D data management: Controlling data volume, velocity and variety. META Group Res. Note 2001, 6, 1. [Google Scholar]
- Patgiri, R.; Ahmed, A. Big Data: The V’s of the Game Changer Paradigm. In Proceedings of the 2016 IEEE 18th International Conference on High Performance Computing and Communications; IEEE 14th International Conference on Smart City; IEEE 2nd International Conference on Data Science and Systems (HPCC/SmartCity/DSS), Sydney, NSW, Australia, 12–14 December 2016; pp. 17–24. [Google Scholar] [CrossRef]
- Chang, W.L.; Grady, N. Big Data Public Working Group Definitions and Taxonomies Subgroup NIST Big Data Interoperability Framework: Volume 1, Definitions. NIST Spec. Publ. 2015. [Google Scholar] [CrossRef]
- Husamaldin, L.; Saeed, N. Big Data Analytics Correlation Taxonomy. Information 2010, 11, 17. [Google Scholar] [CrossRef] [Green Version]
- Kune, R.; Konugurthi, P.K.; Agarwal, A.; Chillarige, R.R.; Buyya, R. The anatomy of big data computing. Softw. Pract. Exp. 2016, 46, 79–105. [Google Scholar] [CrossRef] [Green Version]
- Pushkar, A. Network-centric warfare: Its origin and future. Accel. World’s Res. 1998, 124, 28–35. [Google Scholar]
- Hammad, K.A.I.; Fakharaldien, M.A.I.; Zain, J.M.; Majid, M. Big data analysis and storage. In Proceedings of the 2015 International Conference on Operations Excellence and Service Engineering, Orlando, FL, USA, 10–11 September 2015. [Google Scholar]
- Chang, W.L.; Grady, N. NIST big data interoperability framework: Volume 2 Big Data Taxonomy. NIST Spec. Publ. 2017, 1500, 10. [Google Scholar] [CrossRef]
- Patgiri, R. A Taxonomy on Big Data: Survey. arXiv 2018, arXiv:1808.08474. [Google Scholar]
- Koo, J.; Kang, G.; Kim, Y.-G. Security and Privacy in Big Data Life Cycle: A Survey and Open Challenges. Sustainability 2020, 12, 10571. [Google Scholar] [CrossRef]
- Murthy, P.; Bharadwaj, A.; Subrahmanyam, P.A.; Roy, A.; Rajan, S. Cloud Security Alliance Report on Big Data Taxonomy. September 2014. Available online: https://downloads.cloudsecurityalliance.org/initiatives/bdwg/Big_Data_Taxonomy.pdf (accessed on 25 August 2021).
- Shvachko, K.; Kuang, H.; Radia, S.; Chansler, R. The Hadoop Distributed File System. In Proceedings of the IEEE 26th Symposium on Mass Storage Systems and Technologies (MSST), Incline Village, NV, USA, 3–7 May 2010; pp. 1–10. [Google Scholar]
- Dean, J.; Ghemawat, S. MapReduce: Simplified data processing on large cluster. Commun. ACM 2008, 51, 107–113. [Google Scholar] [CrossRef]
- Damiani, E.; Ardagna, C.A.; Zavatarelli, F.; Rekleitis, E.; Marinos, L. Big Data Threat Landscape and Good Practice Guide; European Union Agency for Network and Information Security (ENISA): Athens, Greece, 2016. [Google Scholar]
- Big Data Working Group. Expanded Top Ten Big Data Security and Privacy Challenges. Cloud Security Alliance. 2013. Available online: https://downloads.cloudsecurityalliance.org/initiatives/bdwg/Expanded_Top_Ten_Big_Data_Security_and_Privacy_Challenges.pdf (accessed on 25 August 2021).
- Greene, T.; Shmueli, G.; Ray, S.; Fell, J. Adjusting to the GDPR: The Impact on Data Scientists and Behavioral Researchers. Big Data 2019, 7, 140–162. [Google Scholar] [CrossRef] [Green Version]
- Stallings, W. Handling of Personal Information and Deidentified, Aggregated, and Pseudonymized Information Under the California Consumer Privacy Act. IEEE Secur. Priv. Mag. 2020, 18, 61–64. [Google Scholar] [CrossRef]
- Khan, R.A.; Alka, K. An Improved Security Threat Model for Big Data Life Cycle. Asian J. Comput. Sci. Technol. 2018, 7, 33–39. [Google Scholar] [CrossRef]
- Rajan, S. (Ed.) Top 10 Big Data Security and Privacy Challenges; Cloud Security Alliance: Seattle, WA, USA, 2012; Available online: https://downloads.cloudsecurityalliance.org/initiatives/bdwg/Big_Data_Top_Ten_v1.pdf (accessed on 25 August 2021).
- Yang, K.; Lee, D.; Kim, K.; Yoon, H. Analysis of Security Threat and Security Requirements of the Bigdata System. J. Secur. Eng. 2016, 13, 501–514. [Google Scholar] [CrossRef]
- Hossain, E.; Khan, I.; Un-Noor, F.; Sikander, S.S.; Sunny, S.H. Application of Big Data and Machine Learning in Smart Grid, and Associated Security Concerns: A Review. IEEE Access 2019, 7, 13960–13988. [Google Scholar] [CrossRef]
- Mavroeidakos, T.; Chaldeakis, V. Threat landscape of next generation IoT-enabled smart grids. In IFIP International Conference on Artificial Intelligence Applications and Innovations; Springer: Cham, Switzerland, 2020. [Google Scholar]
- Puthal, D.; Ranjan, R.; Chen, J. Big Data Stream Security Classification for IoT Applications. In Encyclopedia of Big Data Technologies; Springer: Cham, Switzerland, 2018. [Google Scholar] [CrossRef]
- Koo, J.; Kim, Y.-G.; Lee, S.H. Design of Security Architecture for the Cloud-Based Korea Military Command and Control System. J. Korean Inst. Commun. Inf. Sci. 2020, 45, 400–408. [Google Scholar] [CrossRef]
- Koo, J.; Oh, S.-R.; Lee, S.H.; Kim, Y.-G. Security Architecture for Cloud-Based Command and Control System in IoT Environment. Appl. Sci. 2020, 10, 1035. [Google Scholar] [CrossRef] [Green Version]
- FedRAMP Security Controls Baseline. Available online: https://www.fedramp.gov/documents/ (accessed on 11 August 2021).
- Cloud Computing Security Requirements Guide. Available online: https://public.cyber.mil/dccs/dccsdocuments/ (accessed on 11 August 2021).
- Security Certification Guide for Cloud Service. Available online: https://www.kisa.or.kr/public/laws/laws3_View.jsp?cPage=1&mode=view&p_No=259&b_No=259&d_No=91&ST=&SV= (accessed on 11 August 2021).
- Security Requirements for Server Virtualization System. Available online: http://www.tta.or.kr/data/ttas_view.jsp?rn=1&pk_num=TTAK.KO-10.0708 (accessed on 11 August 2021).
- Security Guidelines of National and Public Institution for Cloud Computing; National Intelligence Service: Seoul, Korea, 2016; pp. 101–103.
- Cloudera Inc. Cloudera Security Overview. August 2020. Available online: https://docs.cloudera.com/cdp-private-cloud-base/7.1.3/security-overview/cm-security-overview.pdf (accessed on 15 August 2021).
- Perwej, Y. The Hadoop Security in Big Data A Technological Viewpoint and Analysis. Int. J. Sci. Res. Comput. Sci. Eng. IJSRCSE 2019, 7, 1–14. [Google Scholar]
- Shrihari, M.R.; Manjunath, T.N.; Archana, R.A.; Hegadi, R.S. Research Challenges in Big Data Security with Hadoop Platform. In International Conference on Recent Trends in Image Processing and Pattern Recognition; Springer: Singapore, 2019; Volume 1037. [Google Scholar] [CrossRef]
- Martis, M.; Pai, N.V.; Pragathi, R.S.; Rakshatha, S.; Dixit, S. Comprehensive Survey on Hadoop Security. Emerg. Res. Comput. Inf. Commun. Appl. 2019, 227–236. [Google Scholar] [CrossRef]
- Peterson, G. Security Architecture Blueprint; Arctec Group, LLC.: Graz, Austria, 2007. [Google Scholar]
- Alghamdi, A.S. Proposed methodology to enhance C4I systems security on architectural level. Sci. Res. Essays 2011, 6, 6095–6103. [Google Scholar] [CrossRef]
- Shukla, V.; Singh, B.; Kumar, M.; Negi, K. Big Data Analytics in C4I Systems. In Proceedings of the 2018 International Conference on Automation and Computational Engineering (ICACE), Greater Noida, India, 3–4 October 2018. [Google Scholar]
- Zhang, J.; Wang, G.; Wang, S. Command and Control System Construction in Big Data Era. J. Phys. Conf. Ser. 2019, 1168, 032022. [Google Scholar] [CrossRef]
- Song, X.; Wu, Y.; Ma, Y.; Cui, Y.; Gong, G. Military simulation big data: Background, state of the art, and challenges. Math. Probl. Eng. 2015, 2015, 298356. [Google Scholar] [CrossRef] [Green Version]
- DoD Digital Modernization Strategy; Department of Defense: Arlington, VA, USA, 2019.
Brief Description | In the Military C4I System | |
---|---|---|
Volume | Large amount of data |
|
Velocity | Speed of data growth Rate of data flow |
|
Variety | Different types of data from different kind of data source. |
|
Variability | Change of data flow rate, format, structure, volume, etc. |
|
Veracity | Data accuracy |
|
Value | Valuable input/output data |
|
System | Security | ||||
---|---|---|---|---|---|
Big Data | C4I System Framework | Requirements | Architecture | ||
Lifecycle | System Architecture | ||||
Ahmad et al. (2021) [12] | − | − | Four categories centered on the communication network | 62 countermeasures based on 27 vulnerabilities and 22 attack vectors | − |
Alghamdi et al. (2011) [52] | − | − | Department of defense architectural framework (DODAF) models | Briefly mentioned INFOSEC (confidentiality, integrity, and availability) | An example of a security architecture model based on cyber threats and operational situation |
Shukla et al. (2018) [53] | Raw data, collection, filtering/classification, analysis, storage, and visualization | Briefly mentioned Hadoop core architecture | − | Authorization, auditing, and authentication | − |
Zhang et al. (2019) [54] | − | − | Resource, capability, platform, management layer | Briefly mentioned about data security | − |
Song et al. (2015) [55] | Data generation, management, and analysis | − | Five-layered architecture (repository, platform, service, application, and portal) | − | − |
Proposed method | Collection, storage, analytics, utilization, and destruction | Four-layered architecture (infrastructure, data, platform, and application) | Three-layered framework (data generation, data processing, and data usage) | 34 security requirements | Four-layered security architecture |
Publisher’s Note: MDPI stays neutral with regard to jurisdictional claims in published maps and institutional affiliations. |
© 2021 by the authors. Licensee MDPI, Basel, Switzerland. This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution (CC BY) license (https://creativecommons.org/licenses/by/4.0/).
Share and Cite
Baek, S.; Kim, Y.-G. C4I System Security Architecture: A Perspective on Big Data Lifecycle in a Military Environment. Sustainability 2021, 13, 13827. https://doi.org/10.3390/su132413827
Baek S, Kim Y-G. C4I System Security Architecture: A Perspective on Big Data Lifecycle in a Military Environment. Sustainability. 2021; 13(24):13827. https://doi.org/10.3390/su132413827
Chicago/Turabian StyleBaek, Seungjin, and Young-Gab Kim. 2021. "C4I System Security Architecture: A Perspective on Big Data Lifecycle in a Military Environment" Sustainability 13, no. 24: 13827. https://doi.org/10.3390/su132413827
APA StyleBaek, S., & Kim, Y. -G. (2021). C4I System Security Architecture: A Perspective on Big Data Lifecycle in a Military Environment. Sustainability, 13(24), 13827. https://doi.org/10.3390/su132413827