BATTLE OF SKM AND IUM

Recommendations

Info

TRUSTLET POLICY / IUM POLICY METADATA • When a Trustlet loads, it must have a Trustlet Policy associated with it • Stored in a variable called s_IumPolicyMetadata, which must be exported • Must be located in a PE section called “.tpolicy”, which must be IMAGE_SCN_CNT_INITIALIZED_DATA | IMAGE_SCN_MEM_READ • The Truslet Policy contains a version (must be 1) and the Trustlet ID of the process • This must match the Secure Process Process Attribute that was passed to CreateProcess • The rest of the policy contains entries for different kinds of features that the Trustlet is allowed to use • EtwAllowed – Sets flag 0x20 in the SKPROCESS structure • Blob is saved at offset 0xC0 in SKPROCESS, to be checked later • Options include DebugEnabled, CrashdumpEnabled, CrashdumpKeyGuid, CrashdumpKey • Checked at runtime by SkpspFindPolicy • SkpsIsProcessDebuggingAllowed, SkpsIsProcessDumpEnabled, SkpsGetTrustletCrashdumpKey
TRUSTLET INSTANCE GUID • Trustlets can also associate an Instance GUID with their process • The same Instance GUID can be used by multiple Trustlets (with different IDs), including Trustlets that are running on different partitions • Instance GUIDs are tied with Hyper-V Partition GUIDs • Allows a Trustlet on a child Hyper-V Partition to identify itself to SKM, as well as a Trustlet on the host partition to identify itself with SKM • Can now use the Secure Storage facility • Instance GUID is set with SetTrustletInstance • This is then stored in the SKPROCESS structure at offset 0x10
Page 1 and 2: BATTLE OF SKM AND IUM HOW WINDOWS 1
Page 3 and 4: PRESENTATION OVERVIEW • Microsoft
Page 5 and 6: VBS FEATURES IN WINDOWS 10 / SERVER
Page 7 and 8: ENABLING VBS
Page 9 and 10: HOW DOES IT ALL WORK? • Hyperviso
Page 11 and 12: SEPARATION OF ROLES • Instead of
Page 13 and 14: PLATFORM REQUIREMENTS • The Boot
Page 15 and 16: HARD CODE GUARANTEES • When hard
Page 17 and 18: VIRTUAL SECURE MODE (VSM) BOOTSTRAP
Page 19 and 20: SKM LAUNCH • To initialize VTL 1,
Page 21 and 22: BCD VSM POLICY OPTIONS • The poli
Page 23 and 24: SKM INTERNALS
Page 25 and 26: SKM STRUCTURES • SKM has a PCR at
Page 27 and 28: SKM CAPABILITIES • The SkCapabili
Page 29 and 30: SECURE MODE CALLS • Secure Mode C
Page 31 and 32: SPECIALIZED SECURE MORE SERVICE CAL
Page 33 and 34: NORMAL MODE SERVICE CALLS • SK ne
Page 35 and 36: IUM INTERNALS
Page 37 and 38: SECURE SYSTEM CALLS • SKM exposes
Page 39 and 40: SECURE BASE API • Trustlets shoul
Page 41 and 42: NOTABLY MISSING… • Trustlets ca
Page 43 and 44: NORMAL MODE SYSTEM CALL PROXYING Th
Page 45 and 46: LAUNCHING A TRUSTLET • Process At
Page 47: EXAMPLE IUM-COMPLIANT SIGNED BINARY
Page 51 and 52: LSA TRUSTLET • One of the two inb
Page 53 and 54: LOADING A TRUSTLET • Ldr, or the
Page 55 and 56: TRUSTLET TO NORMAL WORLD COMMUNICAT
Page 57 and 58: CAN WE BUILD OUR OWN TRUSTLETS? •
Page 59 and 60: CONCLUSION RISKS AND THOUGHTS
Page 61 and 62: SECURE KERNEL COMPLEXITY / ATTACK S
Page 63 and 64: VSM WITHOUT SECUREBOOT • What’s
Page 65: YOU HAVE QUESTIONS? I HOPEFULLY HAV

BATTLE OF SKM AND IUM

Create successful ePaper yourself

Delete template?

Save as template?