Home

Remove TLS 1.0/1.1 and 3DES Dependencies

%3CLINGO-SUB%20id%3D%22lingo-sub-329481%22%20slang%3D%22en-US%22%3ERemove%20TLS%201.0%2F1.1%20and%203DES%20Dependencies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-329481%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20I%20went%20to%26nbsp%3B%3CA%20href%3D%22http%3A%2F%2Fservicetrust.microsoft.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fservicetrust.microsoft.com%3C%2FA%3E%26nbsp%3Bto%20see%20any%20users%20still%20using%20TLS%201.9%2F1.1.%20How%20do%20I%20remove%20TLS%201.0%2F1.1.%20How%20do%20I%20go%20about%20making%20these%20compatible%20so%20they%20work%20come%20February%2028%2C%202019%20when%20Office%20365%20retires%203DES%3F%20Thank%20you%20for%20your%20help.%20Here%20is%20what%20I%20get%3A%3C%2FP%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3ENotice%3A%20This%20report%20includes%203DES%20and%20TLS1.0%2F1.1%20usages.%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EUserName%20%2F%20IP%20address%3C%2FTD%3E%3CTD%3E%26nbsp%3BProtocol%3C%2FTD%3E%3CTD%3E%26nbsp%3BAgent%3C%2FTD%3E%3CTD%3E%26nbsp%3BCount%3C%2FTD%3E%3CTD%3E%26nbsp%3BReport%20Date%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3Exxxx%40wynnetr.com%3C%2FTD%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3CTD%3E12%3C%2FTD%3E%3CTD%3E1%2F30%2F2019%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3Exxxx%40wynnetr.com%3C%2FTD%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BOffice%2F16.0%2B(Windows%2BNT%2B10.0%3B%2BMicrosoft%2BOutlook%2B16.0.11126%3B%2BPro)%3C%2FTD%3E%3CTD%3E2%3C%2FTD%3E%3CTD%3E1%2F30%2F2019%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3Exxxx%40wynnetr.com%3C%2FTD%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BOffice%2F16.0%2B(Windows%2BNT%2B10.0%3B%2BMicrosoft%2BOutlook%2B16.0.11126%3B%2BPro)%3C%2FTD%3E%3CTD%3E1%3C%2FTD%3E%3CTD%3E1%2F30%2F2019%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3Exxxx%40wynnetr.com%3C%2FTD%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EAndroid-SAMSUNG-SM-G930V%2F101.80000%3C%2FTD%3E%3CTD%3E1%3C%2FTD%3E%3CTD%3E1%2F30%2F2019%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3Exxxx%40wynnetr.com%3C%2FTD%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EAndroid-SAMSUNG-SM-G360V%2F101.50101%3C%2FTD%3E%3CTD%3E2%3C%2FTD%3E%3CTD%3E1%2F30%2F2019%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3Exxxx%40wynnetr.com%3C%2FTD%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EApple-iPhone8C4%2F1507.77%3C%2FTD%3E%3CTD%3E1%3C%2FTD%3E%3CTD%3E1%2F30%2F2019%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3Exxxx%40wynnetr.com%3C%2FTD%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3CTD%3E8%3C%2FTD%3E%3CTD%3E1%2F30%2F2019%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-329481%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Etls%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-387304%22%20slang%3D%22en-US%22%3ERe%3A%20Remove%20TLS%201.0%2F1.1%20and%203DES%20Dependencies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-387304%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F4306%22%20target%3D%22_blank%22%3E%40Forrest%20Hoffman%3C%2FA%3E%26nbsp%3BFrom%20what%20I've%20been%20able%20to%20figure%20out%2C%20sometimes%20these%20devices%20just%20glitch%20and%20fail%20to%20resolve%201.2%2C%20so%20they%20fall%20back%20to%201.1.%20Once%20there%20is%20no%201.1%20they%20will%20stop%20attempting%20fall%20back%20and%20will%20continue%20to%20try%201.2%20until%20it%20succeeds.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20so%20far%20only%20my%20somewhat%20researched%20theory.%20But%20for%20example%2C%20I%20will%20see%20one%20iPhone%20fail%20today%2C%20but%20succeed%20tomorrow.%20This%20seems%20to%20suggest%20they%20aren't%20only%20able%20to%20connect%20to%20just%201.1.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-386907%22%20slang%3D%22en-US%22%3ERe%3A%20Remove%20TLS%201.0%2F1.1%20and%203DES%20Dependencies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386907%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F294991%22%20target%3D%22_blank%22%3E%40AliceChained%3C%2FA%3E%26nbsp%3B%20I%20have%20been%20researching%20the%20same%20thing%20for%20the%20past%20few%20hours.%26nbsp%3B%20I%20even%20went%20so%20far%20as%20to%20post%20a%20question%20on%20the%20%3CA%20title%3D%22TLS%201.2%20for%20iPhone%22%20href%3D%22https%3A%2F%2Fdiscussions.apple.com%2Fthread%2F250256623%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EApple%20Community%3C%2FA%3E%26nbsp%3B.%3C%2FP%3E%3CP%3EI%20am%20pulling%20my%20hair%20out%20because%20I%20do%20not%20use%20iPhone%20and%20unsure%20how%20to%20force%20them%20to%20use%20TLS%201.2%20.%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20my%20Security%20Score%20Report%20this%20is%20what%20I%20see%3B%3C%2FP%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3E%26nbsp%3BProtocol%3C%2FTD%3E%3CTD%3E%26nbsp%3BAgent%3C%2FTD%3E%3CTD%3E%26nbsp%3BCount%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EApple-iPhone11C8%2F1604.57%3C%2FTD%3E%3CTD%3E2%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EApple-iPhone8C1%2F1604.39%3C%2FTD%3E%3CTD%3E1%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EApple-iPhone10C4%2F1604.57%3C%2FTD%3E%3CTD%3E3%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20may%20have%20found%20a%20clue%20on%20one%20of%20the%20other%20%3CA%20title%3D%22TLS%20config%22%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fexchange%2F2018%2F04%2F02%2Fexchange-server-tls-guidance-part-2-enabling-tls-1-2-and-identifying-clients-not-using-it%2F%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EMS%20Exchange%20blog%20sites%3C%2FA%3E.%20About%20half%20way%20down%20in%20the%20Notes.%26nbsp%3B%20It%20seems%20if%20the%20client%20is%20using%20Authenticated%20SMTP%20the%20Exchange%20server%20logs%20it%20wrong%20and%20TLS%201.2%20may%20be%20used%20after%20all.%20This%20blog%20is%20referring%20to%20Exchange%20on-Prem%20servers%20so%20not%20sure%20how%20relevant%20it%20is.%3C%2FP%3E%3CP%3E%3CSTRONG%3EIf%20anyone%20here%20knows%20how%20to%20configure%20TLS%201.2%20on%20iPhone%20native%20mail%20app%3C%2FSTRONG%3E%20please%20give%20me%20some%20clues.%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-359968%22%20slang%3D%22en-US%22%3ERe%3A%20Remove%20TLS%201.0%2F1.1%20and%203DES%20Dependencies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-359968%22%20slang%3D%22en-US%22%3E%3CP%3EBut%20iOS%20is%20on%20ver%2012%20now%3F!%3F%20Who's%20still%20on%2010%3F%3C%2FP%3E%3CP%3EFound%20this%20thread%20trying%20to%20figure%20out%20why%20I%20have%20one%20iPhone%20(out%20of%20a%20half%20dozen)%20showing%20on%20my%20report.%3C%2FP%3E%3CP%3ENo%20one%20figured%20that%20out%20yet%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-354976%22%20slang%3D%22en-US%22%3ERe%3A%20Remove%20TLS%201.0%2F1.1%20and%203DES%20Dependencies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-354976%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20differences%20in%20reports%20on%20different%20days%20might%20be%20due%20to%20the%20fact%20that%20if%20a%20user%20does%20not%20work%20on%20a%20particular%20day%20(hence%20doesn't%20connect%20to%20Office%20365)%20then%20for%20that%20day's%20report%20the%20user%20will%20not%20show%20up%2C%20even%20though%20the%20user%20is%20still%20not%20compliant.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThen%20how%20do%20we%20know%20for%20sure%20everyone%20is%20compliant%2C%20I%20do%20not%20have%20much%20clue.%20Microsoft%20should%20have%20keep%20listing%20all%20users%20it%20detected%20earlier%20until%20it%20detects%20a%20compliant%20connection%20from%20the%20same%20user.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-353955%22%20slang%3D%22en-US%22%3ERe%3A%20Remove%20TLS%201.0%2F1.1%20and%203DES%20Dependencies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353955%22%20slang%3D%22en-US%22%3E%3CP%3EI%20just%20re-ran%20the%20report%20this%20morning%20and%20have%20different%20results%20also%20and%20I%20did%20not%20make%20any%20changes%20or%20modifications.%20Here%20is%20what%20I%20show%20now%20and%20not%20sure%20how%20to%20fix%20them.%20Most%20of%20them%20are%20on%20either%20Android%20or%20Apple%20phones.%20I%20still%20show%201%20on%20Office%2C%20not%20sure%20what%20Microsoft%2BBITS%2F7.5%20is%3F%3F%3C%2FP%3E%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Fi.gyazo.com%2F83470cc7fc1dd42cda5d71042ad4979e.png%22%20border%3D%220%22%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-353635%22%20slang%3D%22en-US%22%3ERe%3A%20Remove%20TLS%201.0%2F1.1%20and%203DES%20Dependencies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353635%22%20slang%3D%22en-US%22%3ELooking%20on%20Sunday%20night%20at%20the%20reports%20of%20my%20~20%20client%20tenants%2C%20there%20seems%20to%20have%20been%20a%20change.%20None%20of%20them%20now%20contain%20any%20Win10%20(Office16%2F15)%20entries.%20So%20I%E2%80%99m%20wondering%20if%20there%20was%20a%20bug%20in%20the%20reports%20and%20it%E2%80%99s%20been%20fixed!%3CBR%20%2F%3E%3CBR%20%2F%3EAnyone%20see%20the%20same%3F%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20reports%20look%20a%20bit%20sparse%20also%20however.%20MNy%20have%20no%20rows.%20Perhaps%20the%20school%20holidays%20last%20week%20meant%20less%20folk%20were%20connecting%3F%20The%20reports%20clearly%20aren%E2%80%99t%20cumulative%20over%20all%20time%2C%20as%20entries%20from%20an%20older%20report%20don%E2%80%99t%20always%20appear%20in%20a%20later%20one.%20I%20wonder%20what%20needs%20to%20happen%20to%20make%20a%20device%20appear%2C%20is%20it%20just%20to%20connect%20to%20read%20mail%20etc%2C%20or%20it%20that%20it%20needs%20to%20re-authenticate%20e.g.%20after%2014%20days%20etc%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-332404%22%20slang%3D%22en-US%22%3ERe%3A%20Remove%20TLS%201.0%2F1.1%20and%203DES%20Dependencies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-332404%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F6022%22%20target%3D%22_blank%22%3E%40Alan%20McFarlane%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3EI%20had%20learned%20that%20BITS%20is%20used%20to%20download%20the%20address%20book%20(OAB).%20So%20those%20lines%20should%E2%80%A6mean%20Windows%207%2C%20but%20given%20we%20saw%20win10%20above%E2%80%A6%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20sounds%20like%20something%20that%20Microsoft%20has%20to%20update%2C%20as%20our%20systems%20(Office%202016%20%26amp%3B%20Windows%207)%20support%20TLS%201.2%20for%20the%20services%20that%20are%20at%20that%20level.%20But%20if%20their%20services%20(BITS)%20isn't%20supporting%20it%20from%20their%20end%20how%20can%20we%20be%20%22compliant%22%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-332395%22%20slang%3D%22en-US%22%3ERe%3A%20Remove%20TLS%201.0%2F1.1%20and%203DES%20Dependencies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-332395%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20a%20great%20question.%20I%20have%20read%20that%20the%20issue%20with%20the%20Apple%20mail%20native%20iPhone%20app%20was%20corrected%20in%20iOS%2010%2C%20but%20I%20still%20see%20iPhones%20with%20iOS%2010%20showing%20up%20on%20the%20report.%20I%20also%20see%20one%20Microsoft%20Office%202016%20client%20showing%20up%20on%20the%20report%20(using%20Windows%2010%20OS).%20I%20have%20no%20idea%20why%20that%20client%20machine%20would%20be%20using%20a%20lower%20flavor%20of%20TLS.%20I%20could%20disable%20TLS%201.0%20and%201.1%20on%20the%20client%20machine%2C%20but%20unfortunately%2C%20many%20websites%20still%20use%201.0%20for%20whatever%20reason.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20received%20an%20email%20from%20Office%20365%20urging%20me%20to%20run%20this%20report%2C%20probably%20like%20most%20of%20you.%20I%20ran%20it%20and%20see%20some%20TLS%201%20usage.%20It%20would%20be%20nice%20to%20get%20some%20guidance%20on%20this%20subject%20from%20Microsoft.%20Any%20pointers%20anyone%20can%20provide%20would%20be%20awesome!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEric%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-330188%22%20slang%3D%22en-US%22%3ERe%3A%20Remove%20TLS%201.0%2F1.1%20and%203DES%20Dependencies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-330188%22%20slang%3D%22en-US%22%3EMy%20report%20Also%20shows%20the%20%2B(Windows%2BNT%2B10.0%3B%2BMicrosoft%2BOutlook%2B16.0.10730%3B%2BPro)%20still%20using%20TLS%201.0%2F1.1%20and%3CBR%20%2F%3ESeveral%20Apple-iPhone%3CBR%20%2F%3EWhat%20%2F%20Why%20would%20the%20two%20items%20be%20on%20the%20list%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-329683%22%20slang%3D%22en-US%22%3ERe%3A%20Remove%20TLS%201.0%2F1.1%20and%203DES%20Dependencies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-329683%22%20slang%3D%22en-US%22%3E%3CP%3EEven%20I%20went%20ahead%20and%20tried%20to%20research%20on%20the%20topic%2C%20no%20such%20information%20is%20available.%26nbsp%3B%3C%2FP%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3E%26nbsp%3BProtocol%3C%2FTD%3E%3CTD%3E%26nbsp%3BAgent%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMacOutlook%2F14.7.2.170228%2B(Intel%2BMac%2BOS%2BX%2B10.9.6)%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BOffice%2F16.0%2B(Windows%2BNT%2B10.0%3B%2BMicrosoft%2BOutlook%2B16.0.11126%3B%2BPro)%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BOffice%2F16.0%2B(Windows%2BNT%2B10.0%3B%2BMicrosoft%2BOutlook%2B16.0.11126%3B%2BPro)%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMacOutlook%2F14.7.2.170228%2B(Intel%2BMac%2BOS%2BX%2B10.9.6)%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BOffice%2F14.0%2B(Windows%2BNT%2B6.1%3B%2BMicrosoft%2BOutlook%2B14.0.7190%3B%2BPro)%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BOffice%2F16.0%2B(Windows%2BNT%2B10.0%3B%2BMicrosoft%2BOutlook%2B16.0.11126%3B%2BPro)%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BOffice%2F16.0%2B(Windows%2BNT%2B10.0%3B%2BMicrosoft%2BOutlook%2B16.0.11126%3B%2BPro)%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BOffice%2F16.0%2B(Windows%2BNT%2B10.0%3B%2BMicrosoft%2BOutlook%2B16.0.11126%3B%2BPro)%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BOffice%2F16.0%2B(Windows%2BNT%2B6.3%3B%2BMicrosoft%2BOutlook%2B16.0.11126%3B%2BPro)%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMacOutlook%2F14.7.2.170228%2B(Intel%2BMac%2BOS%2BX%2B10.9.6)%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EAndroid-SAMSUNG-SM-G570F%2F101.80000%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BOffice%2F16.0%2B(Windows%2BNT%2B10.0%3B%2BMicrosoft%2BOutlook%2B16.0.11126%3B%2BPro)%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMacOutlook%2F14.7.2.170228%2B(Intel%2BMac%2BOS%2BX%2B10.9.6)%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BOffice%2F14.0%2B(Windows%2BNT%2B6.1%3B%2BMicrosoft%2BOutlook%2B14.0.7190%3B%2BPro)%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EAndroid-SAMSUNG-SM-G570F%2F101.700%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMacOutlook%2F14.7.2.170228%2B(Intel%2BMac%2BOS%2BX%2B10.9.6)%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BOffice%2F16.0%2B(Windows%2BNT%2B10.0%3B%2BMicrosoft%2BOutlook%2B16.0.11126%3B%2BPro)%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EApple-iPhone8C1%2F1602.92%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3E-%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMacOutlook%2F14.7.2.170228%2B(Intel%2BMac%2BOS%2BX%2B10.9.6)%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3EMicrosoft%2BBITS%2F7.5%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ETLS1.0%2F1.1%3C%2FTD%3E%3CTD%3E%3CP%3EMicrosoft%2BOffice%2F16.0%2B(Windows%2BNT%2B10.0%3B%2BMicrosoft%2BOutlook%2B16.0.10730%3B%2BPro)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENot%20sure%20why%26nbsp%3B%3CSTRONG%3EMicrosoft%2BOffice%2F16.0%2B(Windows%2BNT%2B10.0%3B%2BMicrosoft%2BOutlook%2B16.0.10730%3B%2BPro)%20still%20using%20TLS%201.0%2F1.1%20%3F%3C%2FSTRONG%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-329606%22%20slang%3D%22en-US%22%3ERe%3A%20Remove%20TLS%201.0%2F1.1%20and%203DES%20Dependencies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-329606%22%20slang%3D%22en-US%22%3EGood%20question!%20I%20don%E2%80%99t%20understand%20why%20Windows%2BNT%2B10.0%20myself.%20So%20looking%20for%20an%20answer%20too.%20In%20fact%20I%20asked%20such%20a%20question%20here%20before.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20had%20learned%20that%20BITS%20is%20used%20to%20download%20the%20address%20book%20(OAB).%20So%20those%20lines%20should%E2%80%A6mean%20Windows%207%2C%20but%20given%20we%20saw%20win10%20above%E2%80%A6%3C%2FLINGO-BODY%3E
Highlighted
Regular Contributor

