home.social

#iosforensics — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #iosforensics, aggregated by home.social.

fetched live
  1. Every Apple Unified Log predicate iLEAPP searches for, artifact by artifact.

    34 artifacts, 230 predicates. Calls, typing, Face ID and Touch ID frames, touch contact, pocket state, camera, AirDrop, Bluetooth pairing, driving state.

    Each one is documented in published research, observed on real iOS 16.5/17.1/18.7 extractions, or both. The guide says which, per pattern, and what did not make the cut.

    Free, PDF included.

    leapps.org/blog-post?post=2026

    #DFIR #iOSForensics

  2. Every Apple Unified Log predicate iLEAPP searches for, artifact by artifact.

    34 artifacts, 230 predicates. Calls, typing, Face ID and Touch ID frames, touch contact, pocket state, camera, AirDrop, Bluetooth pairing, driving state.

    Each one is documented in published research, observed on real iOS 16.5/17.1/18.7 extractions, or both. The guide says which, per pattern, and what did not make the cut.

    Free, PDF included.

    leapps.org/blog-post?post=2026

    #DFIR #iOSForensics

  3. Every Apple Unified Log predicate iLEAPP searches for, artifact by artifact.

    34 artifacts, 230 predicates. Calls, typing, Face ID and Touch ID frames, touch contact, pocket state, camera, AirDrop, Bluetooth pairing, driving state.

    Each one is documented in published research, observed on real iOS 16.5/17.1/18.7 extractions, or both. The guide says which, per pattern, and what did not make the cut.

    Free, PDF included.

    leapps.org/blog-post?post=2026

    #DFIR #iOSForensics

  4. Every Apple Unified Log predicate iLEAPP searches for, artifact by artifact.

    34 artifacts, 230 predicates. Calls, typing, Face ID and Touch ID frames, touch contact, pocket state, camera, AirDrop, Bluetooth pairing, driving state.

    Each one is documented in published research, observed on real iOS 16.5/17.1/18.7 extractions, or both. The guide says which, per pattern, and what did not make the cut.

    Free, PDF included.

    leapps.org/blog-post?post=2026

    #DFIR #iOSForensics

  5. Every Apple Unified Log predicate iLEAPP searches for, artifact by artifact.

    34 artifacts, 230 predicates. Calls, typing, Face ID and Touch ID frames, touch contact, pocket state, camera, AirDrop, Bluetooth pairing, driving state.

    Each one is documented in published research, observed on real iOS 16.5/17.1/18.7 extractions, or both. The guide says which, per pattern, and what did not make the cut.

    Free, PDF included.

    leapps.org/blog-post?post=2026

    #DFIR #iOSForensics

  6. Apple Unified Logs are no longer an edge-case data source.

    🔒 Lock/unlock activity
    📱 App launches
    📶 Connectivity changes
    📸 Screenshots
    🧭 Navigation

    My updated article covers acquisition, macOS 26.4 Info.plist requirements, iLEAPP processing, 132 message predicates across 23 evidentiary themes, and analysis in LAVA/SQLite.

    Article + printable guide:
    leapps.org/blog-post?post=2026

    #DFIR #iOSForensics #DigitalForensics #iLEAPP

  7. Apple Unified Logs are no longer an edge-case data source.

    🔒 Lock/unlock activity
    📱 App launches
    📶 Connectivity changes
    📸 Screenshots
    🧭 Navigation

    My updated article covers acquisition, macOS 26.4 Info.plist requirements, iLEAPP processing, 132 message predicates across 23 evidentiary themes, and analysis in LAVA/SQLite.

    Article + printable guide:
    leapps.org/blog-post?post=2026

    #DFIR #iOSForensics #DigitalForensics #iLEAPP

  8. Apple Unified Logs are no longer an edge-case data source.

    🔒 Lock/unlock activity
    📱 App launches
    📶 Connectivity changes
    📸 Screenshots
    🧭 Navigation

    My updated article covers acquisition, macOS 26.4 Info.plist requirements, iLEAPP processing, 132 message predicates across 23 evidentiary themes, and analysis in LAVA/SQLite.

    Article + printable guide:
    leapps.org/blog-post?post=2026

    #DFIR #iOSForensics #DigitalForensics #iLEAPP

  9. Apple Unified Logs are no longer an edge-case data source.

    🔒 Lock/unlock activity
    📱 App launches
    📶 Connectivity changes
    📸 Screenshots
    🧭 Navigation

    My updated article covers acquisition, macOS 26.4 Info.plist requirements, iLEAPP processing, 132 message predicates across 23 evidentiary themes, and analysis in LAVA/SQLite.

    Article + printable guide:
    leapps.org/blog-post?post=2026

    #DFIR #iOSForensics #DigitalForensics #iLEAPP

  10. Apple Unified Logs are no longer an edge-case data source.

    🔒 Lock/unlock activity
    📱 App launches
    📶 Connectivity changes
    📸 Screenshots
    🧭 Navigation

    My updated article covers acquisition, macOS 26.4 Info.plist requirements, iLEAPP processing, 132 message predicates across 23 evidentiary themes, and analysis in LAVA/SQLite.

    Article + printable guide:
    leapps.org/blog-post?post=2026

    #DFIR #iOSForensics #DigitalForensics #iLEAPP

  11. Mattia Epifani published "84 Streams Later", tracking Apple Biome from iOS 14 through iOS 26 and what it means for examiners.

    Community work at its best: he found the streams and shared samples, we wrote and validated the parsers. iLEAPP went from 45 Biome artifacts to 101 in two days.

    Where we could check a field against another source on the same device, we did. Call direction against CallHistory, message direction against sms.db, lock state against the DKEvent streams. Where we could not confirm a value, the column says raw and the notes say why.

    Run from python code to benefit today. Parsers will be added to the next tool release soon

    Free and open source, as always.

    Blog: blog.digital-forensics.it/2026 iLEAPP: leapps.org/releases#section-il

    #DFIR #MobileForensics #iOSForensics

  12. Mattia Epifani published "84 Streams Later", tracking Apple Biome from iOS 14 through iOS 26 and what it means for examiners.

    Community work at its best: he found the streams and shared samples, we wrote and validated the parsers. iLEAPP went from 45 Biome artifacts to 101 in two days.

    Where we could check a field against another source on the same device, we did. Call direction against CallHistory, message direction against sms.db, lock state against the DKEvent streams. Where we could not confirm a value, the column says raw and the notes say why.

    Run from python code to benefit today. Parsers will be added to the next tool release soon

    Free and open source, as always.

    Blog: blog.digital-forensics.it/2026 iLEAPP: leapps.org/releases#section-il

    #DFIR #MobileForensics #iOSForensics

  13. Mattia Epifani published "84 Streams Later", tracking Apple Biome from iOS 14 through iOS 26 and what it means for examiners.

    Community work at its best: he found the streams and shared samples, we wrote and validated the parsers. iLEAPP went from 45 Biome artifacts to 101 in two days.

    Where we could check a field against another source on the same device, we did. Call direction against CallHistory, message direction against sms.db, lock state against the DKEvent streams. Where we could not confirm a value, the column says raw and the notes say why.

    Run from python code to benefit today. Parsers will be added to the next tool release soon

    Free and open source, as always.

    Blog: blog.digital-forensics.it/2026 iLEAPP: leapps.org/releases#section-il

    #DFIR #MobileForensics #iOSForensics

  14. Mattia Epifani published "84 Streams Later", tracking Apple Biome from iOS 14 through iOS 26 and what it means for examiners.

    Community work at its best: he found the streams and shared samples, we wrote and validated the parsers. iLEAPP went from 45 Biome artifacts to 101 in two days.

    Where we could check a field against another source on the same device, we did. Call direction against CallHistory, message direction against sms.db, lock state against the DKEvent streams. Where we could not confirm a value, the column says raw and the notes say why.

    Run from python code to benefit today. Parsers will be added to the next tool release soon

    Free and open source, as always.

    Blog: blog.digital-forensics.it/2026 iLEAPP: leapps.org/releases#section-il

    #DFIR #MobileForensics #iOSForensics

  15. Mattia Epifani published "84 Streams Later", tracking Apple Biome from iOS 14 through iOS 26 and what it means for examiners.

    Community work at its best: he found the streams and shared samples, we wrote and validated the parsers. iLEAPP went from 45 Biome artifacts to 101 in two days.

    Where we could check a field against another source on the same device, we did. Call direction against CallHistory, message direction against sms.db, lock state against the DKEvent streams. Where we could not confirm a value, the column says raw and the notes say why.

    Run from python code to benefit today. Parsers will be added to the next tool release soon

    Free and open source, as always.

    Blog: blog.digital-forensics.it/2026 iLEAPP: leapps.org/releases#section-il

    #DFIR #MobileForensics #iOSForensics

  16. New iLEAPP artifact: Biome - Device TimeZone, contributed by Cynthia van Dorp.

    Starting around iOS 17, the Device.TimeZone biome stream keeps a record of every timezone the device switches into, each entry with a SEGB timestamp. That means a built-in travel timeline: on one of our test images the output showed the device going New York, then Chicago, then Honolulu, then back, all with exact times.

    Tested against 8 iOS 17 and 18 images from our corpus before merging. Free and open source, as always.

    #DFIR #iosforensics #mobileforensics

  17. New iLEAPP artifact: Biome - Device TimeZone, contributed by Cynthia van Dorp.

    Starting around iOS 17, the Device.TimeZone biome stream keeps a record of every timezone the device switches into, each entry with a SEGB timestamp. That means a built-in travel timeline: on one of our test images the output showed the device going New York, then Chicago, then Honolulu, then back, all with exact times.

    Tested against 8 iOS 17 and 18 images from our corpus before merging. Free and open source, as always.

    #DFIR #iosforensics #mobileforensics

  18. New iLEAPP artifact: Biome - Device TimeZone, contributed by Cynthia van Dorp.

    Starting around iOS 17, the Device.TimeZone biome stream keeps a record of every timezone the device switches into, each entry with a SEGB timestamp. That means a built-in travel timeline: on one of our test images the output showed the device going New York, then Chicago, then Honolulu, then back, all with exact times.

    Tested against 8 iOS 17 and 18 images from our corpus before merging. Free and open source, as always.

    #DFIR #iosforensics #mobileforensics

  19. New iLEAPP artifact: Biome - Device TimeZone, contributed by Cynthia van Dorp.

    Starting around iOS 17, the Device.TimeZone biome stream keeps a record of every timezone the device switches into, each entry with a SEGB timestamp. That means a built-in travel timeline: on one of our test images the output showed the device going New York, then Chicago, then Honolulu, then back, all with exact times.

    Tested against 8 iOS 17 and 18 images from our corpus before merging. Free and open source, as always.

    #DFIR #iosforensics #mobileforensics

  20. New iLEAPP artifact: Biome - Device TimeZone, contributed by Cynthia van Dorp.

    Starting around iOS 17, the Device.TimeZone biome stream keeps a record of every timezone the device switches into, each entry with a SEGB timestamp. That means a built-in travel timeline: on one of our test images the output showed the device going New York, then Chicago, then Honolulu, then back, all with exact times.

    Tested against 8 iOS 17 and 18 images from our corpus before merging. Free and open source, as always.

    #DFIR #iosforensics #mobileforensics

  21. 🆕 New blog post on Apple Unified Logs (iOS) and how to query them effectively.
    🪵 Learn how to generate a .logarchive using a macOS device, third-party tools, or straight from files in a full file system extraction.
    🪵 Use a macOS device to convert the .logarchive into a JSON file for use outside of a macOS environment.
    🪵 Process the JSON file with iLEAPP in order to query the data using SQLite.

    If you are not looking at unified logs you are missing incredibly valuable evidence in your cases.

    Thanks to the following researchers for their invaluable contributions:
    🙏 Lionel Notari
    🙏 Tim Korver
    🙏 Johann POLEWCZYK
    🙏 Heather Charpentier

    Read the blog post here:

    abrignoni.blogspot.com/2025/05

    #DigitalForensics #DFIR #MobileForensics #UnifiedLogs #AppleForensics #iOSForensics #iLEAPP
    #DigitalForensics

  22. 🆕 New blog post on Apple Unified Logs (iOS) and how to query them effectively.
    🪵 Learn how to generate a .logarchive using a macOS device, third-party tools, or straight from files in a full file system extraction.
    🪵 Use a macOS device to convert the .logarchive into a JSON file for use outside of a macOS environment.
    🪵 Process the JSON file with iLEAPP in order to query the data using SQLite.

    If you are not looking at unified logs you are missing incredibly valuable evidence in your cases.

    Thanks to the following researchers for their invaluable contributions:
    🙏 Lionel Notari
    🙏 Tim Korver
    🙏 Johann POLEWCZYK
    🙏 Heather Charpentier

    Read the blog post here:

    abrignoni.blogspot.com/2025/05

    #DigitalForensics #DFIR #MobileForensics #UnifiedLogs #AppleForensics #iOSForensics #iLEAPP
    #DigitalForensics

  23. 🆕 New blog post on Apple Unified Logs (iOS) and how to query them effectively.
    🪵 Learn how to generate a .logarchive using a macOS device, third-party tools, or straight from files in a full file system extraction.
    🪵 Use a macOS device to convert the .logarchive into a JSON file for use outside of a macOS environment.
    🪵 Process the JSON file with iLEAPP in order to query the data using SQLite.

    If you are not looking at unified logs you are missing incredibly valuable evidence in your cases.

    Thanks to the following researchers for their invaluable contributions:
    🙏 Lionel Notari
    🙏 Tim Korver
    🙏 Johann POLEWCZYK
    🙏 Heather Charpentier

    Read the blog post here:

    abrignoni.blogspot.com/2025/05

    #DigitalForensics #DFIR #MobileForensics #UnifiedLogs #AppleForensics #iOSForensics #iLEAPP
    #DigitalForensics

  24. 🆕 New blog post on Apple Unified Logs (iOS) and how to query them effectively.
    🪵 Learn how to generate a .logarchive using a macOS device, third-party tools, or straight from files in a full file system extraction.
    🪵 Use a macOS device to convert the .logarchive into a JSON file for use outside of a macOS environment.
    🪵 Process the JSON file with iLEAPP in order to query the data using SQLite.

    If you are not looking at unified logs you are missing incredibly valuable evidence in your cases.

    Thanks to the following researchers for their invaluable contributions:
    🙏 Lionel Notari
    🙏 Tim Korver
    🙏 Johann POLEWCZYK
    🙏 Heather Charpentier

    Read the blog post here:

    abrignoni.blogspot.com/2025/05

    #DigitalForensics #DFIR #MobileForensics #UnifiedLogs #AppleForensics #iOSForensics #iLEAPP
    #DigitalForensics

  25. 🆕 New blog post on Apple Unified Logs (iOS) and how to query them effectively.
    🪵 Learn how to generate a .logarchive using a macOS device, third-party tools, or straight from files in a full file system extraction.
    🪵 Use a macOS device to convert the .logarchive into a JSON file for use outside of a macOS environment.
    🪵 Process the JSON file with iLEAPP in order to query the data using SQLite.

    If you are not looking at unified logs you are missing incredibly valuable evidence in your cases.

    Thanks to the following researchers for their invaluable contributions:
    🙏 Lionel Notari
    🙏 Tim Korver
    🙏 Johann POLEWCZYK
    🙏 Heather Charpentier

    Read the blog post here:

    abrignoni.blogspot.com/2025/05

    #DigitalForensics #DFIR #MobileForensics #UnifiedLogs #AppleForensics #iOSForensics #iLEAPP
    #DigitalForensics

  26. Hey #iosforensics pals - is there a way to perform a physical acquisition of an iPhone without using any specialist commercial software?

    I'd love to extend my research beyond the iPhone backup, but don't have access to any of the fancy ($$$) tools. 😢

  27. Hey #iosforensics pals - is there a way to perform a physical acquisition of an iPhone without using any specialist commercial software?

    I'd love to extend my research beyond the iPhone backup, but don't have access to any of the fancy ($$$) tools. 😢

  28. Hey #iosforensics pals - is there a way to perform a physical acquisition of an iPhone without using any specialist commercial software?

    I'd love to extend my research beyond the iPhone backup, but don't have access to any of the fancy ($$$) tools. 😢

  29. Hey #iosforensics pals - is there a way to perform a physical acquisition of an iPhone without using any specialist commercial software?

    I'd love to extend my research beyond the iPhone backup, but don't have access to any of the fancy ($$$) tools. 😢

  30. Hey #iosforensics pals - is there a way to perform a physical acquisition of an iPhone without using any specialist commercial software?

    I'd love to extend my research beyond the iPhone backup, but don't have access to any of the fancy ($$$) tools. 😢

  31. 🚨 The SEGB file format is a key data recovery source on devices that run iOS and macOS. SEGB version 2 comes in the most recent operating system implementations.

    🔬 Understand the file format: cellebrite.com/en/understandin

    📄 Parse the file format using Python: github.com/cclgroupltd/ccl-seg

    #DigitalForensics #MobileForensics #iOSForensics #SEGB #DFIR

  32. 🚨 The SEGB file format is a key data recovery source on devices that run iOS and macOS. SEGB version 2 comes in the most recent operating system implementations.

    🔬 Understand the file format: cellebrite.com/en/understandin

    📄 Parse the file format using Python: github.com/cclgroupltd/ccl-seg

    #DigitalForensics #MobileForensics #iOSForensics #SEGB #DFIR

  33. 🚨 The SEGB file format is a key data recovery source on devices that run iOS and macOS. SEGB version 2 comes in the most recent operating system implementations.

    🔬 Understand the file format: cellebrite.com/en/understandin

    📄 Parse the file format using Python: github.com/cclgroupltd/ccl-seg

    #DigitalForensics #MobileForensics #iOSForensics #SEGB #DFIR

  34. 🚨 The SEGB file format is a key data recovery source on devices that run iOS and macOS. SEGB version 2 comes in the most recent operating system implementations.

    🔬 Understand the file format: cellebrite.com/en/understandin

    📄 Parse the file format using Python: github.com/cclgroupltd/ccl-seg

    #DigitalForensics #MobileForensics #iOSForensics #SEGB #DFIR

  35. 🚨 The SEGB file format is a key data recovery source on devices that run iOS and macOS. SEGB version 2 comes in the most recent operating system implementations.

    🔬 Understand the file format: cellebrite.com/en/understandin

    📄 Parse the file format using Python: github.com/cclgroupltd/ccl-seg

    #DigitalForensics #MobileForensics #iOSForensics #SEGB #DFIR

  36. 🐍 New Python parsers for Apple SEGB versions 1 & 2 file formats by Alex Caithness and CCL Solutions Group. Will be updating #iLEAPP soon to support both formats.

    📚 These data structures are found in iOS and macOS operating systems. SEGB v2 are found on the latest versions of these operating systems.

    🔎 Important note: If you expect Protobuf as the data payload (it usually is) make sure to skip the first 8 bytes before decoding a SEGB v2 file. See line 17 in the attached image.

    ℹ Notice how the script provides the offset, metadata offset, and timestamp along with the data.

    📎 Get the code here: github.com/cclgroupltd/ccl-seg

    📖 Thanks to Cellebrite for the file format research found here: cellebrite.com/en/understandin

    #DigitalForensics #MobileForensics #iOSForensics #SEGB #DFIR

  37. 🐍 New Python parsers for Apple SEGB versions 1 & 2 file formats by Alex Caithness and CCL Solutions Group. Will be updating #iLEAPP soon to support both formats.

    📚 These data structures are found in iOS and macOS operating systems. SEGB v2 are found on the latest versions of these operating systems.

    🔎 Important note: If you expect Protobuf as the data payload (it usually is) make sure to skip the first 8 bytes before decoding a SEGB v2 file. See line 17 in the attached image.

    ℹ Notice how the script provides the offset, metadata offset, and timestamp along with the data.

    📎 Get the code here: github.com/cclgroupltd/ccl-seg

    📖 Thanks to Cellebrite for the file format research found here: cellebrite.com/en/understandin

    #DigitalForensics #MobileForensics #iOSForensics #SEGB #DFIR

  38. 🐍 New Python parsers for Apple SEGB versions 1 & 2 file formats by Alex Caithness and CCL Solutions Group. Will be updating #iLEAPP soon to support both formats.

    📚 These data structures are found in iOS and macOS operating systems. SEGB v2 are found on the latest versions of these operating systems.

    🔎 Important note: If you expect Protobuf as the data payload (it usually is) make sure to skip the first 8 bytes before decoding a SEGB v2 file. See line 17 in the attached image.

    ℹ Notice how the script provides the offset, metadata offset, and timestamp along with the data.

    📎 Get the code here: github.com/cclgroupltd/ccl-seg

    📖 Thanks to Cellebrite for the file format research found here: cellebrite.com/en/understandin

    #DigitalForensics #MobileForensics #iOSForensics #SEGB #DFIR

  39. 🐍 New Python parsers for Apple SEGB versions 1 & 2 file formats by Alex Caithness and CCL Solutions Group. Will be updating #iLEAPP soon to support both formats.

    📚 These data structures are found in iOS and macOS operating systems. SEGB v2 are found on the latest versions of these operating systems.

    🔎 Important note: If you expect Protobuf as the data payload (it usually is) make sure to skip the first 8 bytes before decoding a SEGB v2 file. See line 17 in the attached image.

    ℹ Notice how the script provides the offset, metadata offset, and timestamp along with the data.

    📎 Get the code here: github.com/cclgroupltd/ccl-seg

    📖 Thanks to Cellebrite for the file format research found here: cellebrite.com/en/understandin

    #DigitalForensics #MobileForensics #iOSForensics #SEGB #DFIR

  40. 🐍 New Python parsers for Apple SEGB versions 1 & 2 file formats by Alex Caithness and CCL Solutions Group. Will be updating #iLEAPP soon to support both formats.

    📚 These data structures are found in iOS and macOS operating systems. SEGB v2 are found on the latest versions of these operating systems.

    🔎 Important note: If you expect Protobuf as the data payload (it usually is) make sure to skip the first 8 bytes before decoding a SEGB v2 file. See line 17 in the attached image.

    ℹ Notice how the script provides the offset, metadata offset, and timestamp along with the data.

    📎 Get the code here: github.com/cclgroupltd/ccl-seg

    📖 Thanks to Cellebrite for the file format research found here: cellebrite.com/en/understandin

    #DigitalForensics #MobileForensics #iOSForensics #SEGB #DFIR