{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2024,12,4]],"date-time":"2024-12-04T05:29:49Z","timestamp":1733290189385,"version":"3.30.1"},"reference-count":4,"publisher":"Breda Publishing Press","issue":"6","license":[{"start":{"date-parts":[[2020,6,1]],"date-time":"2020-06-01T00:00:00Z","timestamp":1590969600000},"content-version":"tdm","delay-in-days":0,"URL":"https:\/\/www.elsevier.com\/tdm\/userlicense\/1.0\/"}],"content-domain":{"domain":[],"crossmark-restriction":false},"short-container-title":["Network Security"],"published-print":{"date-parts":[[2020,6]]},"abstract":"<jats:p> Proper storage of data is a security necessity. This is because data can often contain valuable company information, which is liable to fall into the wrong hands if not properly managed. The problem is growing in tandem with increased content creation \u2013 the world is full of data. It is estimated that the aggregate amount of data, which doubles in size every two years, measures 4.4 zettabytes (trillion gigabytes) and is likely to reach a massive 44 zettabytes by 2020. <jats:sup>1<\/jats:sup> <\/jats:p><jats:p> Companies are attempting to deal with a tidal wave of data. And a lack of integration inside a business can promote the dangerous phenomenon of content sprawl. <\/jats:p><jats:p> This occurs when different departments do not harmonise their processes and there is no plan to address outdated content or to ensure that data is stored in the right way. Companies need to gain a tight rein on their digital assets and institute a rigid content management system to keep up with the data explosion. But that can be easier said than done, explains Paul Hampton of Alfresco. <\/jats:p>","DOI":"10.1016\/s1353-4858(20)30066-0","type":"journal-article","created":{"date-parts":[[2020,6,17]],"date-time":"2020-06-17T14:30:43Z","timestamp":1592404243000},"page":"8-11","source":"Crossref","is-referenced-by-count":1,"title":["Keeping a secure hold on data through modern electronic content management"],"prefix":"10.70985","volume":"2020","author":[{"given":"Paul","family":"Hampton","sequence":"first","affiliation":[{"name":"Alfresco"}],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"51855","reference":[{"volume-title":"\u2018PwC Perspectives \u2013 The Future of Audit\u2019","year":"2019","key":"bib2"},{"volume-title":"\u2018How to tackle dark data\u2019","year":"2017","key":"bib3"},{"key":"bib4","unstructured":"\u2018The State of Dark Data\u2019. Splunk; \nwww.splunk.com\/pdfs\/dark-data\/the-state-of-dark-data-report.pdf accessed June 2020"},{"key":"bib5","unstructured":"\u2018The Cost of Standing Still: Top 6 Reasons to Renovate Legacy ECM\u2019. AIIM Industry Watch; \nhttps:\/\/info.aiim.org\/top-6-reasons-to-renovate-legacy-ecm accessed June 2020"}],"container-title":["Network Security"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/api.elsevier.com\/content\/article\/PII:S1353485820300660?httpAccept=text\/xml","content-type":"text\/xml","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/api.elsevier.com\/content\/article\/PII:S1353485820300660?httpAccept=text\/plain","content-type":"text\/plain","content-version":"vor","intended-application":"text-mining"},{"URL":"http:\/\/www.magonlinelibrary.com\/doi\/pdf\/10.1016\/S1353-4858%2820%2930066-0","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2024,12,3]],"date-time":"2024-12-03T22:20:13Z","timestamp":1733264413000},"score":1,"resource":{"primary":{"URL":"http:\/\/www.magonlinelibrary.com\/doi\/10.1016\/S1353-4858%2820%2930066-0"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2020,6]]},"references-count":4,"journal-issue":{"issue":"6","published-print":{"date-parts":[[2020,6]]}},"alternative-id":["10.1016\/S1353-4858(20)30066-0"],"URL":"https:\/\/doi.org\/10.1016\/s1353-4858(20)30066-0","relation":{},"ISSN":["1353-4858","1872-9371"],"issn-type":[{"type":"print","value":"1353-4858"},{"type":"electronic","value":"1872-9371"}],"subject":[],"published":{"date-parts":[[2020,6]]}}}