When I went to http://servicetrust.microsoft.com to see any users still using TLS 1.9/1.1. How do I remove TLS 1.0/1.1. How do I go about making these compatible so they work come February 28, 2019 when Office 365 retires 3DES? Thank you for your help. Here is what I get:

Notice: This report includes 3DES and TLS1.0/1.1 usages.    
     
UserName / IP address Protocol Agent Count Report Date
xxxx@wynnetr.comTLS1.0/1.1Microsoft+BITS/7.5121/30/2019
xxxx@wynnetr.comTLS1.0/1.1Microsoft+Office/16.0+(Windows+NT+10.0;+Microsoft+Outlook+16.0.11126;+Pro)21/30/2019
xxxx@wynnetr.comTLS1.0/1.1Microsoft+Office/16.0+(Windows+NT+10.0;+Microsoft+Outlook+16.0.11126;+Pro)11/30/2019
xxxx@wynnetr.comTLS1.0/1.1Android-SAMSUNG-SM-G930V/101.8000011/30/2019
xxxx@wynnetr.comTLS1.0/1.1Android-SAMSUNG-SM-G360V/101.5010121/30/2019
xxxx@wynnetr.comTLS1.0/1.1Apple-iPhone8C4/1507.7711/30/2019
xxxx@wynnetr.comTLS1.0/1.1Microsoft+BITS/7.581/30/2019
11 Replies
Highlighted
Good question! I don’t understand why Windows+NT+10.0 myself. So looking for an answer too. In fact I asked such a question here before.

