How to manage personal device risk

<?xml version="1.0" encoding="UTF-8"?><modsCollection xmlns="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-8.xsd">
<mods version="3.8">
<titleInfo>
<title>How to manage personal device risk</title>
</titleInfo>
<typeOfResource>text</typeOfResource>
<genre authority="marcgt">periodical</genre>
<originInfo>
<place>
<placeTerm type="code" authority="marccountry">esp</placeTerm>
</place>
<dateIssued encoding="marc">2017</dateIssued>
<issuance>serial</issuance>
</originInfo>
<language>
<languageTerm type="code" authority="iso639-2b">eng</languageTerm>
</language>
<physicalDescription>
<form authority="marcform">print</form>
</physicalDescription>
<abstract displayLabel="Summary">In the decade since the iPhone was released in 2007, mobile device adoption has exploded in the workplace. Bringyour own device (BYOD) policies are proliferating at a fas ter rate than the use of corporate-owned devices. Many security teams have moved to control corporate-owned devices with enterprise mobility management programs, and sorne go as far as actually securing these devices with mobile threat defense solutions. For the most part, however, employees' personal devices are left unprotected. </abstract>
<note type="statement of responsibility">Domingo Guerra</note>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080591182">
<topic>Gerencia de riesgos</topic>
</subject>
<classification authority="">7</classification>
<relatedItem type="host">
<titleInfo>
<title>Risk Management Magazine</title>
</titleInfo>
<originInfo>
<publisher>New York : Risk and Insurance Management Society, 1982-</publisher>
</originInfo>
<identifier type="issn">0035-5593</identifier>
<identifier type="local">MAP20077000291</identifier>
<part>
<text>01/12/2017 Volumen 64 Número 11 - diciembre 2017 , p. 8-10</text>
</part>
</relatedItem>
<recordInfo>
<recordContentSource authority="marcorg">MAP</recordContentSource>
<recordCreationDate encoding="marc">180111</recordCreationDate>
<recordChangeDate encoding="iso8601">20180126141150.0</recordChangeDate>
<recordIdentifier source="MAP">MAP20180000980</recordIdentifier>
<languageOfCataloging>
<languageTerm type="code" authority="iso639-2b">spa</languageTerm>
</languageOfCataloging>
</recordInfo>
</mods>
</modsCollection>