Air Force

August 1, 2014

Existing tools help users reduce PII breaches

1st Lt. Meredith Hein
JB San Antonio-Lackland, Texas

New buttons will show up on Outlook e-mails as part of the new Digital Signature Enforcement Tool roll out. DSET helps users protect personally identifiable information by flagging possible PII in e-mails and attachments.

 
Members of 24th Air Force are refurbishing an old e-mail tool to help Air Force users reduce breaches of personally identifiable information.

The Digital Signature Enforcement Tool, which currently prompts users to provide a digital signature when an e-mail contains an active hyperlink or attachment, is being reconfigured to scan e-mails and attachments for PII. DSET was first introduced to Outlook in 2009 by the Air Force Life Cycle Management Center.

“DSET was originally designed to mitigate risk from socially-engineered e-mail or phishing attacks. Now, it provides some protection of messages transmitting PII,” said Alonzo Pugh, cyber business system analyst for 24th AF. “The tool provides awareness for users of risks before the e-mail leaves the workstation, giving users the chance to correct the identified risk.”

PII includes items such as an individual’s social security number, driver’s license information and financial information. Breaches occur when this information is inadvertently released. User awareness is one of the biggest issues associated with PII breaches, according to Pugh.

“When users release PII that is not protected, that puts information at risk for being intercepted by adversaries. These adversaries can then use that information to target users to gain access the network,” said Pugh. “Air Force network users must do their due diligence when sending an e-mail containing PII. They need to make sure the information is protected.”

DSET capability should encourage users to be more involved in the process of preventing PII breaches, said Pugh. “The user is afforded the ability to take action in checking their e-mails to make sure they are not inadvertently releasing PII, and given the opportunity to protect it. DSET makes users more aware that they need to double check their e-mails and ensure that they are in accordance with policy; the responsibility for preventing breaches ultimately falls on them.”

The tool itself is straightforward to use, said Pugh, and will give users simple prompts to follow in sending e-mails. In addition, there is a function allowing information which was falsely identified as PII to still be sent.

“While our software solution will support the Air Force’s efforts to reduce PII breaches, it is still important for personnel to be aware and vigilant with their handling of documents containing PII,” said Col. Eric Oliver, 24th AF director of cyber systems.

The tool’s new usage is still in its initial stage, focusing on social security numbers. Developers hope that DSET will ultimately be able to scan for a variety of PII to prevent future breaches.

“It is imperative that we protect one another as we move each Air Force mission forward,” said Maj. Gen. J. Kevin McLaughlin, 24th Air Force commander. “Avoiding the release of PII is part of being a good wingman, but it is also part of protecting the network and accomplishing the Air Force mission.”

In preparation for the release of DSET, you can access training for the new tool using the following link https://afpki.lackland.af.mil/assets/files/OE-15-40-064_QRG-DSET_v0001.pdf.

Additional training on how to encrypt Microsoft Office documents can be accessed at www.24af.af.mil/shared/media/document/AFD-140701-064.pdf.

Users have multiple tools at their disposal to protect PII if encrypting e-mail is not feasible, but if electronic transmission of sensitive PII is operationally required, users can leverage approved Department of Defense file exchange services at https://safe.amrdec.army.mil/safe/.




All of this week's top headlines to your email every Friday.


 
 

 

News Briefs October 24, 2014

M4/M9 Firing Range closure The Edwards AFB Combat Arms Firing Range is closed for M4 and M9 firing until further notice. Any required firing for PCS or deployments will temporarily be accomplished at March ARB, Calif. To schedule training, contact the Combat Arms section at 661-277-2103. It is strongly recommended that all firing be scheduled as soon...
 
 
town-hall

Edwards community holds town hall meeting

Air Force photograph by Jena Romo Col. Eric Leshinksy, 412th Mission Support Group commander, addresses the audience at a town hall meeting Oct. 15 at the Airmen and Family Readiness Center. The Edwards community gathered at th...
 
 
Instagram by Master Sgt. Sonny Cohrs

Online vigilance helps reduce risk

Instagram by Master Sgt. Sonny Cohrs The Air Force reminds us not to post information about deployment departures, locations, and on-going operations. However, even a simple photo of your family pet can reveal personal informat...
 

 
Air Force photograph by Rebecca Amber

Gathering of Eagles honors 70 years of TPS

Air Force photograph by Rebecca Amber Brig. Gen. Michael Brewer, 412th Test Wing commander, offered the closing remarks for the event, reminding the audience that fundraiser is about preparing for the future. The Flight Test Hi...
 
 
commissary

Giving ‘gift of groceries’? Think Commissary gift cards

No matter the occasion, Commissary gift cards are always available to help family members, friends and organizations give the gift of groceries. “Our gift cards are versatile,” said Randy Chandler, the Defense Commi...
 
 
Air Force photograph by Christian Turner

AFMC command chief visits with Edwards Airmen

Air Force photograph by Christian Turner Chief Master Sgt. Michael J. Warner, Air Force Materiel Command command chief, speaks to enlisted Airmen at Club Muroc Oct. 15. Warner held two enlisted calls speaking to junior Airmen i...
 




0 Comments


Be the first to comment!


Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>