I had learned that BITS is used to download the address book (OAB). So those lines should…mean Windows 7, but given we saw win10 above…
Highlighted

Even I went ahead and tried to research on the topic, no such information is available. 

 Protocol Agent
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1MacOutlook/14.7.2.170228+(Intel+Mac+OS+X+10.9.6)
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1Microsoft+Office/16.0+(Windows+NT+10.0;+Microsoft+Outlook+16.0.11126;+Pro)
TLS1.0/1.1Microsoft+Office/16.0+(Windows+NT+10.0;+Microsoft+Outlook+16.0.11126;+Pro)
TLS1.0/1.1MacOutlook/14.7.2.170228+(Intel+Mac+OS+X+10.9.6)
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7190;+Pro)
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1Microsoft+Office/16.0+(Windows+NT+10.0;+Microsoft+Outlook+16.0.11126;+Pro)
TLS1.0/1.1Microsoft+Office/16.0+(Windows+NT+10.0;+Microsoft+Outlook+16.0.11126;+Pro)
TLS1.0/1.1Microsoft+Office/16.0+(Windows+NT+10.0;+Microsoft+Outlook+16.0.11126;+Pro)
TLS1.0/1.1Microsoft+Office/16.0+(Windows+NT+6.3;+Microsoft+Outlook+16.0.11126;+Pro)
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1MacOutlook/14.7.2.170228+(Intel+Mac+OS+X+10.9.6)
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1Android-SAMSUNG-SM-G570F/101.80000
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1Microsoft+Office/16.0+(Windows+NT+10.0;+Microsoft+Outlook+16.0.11126;+Pro)
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1MacOutlook/14.7.2.170228+(Intel+Mac+OS+X+10.9.6)
TLS1.0/1.1Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7190;+Pro)
TLS1.0/1.1Android-SAMSUNG-SM-G570F/101.700
TLS1.0/1.1MacOutlook/14.7.2.170228+(Intel+Mac+OS+X+10.9.6)
TLS1.0/1.1Microsoft+Office/16.0+(Windows+NT+10.0;+Microsoft+Outlook+16.0.11126;+Pro)
TLS1.0/1.1Apple-iPhone8C1/1602.92
TLS1.0/1.1-
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1MacOutlook/14.7.2.170228+(Intel+Mac+OS+X+10.9.6)
TLS1.0/1.1Microsoft+BITS/7.5
TLS1.0/1.1

