Windows Phone 8 provides an application security model based on chambers and capabilities. It utilizes sandboxing, application signing, and encryption to isolate apps and protect sensitive data. The document outlines various application entry points like SD cards, sockets, and URIs that could introduce vulnerabilities if not properly secured. It examines platform-specific issues like privacy leaks from device IDs, secure storage APIs, and mitigations for attacks like XSS, directory traversal, and XML external entity injection. In conclusion, the security model of Windows Phone 8 is assessed to be relatively robust while providing more flexibility than iOS but greater isolation than Android.
Windows Phone 8 Security and Testing WP8 AppsJorge Orchilles
This document discusses security testing of Windows Phone 8 applications. It provides an overview of the Windows Phone 8 platform and architecture, including the use of the NT kernel and sandboxing of applications. Methods for testing applications are covered, including dynamic analysis using a proxy to view network traffic and static analysis by decompiling application files. Vulnerabilities that may be tested for are also outlined, such as lack of encryption or validation of certificates. The document concludes that while application testing depends on access to application files, server and client side testing is similar to other mobile platforms.
Windows Phone 8 provides several security features to protect devices and data, including secure boot to prevent malware installation, device encryption, and application sandboxing. It also supports enterprise management of apps and policies through Exchange ActiveSync or System Center Mobile Device Management for features like remote wiping, password policies, and app distribution controls.
This document summarizes a presentation on inspecting Windows Phone applications for security vulnerabilities. It introduces the speakers and their backgrounds in security research and Windows Phone development. The presentation covers the history and security model of Windows Phone, how applications work, common vulnerabilities, and tools for analyzing applications statically and dynamically. It demonstrates a tool called Tangerine that instruments application bytecode to log method calls and parameters for dynamic analysis. The presentation concludes that the attack surface has increased in Windows Phone 8 and that logical bugs will continue to pose risks.
Reverse engineering and modifying windows 8 appsAmaan Khan
The document discusses security vulnerabilities in Windows 8 apps that allow for reverse engineering and modification. It describes how apps' source code is stored openly on users' machines, allowing easy access and editing of HTML, JavaScript, CSS, XAML, and .NET code. This could enable new viruses, app piracy through modification, and extraction of intellectual property. The author provides steps to access and modify sample apps as proofs of concept and suggests mitigation strategies for Microsoft.
An expert in custom Android malware for penetration testing discussed building custom malware to bypass security controls. The speaker outlined their methodology which included researching existing malware techniques, probing the environment, uploading unmodified malware, and creating altered versions to evade detection. The talk covered functionality like autostarting, collecting device data, and communicating with command and control servers. Various scenarios were proposed like using vulnerable libraries or requesting all permissions to test security controls.
Georgia Weidman discusses various ways that Android permissions can be bypassed, including through exploiting permissions, storing sensitive data without protection, and open interfaces. She demonstrates how apps can abuse permissions to access contacts and send SMS, how unprotected storage allows data access, and how interfaces can be used to trigger SMS sending without consent. Mitigations include securing data, limiting interfaces, and ensuring updates are available to patch vulnerabilities.
This document provides an overview of Android security at the system, application, and enterprise levels. At the system level, it discusses Android architecture, sandboxing, permissions, and security measures like ASLR and NX-bit. It describes application security features like intents, permissions, and application signing. Finally, it outlines enterprise security capabilities such as full-disk encryption, device policies for remote wipe/location, and VPN integration.
Windows Phone 8 provides an application security model based on chambers and capabilities. It utilizes sandboxing, application signing, and encryption to isolate apps and protect sensitive data. The document outlines various application entry points like SD cards, sockets, and URIs that could introduce vulnerabilities if not properly secured. It examines platform-specific issues like privacy leaks from device IDs, secure storage APIs, and mitigations for attacks like XSS, directory traversal, and XML external entity injection. In conclusion, the security model of Windows Phone 8 is assessed to be relatively robust while providing more flexibility than iOS but greater isolation than Android.
Windows Phone 8 Security and Testing WP8 AppsJorge Orchilles
This document discusses security testing of Windows Phone 8 applications. It provides an overview of the Windows Phone 8 platform and architecture, including the use of the NT kernel and sandboxing of applications. Methods for testing applications are covered, including dynamic analysis using a proxy to view network traffic and static analysis by decompiling application files. Vulnerabilities that may be tested for are also outlined, such as lack of encryption or validation of certificates. The document concludes that while application testing depends on access to application files, server and client side testing is similar to other mobile platforms.
Windows Phone 8 provides several security features to protect devices and data, including secure boot to prevent malware installation, device encryption, and application sandboxing. It also supports enterprise management of apps and policies through Exchange ActiveSync or System Center Mobile Device Management for features like remote wiping, password policies, and app distribution controls.
This document summarizes a presentation on inspecting Windows Phone applications for security vulnerabilities. It introduces the speakers and their backgrounds in security research and Windows Phone development. The presentation covers the history and security model of Windows Phone, how applications work, common vulnerabilities, and tools for analyzing applications statically and dynamically. It demonstrates a tool called Tangerine that instruments application bytecode to log method calls and parameters for dynamic analysis. The presentation concludes that the attack surface has increased in Windows Phone 8 and that logical bugs will continue to pose risks.
Reverse engineering and modifying windows 8 appsAmaan Khan
The document discusses security vulnerabilities in Windows 8 apps that allow for reverse engineering and modification. It describes how apps' source code is stored openly on users' machines, allowing easy access and editing of HTML, JavaScript, CSS, XAML, and .NET code. This could enable new viruses, app piracy through modification, and extraction of intellectual property. The author provides steps to access and modify sample apps as proofs of concept and suggests mitigation strategies for Microsoft.
An expert in custom Android malware for penetration testing discussed building custom malware to bypass security controls. The speaker outlined their methodology which included researching existing malware techniques, probing the environment, uploading unmodified malware, and creating altered versions to evade detection. The talk covered functionality like autostarting, collecting device data, and communicating with command and control servers. Various scenarios were proposed like using vulnerable libraries or requesting all permissions to test security controls.
Georgia Weidman discusses various ways that Android permissions can be bypassed, including through exploiting permissions, storing sensitive data without protection, and open interfaces. She demonstrates how apps can abuse permissions to access contacts and send SMS, how unprotected storage allows data access, and how interfaces can be used to trigger SMS sending without consent. Mitigations include securing data, limiting interfaces, and ensuring updates are available to patch vulnerabilities.
This document provides an overview of Android security at the system, application, and enterprise levels. At the system level, it discusses Android architecture, sandboxing, permissions, and security measures like ASLR and NX-bit. It describes application security features like intents, permissions, and application signing. Finally, it outlines enterprise security capabilities such as full-disk encryption, device policies for remote wipe/location, and VPN integration.
This document provides a brief overview of Android security. It discusses how Android uses a combination of mandatory application sandboxing, secure inter-process communication, application signing, and permission models to isolate applications and protect the operating system and user data. It also describes some key aspects of the Android security architecture including protections built into the Linux kernel, techniques for preventing and minimizing the impact of security breaches, and mechanisms for automatically updating applications. Finally, it discusses some common Android security threats and how projects like TaintDroid aim to track and prevent privacy leaks on Android devices.
Pwning Windows Mobile applications by Ankit GiriOWASP Delhi
Mobile Platform Operating Systems
Windows Phone Overview
What we can test?
Challenges
Approach & Prerequisites
Methodology
Application File Structure
Tools for Penetration Testing
Security Features
This document provides an overview of Android security. It discusses Android's architecture including activities, services, content providers and broadcast receivers. It then covers Android security features like application sandboxing, application signing, and Android's permission model. It provides examples of how these components and security features work together in a sample Android application for tracking friends' locations. It also discusses how applications can programmatically enforce permissions and how application components interact through intents.
The document discusses Android security and provides an overview of key topics. It begins with Android basics and versions. It then covers the Android security model including application sandboxing and permissions. It defines Android applications and their components. It discusses debates on whether Android is more secure than iOS and outlines multiple layers of Android security. It also addresses Android malware, anti-virus effectiveness, rooting, application vulnerabilities, and security issues.
Analysis and research of system security based on androidRavishankar Kumar
The document discusses mobile security and the Android operating system. It provides an overview of why mobile security is important, what Android is, how to develop for Android, and Android security features. It discusses threats like malware, data theft, and device loss. It then covers key aspects of the Android security model like application sandboxes, data storage options, permissions, and cryptography. Finally, it provides examples of security applications like Lookout Antivirus and App Lock.
Video at http://mrkn.co/andsec
With Android activations reaching a million devices per day, it is no surprise that security threats against our favorite mobile platform have been on the rise.
In this session, you will learn all about Android's security model, including application isolation (sandboxing) and provenance (signing), its permission system and enforcement, data protection features and encryption, as well as enterprise device administration.
Together, we will dig into Android's own internals to see how its security model is applied through the entire Android stack - from the Linux kernel, to the native layers, to the Application Framework services, and to the applications themselves.
Finally, you’ll learn about some of the weaknesses in the Android's model (including rooting, tap-jacking, malware, social-engineering) as well as what can be done to mitigate those threats, such as SE-Linux, memory protection, anti-malware, firewall, and developer best practices.
By the end of this session you will have a better understanding of what it takes to make Android a more trusted component of our personal and professional lives.
Introduction to Android Development and SecurityKelwin Yang
This document provides an introduction to Android development and security. It begins with a brief history of Android and overview of its architecture. It then discusses the Android development environment and process, including key tools and frameworks. It also outlines Android security features like application sandboxing, permissions, and encryption. Finally, it introduces a series of Android security labs that demonstrate exploits like parameter manipulation, insecure storage, and memory attacks. The goal is to provide hands-on examples of common Android vulnerabilities.
The document discusses Microsoft Intune and device management capabilities. It provides an overview of Intune's management of PCs, mobile phones and tablets including application management, patch management and antivirus. It also discusses options for mobile device management including direct enrollment of devices and management through Exchange ActiveSync. Requirements and capabilities for managing different device platforms like Windows, iOS and Android are outlined. The document demonstrates Intune's management of PCs, identity management and mobile device management features.
RSA SF Conference talk-2009-ht2-401 sallamAhmed Sallam
- The document discusses how ordinary people can understand Windows code despite it previously being kept secret.
- It outlines resources now available from Microsoft to learn Windows internals like debuggers, symbol files, documentation and communities. Skills needed are also discussed.
- Case studies are presented showing how tools like debuggers and disassemblers can be used to understand techniques used by rootkits and find undocumented Windows functions.
- In conclusion, the document argues Windows code is not as secret as assumed and many means exist for both security experts and developers to learn it through resources Microsoft now provides.
This presentation done for my MSc studies @ UOM. The presentation is related to the paper "Understanding Android Security" by William Enck, Machigar Ongtang, and Patrick McDaniel. Pennsylvania State University on 2009
The document discusses various security threats related to Android applications. It begins by introducing the OWASP Mobile Top 10 risks framework for categorizing common mobile vulnerabilities. It then provides more details on each of the top 10 risk categories, including examples, impacts, and tips for prevention. It also discusses techniques for protecting Android apps from reverse engineering and tampering, such as code obfuscation, anti-debugging, and license verification.
The document discusses best practices for building secure Android apps for enterprise use. It covers an overview of mobility and mobile security, secure software development practices, the Android security architecture including permission-based security and sandboxing, common Android attack surfaces, and enterprise features in Android like remote wipe that can be leveraged. The presentation emphasizes designing apps with user authentication, data security on devices, secure data transmission, and device management and provisioning.
Ahmed sallam technical_journey_1992_1999Ahmed Sallam
Author, Ahmed Said Sallam is known for his work in the US on computer system security and virtualization. Very little has been told about his work beginning of his career in the period 1992-1999. It was great system work performed at a very early stage of the PC era and Internet time.
This is an attempt to document such journey methodically. Hopefully, it will inspire younger generation to focus on science and technology as a mean to generate value, create jobs, build smart communities and transform societies.
Android is an open-source operating system used for mobile devices. It was developed by Android Inc., which was purchased by Google in 2005. Android is based on the Linux kernel and allows developers to write managed code using Java. The Android software stack consists of applications, an application framework, libraries and runtime, and the Linux kernel. Android uses security features like process isolation and permissions to protect applications and user data. It has many features like customization, notifications, app market support, and integration with Google services. However, it also faces limitations like inconsistent designs between apps, unstable performance, and lack of support for some Bluetooth functions.
DEBUNKING ANDROID SECURITY MYTHS WITH DATA
In this talk I’m presenting some hot topics for European Corporation in the process to adopt Android as COSU devices.
How features introduced in Android 6.0, Google Mobile Services and third party extensions collaborate to provide to the market state of art solutions.
This talk will answer to questions like:
1. Android threats, real or FUD?
2. Security updates, why are they critical for the Enterprise market
3. Security and Long Life Cycle of Android devices, what are the market best practices
This session is powered by Zebra
The document discusses mobile application security. It describes challenges in managing and securing mobile devices and applications. It introduces IBM's mobile security strategy and solutions that address these challenges, including managing mobile devices, protecting data and network access, and developing secure mobile applications. The solutions provide capabilities such as mobile device management, data encryption, identity and access management, and application testing.
This document discusses various aspects of securing Android development including permissions, encryption, API management, and more. It addresses securing the USB, screen, clipboard, and databases. It recommends using Android NDK for cryptography to make analysis harder. API access should use randomly generated access tokens that are tied to the user ID and hardware ID and refreshed periodically. Encryption should be done with keys derived from random, hardware ID, and user-provided values.
Christchurch Embedded .NET User Group - Introduction to Microsoft Embedded pl...christopherfairbairn
Part 1 of the first session of the newly formed Christchurch Embedded .NET User Group.
Introduces the range of embedded platforms and technologies offered by Microsoft. Covers the .NET Micro and Compact Frameworks as well as operating systems such as Windows Embedded CE and Windows Mobile.
Presented by Andrew Leckie, Bryn Lewis and myself.
Runtime 8 provides a common application programming interface and runtime across Windows 8, Windows Phone 8, and Windows Server 2012. It allows developers to write code once and deploy it across these platforms, simplifying development. Some key aspects of Runtime 8 include a new type system, app deployment options through the Windows Store or sideloading, and common APIs for networking, sensors, storage and more. It aims to unify development across platforms.
Windows Phone 8 Advanced Developers ConferenceDamir Dobric
Windows Phone 8 introduced a new "Runtime 8" platform that provides backwards compatibility with Windows Phone 7 apps. It allows code sharing between Windows Phone 8, Windows 8, and portable class libraries. The Windows Phone 8 SDK added new APIs, supported additional languages like JavaScript, and improved areas like multitasking, networking, and in-app purchasing.
This document provides a brief overview of Android security. It discusses how Android uses a combination of mandatory application sandboxing, secure inter-process communication, application signing, and permission models to isolate applications and protect the operating system and user data. It also describes some key aspects of the Android security architecture including protections built into the Linux kernel, techniques for preventing and minimizing the impact of security breaches, and mechanisms for automatically updating applications. Finally, it discusses some common Android security threats and how projects like TaintDroid aim to track and prevent privacy leaks on Android devices.
Pwning Windows Mobile applications by Ankit GiriOWASP Delhi
Mobile Platform Operating Systems
Windows Phone Overview
What we can test?
Challenges
Approach & Prerequisites
Methodology
Application File Structure
Tools for Penetration Testing
Security Features
This document provides an overview of Android security. It discusses Android's architecture including activities, services, content providers and broadcast receivers. It then covers Android security features like application sandboxing, application signing, and Android's permission model. It provides examples of how these components and security features work together in a sample Android application for tracking friends' locations. It also discusses how applications can programmatically enforce permissions and how application components interact through intents.
The document discusses Android security and provides an overview of key topics. It begins with Android basics and versions. It then covers the Android security model including application sandboxing and permissions. It defines Android applications and their components. It discusses debates on whether Android is more secure than iOS and outlines multiple layers of Android security. It also addresses Android malware, anti-virus effectiveness, rooting, application vulnerabilities, and security issues.
Analysis and research of system security based on androidRavishankar Kumar
The document discusses mobile security and the Android operating system. It provides an overview of why mobile security is important, what Android is, how to develop for Android, and Android security features. It discusses threats like malware, data theft, and device loss. It then covers key aspects of the Android security model like application sandboxes, data storage options, permissions, and cryptography. Finally, it provides examples of security applications like Lookout Antivirus and App Lock.
Video at http://mrkn.co/andsec
With Android activations reaching a million devices per day, it is no surprise that security threats against our favorite mobile platform have been on the rise.
In this session, you will learn all about Android's security model, including application isolation (sandboxing) and provenance (signing), its permission system and enforcement, data protection features and encryption, as well as enterprise device administration.
Together, we will dig into Android's own internals to see how its security model is applied through the entire Android stack - from the Linux kernel, to the native layers, to the Application Framework services, and to the applications themselves.
Finally, you’ll learn about some of the weaknesses in the Android's model (including rooting, tap-jacking, malware, social-engineering) as well as what can be done to mitigate those threats, such as SE-Linux, memory protection, anti-malware, firewall, and developer best practices.
By the end of this session you will have a better understanding of what it takes to make Android a more trusted component of our personal and professional lives.
Introduction to Android Development and SecurityKelwin Yang
This document provides an introduction to Android development and security. It begins with a brief history of Android and overview of its architecture. It then discusses the Android development environment and process, including key tools and frameworks. It also outlines Android security features like application sandboxing, permissions, and encryption. Finally, it introduces a series of Android security labs that demonstrate exploits like parameter manipulation, insecure storage, and memory attacks. The goal is to provide hands-on examples of common Android vulnerabilities.
The document discusses Microsoft Intune and device management capabilities. It provides an overview of Intune's management of PCs, mobile phones and tablets including application management, patch management and antivirus. It also discusses options for mobile device management including direct enrollment of devices and management through Exchange ActiveSync. Requirements and capabilities for managing different device platforms like Windows, iOS and Android are outlined. The document demonstrates Intune's management of PCs, identity management and mobile device management features.
RSA SF Conference talk-2009-ht2-401 sallamAhmed Sallam
- The document discusses how ordinary people can understand Windows code despite it previously being kept secret.
- It outlines resources now available from Microsoft to learn Windows internals like debuggers, symbol files, documentation and communities. Skills needed are also discussed.
- Case studies are presented showing how tools like debuggers and disassemblers can be used to understand techniques used by rootkits and find undocumented Windows functions.
- In conclusion, the document argues Windows code is not as secret as assumed and many means exist for both security experts and developers to learn it through resources Microsoft now provides.
This presentation done for my MSc studies @ UOM. The presentation is related to the paper "Understanding Android Security" by William Enck, Machigar Ongtang, and Patrick McDaniel. Pennsylvania State University on 2009
The document discusses various security threats related to Android applications. It begins by introducing the OWASP Mobile Top 10 risks framework for categorizing common mobile vulnerabilities. It then provides more details on each of the top 10 risk categories, including examples, impacts, and tips for prevention. It also discusses techniques for protecting Android apps from reverse engineering and tampering, such as code obfuscation, anti-debugging, and license verification.
The document discusses best practices for building secure Android apps for enterprise use. It covers an overview of mobility and mobile security, secure software development practices, the Android security architecture including permission-based security and sandboxing, common Android attack surfaces, and enterprise features in Android like remote wipe that can be leveraged. The presentation emphasizes designing apps with user authentication, data security on devices, secure data transmission, and device management and provisioning.
Ahmed sallam technical_journey_1992_1999Ahmed Sallam
Author, Ahmed Said Sallam is known for his work in the US on computer system security and virtualization. Very little has been told about his work beginning of his career in the period 1992-1999. It was great system work performed at a very early stage of the PC era and Internet time.
This is an attempt to document such journey methodically. Hopefully, it will inspire younger generation to focus on science and technology as a mean to generate value, create jobs, build smart communities and transform societies.
Android is an open-source operating system used for mobile devices. It was developed by Android Inc., which was purchased by Google in 2005. Android is based on the Linux kernel and allows developers to write managed code using Java. The Android software stack consists of applications, an application framework, libraries and runtime, and the Linux kernel. Android uses security features like process isolation and permissions to protect applications and user data. It has many features like customization, notifications, app market support, and integration with Google services. However, it also faces limitations like inconsistent designs between apps, unstable performance, and lack of support for some Bluetooth functions.
DEBUNKING ANDROID SECURITY MYTHS WITH DATA
In this talk I’m presenting some hot topics for European Corporation in the process to adopt Android as COSU devices.
How features introduced in Android 6.0, Google Mobile Services and third party extensions collaborate to provide to the market state of art solutions.
This talk will answer to questions like:
1. Android threats, real or FUD?
2. Security updates, why are they critical for the Enterprise market
3. Security and Long Life Cycle of Android devices, what are the market best practices
This session is powered by Zebra
The document discusses mobile application security. It describes challenges in managing and securing mobile devices and applications. It introduces IBM's mobile security strategy and solutions that address these challenges, including managing mobile devices, protecting data and network access, and developing secure mobile applications. The solutions provide capabilities such as mobile device management, data encryption, identity and access management, and application testing.
This document discusses various aspects of securing Android development including permissions, encryption, API management, and more. It addresses securing the USB, screen, clipboard, and databases. It recommends using Android NDK for cryptography to make analysis harder. API access should use randomly generated access tokens that are tied to the user ID and hardware ID and refreshed periodically. Encryption should be done with keys derived from random, hardware ID, and user-provided values.
Christchurch Embedded .NET User Group - Introduction to Microsoft Embedded pl...christopherfairbairn
Part 1 of the first session of the newly formed Christchurch Embedded .NET User Group.
Introduces the range of embedded platforms and technologies offered by Microsoft. Covers the .NET Micro and Compact Frameworks as well as operating systems such as Windows Embedded CE and Windows Mobile.
Presented by Andrew Leckie, Bryn Lewis and myself.
Runtime 8 provides a common application programming interface and runtime across Windows 8, Windows Phone 8, and Windows Server 2012. It allows developers to write code once and deploy it across these platforms, simplifying development. Some key aspects of Runtime 8 include a new type system, app deployment options through the Windows Store or sideloading, and common APIs for networking, sensors, storage and more. It aims to unify development across platforms.
Windows Phone 8 Advanced Developers ConferenceDamir Dobric
Windows Phone 8 introduced a new "Runtime 8" platform that provides backwards compatibility with Windows Phone 7 apps. It allows code sharing between Windows Phone 8, Windows 8, and portable class libraries. The Windows Phone 8 SDK added new APIs, supported additional languages like JavaScript, and improved areas like multitasking, networking, and in-app purchasing.
Windows Phone 8 introduced a new "Runtime 8" platform that provides backwards compatibility with Windows Phone 7 apps. It allows code sharing between Windows Phone 8, Windows 8, and portable class libraries. The Windows Phone 8 SDK added new APIs, supported additional languages like JavaScript, and improved areas like threading, in-app purchasing, and connectivity.
Security of Windows 10 IoT Core(FFRI Monthly Research 201506)FFRI, Inc.
•Windows 10 IoT is successor platform of Windows Embedded that optimized for embedded devices.
•Windows 10 IoT Core Insider Preview has been provided for single-board computers such as the Raspberry Pi 2.
•We show tutorial about security of Windows 10 IoT Core using the Raspberry Pi 2.
EclipseEmbeddedDay2009-OSGi: Best Tool In Your Embedded Systems ToolboxBrett Hackleman
We discuss several of our past and current OSGi-based solutions for defense systems, mining equipment, construction equipment, industrial automation, and automotive/telematics domains. We present some best practices for building flexible, cross-platform, high-performance embedded application and the resulting lessons learned along the way. We demonstrate how the Eclipse Runtime Components and Frameworks can be used to access communication buses such as CAN, J1939, J1850, and MIL-STD-1553. Finally, we explain how using OSGi and Equinox can simplify the development, testing, and deployment of your next application, whether embedded or not.
The document discusses using the Eclipse framework and OSGi for developing modular applications for embedded devices. It describes challenges in embedded systems development and how OSGi addresses these challenges through loose coupling and dynamic updating. It also summarizes several Eclipse projects - DeviceKit for hardware interfacing, an industrial graphics framework, and p2 for remote provisioning - and provides examples of applications developed with these technologies, including for the US Army.
This document discusses embedded operating systems and processors. It covers several embedded operating systems including DOS, QNX, Embedded Linux, and Microsoft embedded operating systems. It also discusses embedded processors from Intel, AMD, DMP and VIA with specifications for the Geode LX, GX2, and CX series. The document provides an overview of options for embedded operating systems and processors.
The opening address for the Windows Embedded & Robotics European Campus Tour. This presentation provides an overview of the Embedded Windows technology available and lots of examples of its use.
FinFisher is cyber espionage software sold by Gamma Group to law enforcement and intelligence agencies. It can infect Windows, iOS, Android, Blackberry, Symbian, and other mobile devices to monitor users. The malware disguises itself using various techniques and communicates with command and control servers located around the world. It has extensive surveillance capabilities including recording calls, intercepting messages, and tracking locations.
Windows Mobile is a compact operating system for mobile devices based on the Win32 API. It can run on Pocket PCs, smartphones, portable media centers, and automotive devices. The document discusses the Windows Mobile platform, including supported hardware, operating systems, network connectivity options, security features, and performance. It also covers software development for Windows Mobile, including required tools, programming languages like C++, C#, and VB, and an overall evaluation of advantages and limitations.
UEFI Firmware Rootkits: Myths and RealitySally Feller
Earlier this month, we teased a proof of concept for UEFI ransomware which was presented at RSA Conference 2017. The HackingTeam, Snowden, Shadow Brokers, and Vault7 leaks have revealed that UEFI/BIOS implants aren't just a theoretical concept but have actually been weaponized by nation states to conduct cyber espionage. Physical access requirements are a thing of the past, these low level implants can be installed remotely by exploiting vulnerabilities in the underlying UEFI system.
Today at BlackHat Asia 2017, we are disclosing two vulnerabilities in two different models of the GIGABYTE BRIX platform:
GB-BSi7H-6500 – firmware version: vF6 (2016/05/18)
GB-BXi7-5775 – firmware version: vF2 (2016/07/19)
OSGi: Best Tool In Your Embedded Systems ToolboxBrett Hackleman
We discuss several of our past and current OSGi-based solutions for defense systems, mining equipment, construction equipment, industrial automation, and automotive/telematics domains. We present some best practices for building flexible, cross-platform, high-performance embedded application and the resulting lessons learned along the way. We demonstrate how the Eclipse Runtime Components and Frameworks can be used to access communication buses such as CAN, J1939, J1850, and MIL-STD-1553. Finally, we explain how using OSGi and Equinox can simplify the development, testing, and deployment of your next application, whether embedded or not.
Windows 10 IoT provides operating systems for a variety of devices from small devices to industrial systems and gateways. It offers free and paid editions across x86, ARM, and other architectures. The platforms are designed to easily integrate sensors and peripherals while providing security and manageability features along with connections to Azure IoT services and tools to configure and deploy devices.
Mansih Chasta is a principal consultant at Indusface with over 6 years of experience in information and application security. The document discusses an upcoming training on analyzing and reverse engineering Android applications. It will cover topics like the Android SDK, setting up a GoatDroid application, memory analysis, intercepting layer 7 traffic, reverse engineering Android apps, SQLite database analysis, and demonstrating exploits on an ExploitMe application. Statistics are provided on growth in mobile app downloads from 2010 to 2014.
Software update for IoT: the current state of playChris Simmonds
Many embedded Linux projects have a requirement to update the software on devices in the field. Recent security flaws in basic components such as OpenSSL and bash, combined with the interconnectedness of all things, have highlighted the problem and made it an absolute necessity
The document discusses attacking proprietary Android vendor customizations through fuzz testing and fault injection testing. It presents Chizpurfle, a gray-box Android fuzzer designed to generate invalid inputs to identify vulnerabilities in vendor customization code without access to source code. Chizpurfle leverages dynamic instrumentation to trace code coverage on actual devices during fuzzing. It detected two bugs from fuzzing Samsung services. The document also discusses a fault injection testing tool that injects faults into Android components to evaluate failure propagation and mitigation. The tool found vendors have varying success in handling faults across components.
This document contains the professional summary and work experience of Albin B. It highlights his extensive experience in developing device drivers across various platforms including Linux, Android, QNX RTOS and Windows. He has hands-on experience in areas such as Linux device driver development, Android kernel and drivers, QNX RTOS drivers and diagnostics software, and Windows device drivers. He also lists technical skills in C/C++, protocols, tools and compilers. Specific work projects are outlined for Android mobile development at Intel and Samsung, QNX diagnostic software, and Linux and Windows driver development.
Reducing attack surface on ICS with Windows native solutionsJan Seidl
This document summarizes steps for hardening Windows systems used in industrial control systems (ICS). It recommends:
1. Performing basic hardening steps like removing unnecessary software, disabling services, and restricting file system access.
2. Leveraging the native Windows firewall to prevent backdoors and malware from communicating.
3. Implementing whitelisting of authorized software using Software Restriction Policies or AppLocker to prevent unauthorized code execution.
4. Using Enhanced Mitigation Experience Toolkit (EMET) for exploitation mitigation to reduce the impact of zero-day vulnerabilities.
5. Leveraging PowerShell remoting and Just Enough Administration (JEA) to restrict remote access without using
Similar to Windows Phone Application Penetration Testing (20)
2. Windows Phone
Overview
Approach
Application File
Structure
Tools for Penetration
Testing
Security Features
PenetrationTesting of Windows Phone Applications
3. Microsoft’s Own OS
Based onWindows 8 Core – ARM Architecture
History
The successor to theWindows Mobile OS
- 15 Mar 2010 –Windows Phone 7 series announced
- 21 Oct 2010 –Windows Phone 7 released
- 29 Oct 2012 –Windows Phone 8 released With the GDR 2 (Amber)
& GDR 3 (Black) Updates
PenetrationTesting of Windows Phone Applications
4. NTFS file system support
BitLocker device encryption
Sandboxed applications: Applications run in their own sandboxed
virtual environment
UEFI Secure boot: Unified Extensible Firmware Interface (UEFI) is
the successor to the legacy BIOS firmware interface. UEFI relies on
theTrusted Platform Module (TPM) 2.0 standard requiring unique
keys to be burned into the chip during production to restrict
software without correct digital signature to execute.
AllWindows Phone 8 binaries must have digital signatures signed
by Microsoft to run
PenetrationTesting of Windows Phone Applications
5. Chamber Concept (WP7)
Trusted Computing Base
(TCB)
▪ Kernel, kernel-mode drivers
- Elevated Rights Chamber
(ERC)
▪ Services, user-mode drivers
- Standard Rights Chamber
(SRC)
▪ Pre-installed applications
- Least PrivilegedChamber
(LPC)
▪ Applications from WP store
PenetrationTesting of Windows Phone Applications
6. Chamber Concept (WP8)
Trusted Computing Base (TCB)
▪ Kernel, kernel-mode drivers
- Least Privileged Chamber (LPC)
All other software: services,
pre-installed apps, application
fromWP store
PenetrationTesting of Windows Phone Applications
9. Emulator /Windows Phone SDK
Unlocked Device
Side Loading
Developer Unlock – Free Unlock with 2 Apps Limit
Student Unlock – Up to 3 Apps
Limitations
Apps from the store cannot be extracted
Apps from the store will not work on emulators
PenetrationTesting of Windows Phone Applications
10. Burp Suite
WP Power tools
.NET Reflector
PenetrationTesting of Windows Phone Applications