Microsoft+Office/16.0+(Windows+NT+10.0;+Microsoft+Outlook+16.0.10730;+Pro)

 

 

Not sure why Microsoft+Office/16.0+(Windows+NT+10.0;+Microsoft+Outlook+16.0.10730;+Pro) still using TLS 1.0/1.1 ?

Highlighted
My report Also shows the +(Windows+NT+10.0;+Microsoft+Outlook+16.0.10730;+Pro) still using TLS 1.0/1.1 and
Several Apple-iPhone
What / Why would the two items be on the list?
Highlighted

This is a great question. I have read that the issue with the Apple mail native iPhone app was corrected in iOS 10, but I still see iPhones with iOS 10 showing up on the report. I also see one Microsoft Office 2016 client showing up on the report (using Windows 10 OS). I have no idea why that client machine would be using a lower flavor of TLS. I could disable TLS 1.0 and 1.1 on the client machine, but unfortunately, many websites still use 1.0 for whatever reason.

 

I received an email from Office 365 urging me to run this report, probably like most of you. I ran it and see some TLS 1 usage. It would be nice to get some guidance on this subject from Microsoft. Any pointers anyone can provide would be awesome!

 

Eric

Highlighted

@Alan McFarlane wrote:
I had learned that BITS is used to download the address book (OAB). So those lines should…mean Windows 7, but given we saw win10 above…

 

That sounds like something that Microsoft has to update, as our systems (Office 2016 & Windows 7) support TLS 1.2 for the services that are at that level. But if their services (BITS) isn't supporting it from their end how can we be "compliant"?

Highlighted
Looking on Sunday night at the reports of my ~20 client tenants, there seems to have been a change. None of them now contain any Win10 (Office16/15) entries. So I’m wondering if there was a bug in the reports and it’s been fixed!

Anyone see the same?

The reports look a bit sparse also however. MNy have no rows. Perhaps the school holidays last week meant less folk were connecting? The reports clearly aren’t cumulative over all time, as entries from an older report don’t always appear in a later one. I wonder what needs to happen to make a device appear, is it just to connect to read mail etc, or it that it needs to re-authenticate e.g. after 14 days etc?
Highlighted

I just re-ran the report this morning and have different results also and I did not make any changes or modifications. Here is what I show now and not sure how to fix them. Most of them are on either Android or Apple phones. I still show 1 on Office, not sure what Microsoft+BITS/7.5 is??

Highlighted

The differences in reports on different days might be due to the fact that if a user does not work on a particular day (hence doesn't connect to Office 365) then for that day's report the user will not show up, even though the user is still not compliant. 

 

Then how do we know for sure everyone is compliant, I do not have much clue. Microsoft should have keep listing all users it detected earlier until it detects a compliant connection from the same user.

Highlighted

But iOS is on ver 12 now?!? Who's still on 10?

Found this thread trying to figure out why I have one iPhone (out of a half dozen) showing on my report.

No one figured that out yet?

 

Highlighted

@AliceChained  I have been researching the same thing for the past few hours.  I even went so far as to post a question on the Apple Community .

I am pulling my hair out because I do not use iPhone and unsure how to force them to use TLS 1.2 . 

In my Security Score Report this is what I see;

 Protocol Agent Count
TLS1.0/1.1Apple-iPhone11C8/1604.572
TLS1.0/1.1Apple-iPhone8C1/1604.391
TLS1.0/1.1Apple-iPhone10C4/1604.573

 

I may have found a clue on one of the other MS Exchange blog sites. About half way down in the Notes.  It seems if the client is using Authenticated SMTP the Exchange server logs it wrong and TLS 1.2 may be used after all. This blog is referring to Exchange on-Prem servers so not sure how relevant it is.

If anyone here knows how to configure TLS 1.2 on iPhone native mail app please give me some clues.

Thanks

Highlighted

@Forrest Hoffman From what I've been able to figure out, sometimes these devices just glitch and fail to resolve 1.2, so they fall back to 1.1. Once there is no 1.1 they will stop attempting fall back and will continue to try 1.2 until it succeeds.  

This is so far only my somewhat researched theory. But for example, I will see one iPhone fail today, but succeed tomorrow. This seems to suggest they aren't only able to connect to just 1.1.